I know how to debug and modify CodenameOne source in an app. That is described here
Can I do the same for the code under iOSPort? I am interested in testing a modified version of Ports/iOSPort/nativeSources/CodenameOne_GLAppDelegate.m. using a build hint to append code to the delegate is not an option since what I need to test is a change within an existing method.
I think a recent update broke something in it but the ticket I raised on GitHub isn't being replied to, so I'd like to see if I can propose a fix myself
When you use include source the full iOS port is included into the source and you can debug directly into the port. You can just copy and paste your changes into there and then debug these changes. Then copy and paste it back.
That's how we test changes to the port.
Related
I'm experimenting with using dev-containers for development by trying to follow along with this simple example: https://github.com/microsoft/vscode-remote-try-python
The setup works fine and I am able to build and connect to the container, and run the app just fine. However, if I try to edit anything and save it, I get an error:
Failed to save 'app.py': Unable to write file 'vscode-remote://dev-container+2f55736572732f62726164656e2e6b696e6172642f706572736f6e616c2f7673636f64652d72656d6f74652d7472792d707974686f6e/workspaces/vscode-remote-try-python/app.py' (Unknown (FileSystemError): Error: EROFS: read-only file system, open '/workspaces/vscode-remote-try-python/app.py')
If I open a secondary window with the local folder open, I can save changes and those are reflected in the remote container window. But due to the file system being set to read-only, I can't edit anything from within the remote container. Any ideas on why I am stuck in read-only?
One potentially important note is that I am using using Colima (version 0.2.2) rather than Docker Desktop, thought I haven't found anything to indicate that this would be an issue.
I found the answer to my own problem. Turns out the issue was using Colima as a runtime. I came across the discussion around issue #102 on the Colima Github page. According to the developer, the default mount "Used to be read-only, but changed to writable in version 0.3.0.". I was using v0.2.2.
I updated colima to the most recent version (v0.4.4) and it fixed the issue for me.
i'm working with renesas MCU RX65N, i want to make a serial connection with other board and also display an HMI i designed on Appwizard, i followed the steps they offer on their manuals but won't work either. Then found more information about how to solve it, and the code works by itself, but when i try to merge both programs just keeps giving me errors (problems that doesn't appear on individual projects), this is the error i got now, and don't know what to do because apparently it is included for my project but won't open no matter what i try, anyone knows how to solve it or what to do?
It sounds like when you include the file in one project, it works, but when you include it in another project, it doesn't? It sounds like there is a configuration difference between your projects. Try creating a new file in a project, then just put #include "r_bsp_config.h" in it, or however you wrote it (it may need to be #include <r_bsp_config.h>). See if you get the same error (you will probably get an error, something about missing main(), but the question is whether you get the same error). If you don't, cut and paste the code from the problematic project in, and also make sure the project configuration is adjusted to match, and see if it works now. If you do get the same error, then see if you can copy the project configuration from the working project to the new project, and see if you get the error this time.
Yesterday i updated to the latest version of CodenameOne.
I like the new version of the new GUI but... 2 problems:
When I try to add a command from the new GUI, the code created to the java file creates an error. If I remember correct it says ";" missing. So i create now the command by code.
On buttons I create a new Action Event. It is created to the jave file, but it never run the code to the onButton_1ActionEvent handler. I tried with debug and never goes in there. It works perfect when i create the Action event from the code myself.
So is it a bug, or i do something wrong? Plugin Version is 3.5.5
Thank you
We released 3.5.6 yesterday which is still undergoing verification right now. When submitting issues/problems we need the version of the GUI builder from the about menu, it looks like this:
I am trying to apply this bug fix http://code.google.com/p/selenium/source/detail?r=11856 to the selenium-server-standalone-2.0b3.jar.
Does anyone know where I can get the source code? The jar only contains class files.
Or if there are alternate ways of getting what I need, please do tell.
Thanks,
-Denali
You should be able to check it out from SVN:
Use this command to anonymously check out the latest project source code:
Non-members may check out a read-only working copy anonymously over HTTP.
svn checkout http://selenium.googlecode.com/svn/trunk/ selenium-read-only
I am not entirely sure how this project branches their code, but I assume it would be a branch in the project for a release.
I have a WPF project which compiles just fine. However, when I enable code contracts, I get a lot of errors like the following:
file 'C:\MyProject\obj\Debug\MyFile.g.i.cs' could not be found
Is there workaround?
Just FYI... This bug has been fixed in the latest version of Code Contracts (v1.2.21023.14, released Oct. 22nd).
Can you be a bit more specific about your repro steps? The significance of the files ending in .g.i.cs is they are files generated specifically to enable intellisense in running projects. They are not truly part of the build process and likely should not be consumed by code contracts. I'm not a code contracts expert by any means though so I could be wrong on this point.
I posted a repro and workaround to this problem on the Code Contracts forum. Here's the URL:
http://social.msdn.microsoft.com/Forums/en-US/codecontracts/thread/4f2af748-1db1-4175-abf0-fbcc82f177ee
The short answer is that the error occurs whenever you have multiple projects that reference each other in a Solution, and one of the child projects is a WPF control library. To get around the problem, you can either disable contract verification for the parent project(s) (the ones that reference the other projects), or you can add a post-build event to the offending child project(s) to create the *.g.i.cs files that the Code Contracts rewriter is looking for.
For example, create a blank text file in the root directory of your child project and name it "Blank.txt". Then add the following command as a post-build event in that project:
copy "$(ProjectDir)Blank.txt" "$(ProjectDir)obj\$(Configuration)\GeneratedInternalTypeHelper.g.i.cs"
Copy this line as many times as needed, one for each missing file.