I have copied the project from my old amchine to windows 10 machine. Application works without any problem on simulator. If I right click to see the properties, I don't see IOS, Android and build hints. Please advise if there is something I'm missing here.
This was removed ages ago in Codename One 5.0 but was deprecated before that. See https://www.codenameone.com/blog/removing-old-preferences.html
You should use Codename One Settings in the right click menu.
Related
Using Eclipse Photon and the newest version of the Codename One plugin, I have an issue where I create a new project and then create a GuiBuilder form inside that project, but when right clicking on that form I do not see any of the Codename One specific options I should be seeing, like the Guibuilder option. So I can't open the form in the Guibuilder.
This is happening in a 36 seat computer lab, but not on my office machine. Any ideas what might be going wrong in the lab?
If anyone else has this same issue, as Shai suggested, it had to do with where the Eclipse workspace was located. In my case I had it on the lab desktop.
There were spaces in the path, but even removing those did not solve the problem if the workspace was on the desktop. When I moved the workspace to the user folder, all started working as I would expect it to work.
There might be an issue with the length of the workspace path, along with special characters. Regardless, relocating the workspace to c:\users\win10\workspace solved the issue for the lab computers.
I have a strange problem I need some help with.
Very recently I started experiencing a problem with the hamburger/side menu.
On startup our production version renders the hamburger menu in black but the current dev version renders in blue.
Once I login on the dev version, and start using the app, when I go into one of our application's forms, the hamburger menu disappears. The side menu can be activated by a slide-in motion.
I first started seeing this when doing a cloud/device build, not on the simulator.
A day or so after I got this on the simulator.
Thinking it may have been an environment issue (specifically I had been doing some theming with the GUI designer), I set everything up on my Windows VM, with a clean copy of the production code copied out of SVN - but I get this problem on the 'clean' version.
As I inherited this code, I was able to go back to the machine left by the previous developer and in running their version in the simulator all was fine. Black hamburger on login screen and present on our application forms.
I submitted the code to do a SAAS device build but then a library update ran on this previous developers machine, and I now get blue Hamburger at startup and missing on our application forms in the simulator - the same problem that I got.
Seems to point to something in the new libs. So, I then pegged the versioned build back a level (3.6 rather than latest) - to try to resolve any 'new version' issues but I get the same problem.
I guess we are missing some initialisation steps out on the new sidemenu - our code has been in place for a few years now, so ideally I would like to build against the previous version of the CN1 libs where we didn't have this problem until I have time to work what we are missing.
I thought versioned build would give me this ability but the problem persists- any assistance would be gratefully accepted.
UBUNTU 16.04
Windows 8&10
Eclipse Oxygen
We transitioned to the on-top menu over the weekend. This has been announced a while back and despite that as usual people were caught a bit off guard. We posted multiple updates on that to the blog so you should probably keep an eye on that.
The on-top side menu uses the default TitleCommand UIID styling where the old side menu had a different UIID but I'm guessing the engineer in charge used the theme constant sideMenuImage which we didn't include in the first release of on top side menu. This should be fixed in the update coming out this Friday (November 3rd 2017).
FYI You can disable the on-top mode using Toolbar.setOnTopSideMenu(false) although I would recommend sticking with it as it's WAY better.
IDE: Eclipse
Desktop OS: Mac
Device : Android 4.0.4
Hi,
last week i sent a new android build to the server, and it updated the jar files i have on my Mac, then i installed the app on LG android 4.0.4 device that i tested before, and was surprised to find some pages display all black.
After investigating a little, i discovered that when i use tabs on any form the form will be displayed black only on android, no problem on simulator nor IOS iPhone 6S.
I looked at the forum and i found similar problem happened a year ago , and the solution was to use "android.asyncPaint=false" temporarily . now this removed the black, but messed all the rendering while navigating between tabs.
So my question is why this happened now? the past three months i was developing and deploying on android without any problem. Did the newest update corrupt something?
Thanks
Sam
Using the android.asyncPaint flag is discouraged as it will fallback into a relatively slow compatibility mode. We are currently investigating some regressions in some rendering optimizations that affect some devices and are in the process of deploying a solution for that.
Please let us know if the issues persist.
At some point I seem to have a lost the ability to go to native iPhone look in the codenameone emulator. How can I get it back to normal?
I did have two themes in the theme.res file - I've tried deleting them both and creating a new native one called "Theme". I've also commented out all my initialization code in the before call for the Form, but it still looks like this:
Codename One migrated to iOS 7 as required by Apple: http://www.codenameone.com/3/post/2014/01/switching-defaults.html http://www.codenameone.com/3/post/2013/10/seven.html
To use the old simulator for the old theme just select Skins->More and select the old iOS 6 skin. You probably shouldn't though since you need to migrate to iOS 7 which most devices have already migrated to.
My VS2010 doesn't stop at breakpoints inside of silverlight application. It appears that no symbols for it have been loaded during debugging. When I hover over the break point it says "The braekpoint will not currently be hit, no symbols have been loaded".
I have tried all of possible solutions offered by google and have no success. The problem occurs even when I create brand new silverlight app hosted by an ASP .NET web project. All of my project configuration looks fine - silverlight debugging is enabled in the Web project.
I am using silverlight 4.
here a link to the sample project created out from the tepmlate.
Any thoughts ?
P.S I just tried to reinstall VS2010 and the problem still exists.
EDIT: I just tested the same project on another machine and it stops at the break point it seams that the problem is somewhere in the configuration of VS or silverlight.
with Matt Dotson's help I managed to attach the debugger manually. However this solution is not good enough for daily use.
Depending on my experience in Silverlight following these steps keep your project debug-gable.
Condition 1>
Firstly we need to be ensure that in Web Project's properties there is a Web section, as you see below Silverlight checkbox must be checked.
Condition 2>
Follow In Menu Debug => Attach Debugger>
Visual Studio sometimes can't attach debugging platform you need to lead the way :) . By this way you may debug other platforms,(also you may debug your product platform but pdb files must be sync and don't forget you may suspend your product platform using this).
Condition 3> Your default web browser may be Firefox,Chrome or other than IE.By Visual Studio default try to attach to IE. But when you run VS calls default browser,so you need to have a manual attachment in Condition 2 or set your default browser by right clicking on default page > Browse with .
Condition 4> There is xap file generally located in web project\ClientBin directory. Sometimes after build operations this file can't be replaced and your ProjectDll and your Project PDB files not be sync. This cause wrong line match while debugging or can't find a debugging file attached caution. I strongly suggest delete all generated files in Bus project and delete Clientbin\ProjectName.xap file. After rebuild all it must be ok!
Hope helps.
What broswer are you using? You need to be using Internet Explorer to debug silverlight projects.
I have had a similar frustrating experience with this but in my case the solution was very simple. It seems that somehow, and I really have no idea how, the debugger option for Silverlight had become unchecked in the properties on the hosting ASP.NET project.
I just assumed that as I had been previously debugging, this option was set and I didn't bother to make sure that this was this case. Just goes to show that one should always check the basics first; if I had done that it would have saved me some time.
To check this in VS2010, right-click on the project and select properties, change to the Web tab and check the Silverlight option at the bottom of the page, in the debuggers section.
Also see the debugger to a silverlight process
http://msdn.microsoft.com/en-us/library/cc838267(VS.95).aspx
If that doesn't work, then
reset iis (if you are debugging in that)
delete temporary asp.net files (%SystemRoot%\Microsoft.NET\Framework\versionNumber\Temporary ASP.NET Files)
clean and rebuild your solution
The resolution came after 2 days of headbanging. It appears that the link which Malcolm gave covers exactly my problem but my I was narrow-minded enough not to pay it enough attention because when I run the debugger as long with the app my default browser was FF. So I thought that after the FF starts I can load the page from IE or Chrome.
Actually the problem is that the debugger cannot be attached to the silverlight project because of the FF. And when I load the app from IE or Chrome the debugger dis still not attached.
Thanks to everyone that tried to help.
if you have multiple project, Rebuild the project separately that you want break point. Its work for me
Try also picking internet explorer from browser list menu as your browser