Mac OS High Sierra 10.13.4 Eclipse Oxigen 3a Java JDK 9.0.4 Garmin JDK 2.4.5
1. START ECLIPSE ===> AppSettingsEditor Off, Simulator Off: Eclipse CPU=1%, Simulator=0% 2. START SIMULATOR ===> AppSettingsEditor Off, Simulator On: Eclipse CPU=1%, Simulator=38% 3. START APPSETTINGSEDITOR ===> AppSettingsEditor On, Simulator On: Eclipse CPU=3%, Simulator=38% 4. CHANGE & SEND PARAMS. ===> AppSettingsEditor On, Simulator On: Eclipse CPU=100%, Simulator=31%
Then eclipse freezes (100% CPU) :-(
Important data: - Number of possible settings (booleans, list, number, text): 59 - Application (watch face) size: 44Kbytes
With less number of properties (for example, 8, of different types), there are no problems. I do not remember when I started experiencing this problem (20, 30, 40 properties, ...). I decided to test the settings by coding them. It was the only way I found to keep on working.
In my older platform (Windows 7, etc.) I had the same problem in the past, but I do not remember more details, neither how I overcame it.
It's really annoying and devaluates the value of the Garmin platform.
Please, Garmin colleagues, could you fix it? If you need more data or you want me to do any test, do not hesitate to tell me.
One additional detail: the problem could be related to the use of lists. I've checked that it arises when there are a lot of list parameters in the settings. Lists are useful for several things, e.g. in order choose the colors of the items in the application. I took the ObjectStore sample in the Garmin SDK and I added 50 lists, 13 colors each one, and then the issue appeared. When I reduced the number of lists to 30, the simulator did the work (but it took its time to finish).
I hope this helps the Garmin team to fix the problem.
Thanks for the additional info on this. We've got a ticket open for investigation, but I don't anticipate the problem will be fixed before the 3.0.0 SDK comes out of beta.
