![]() If I log an issue it seems to be resolved relatively quickly. However, that said, I’ve always found a way to get around issues with a bit of thought (and a lot of help from the forum) to get the end result I’m after. I couldn’t agree more that there are some bugs and issues that really should have been picked up before release. I’m just a hobbyist and have been using xojo for a year and android for the last month. If after so many years of testing, something so basic as the MessageBox class, causes a compiler error, is hard to thing that the rest of the platform is in better shape… ![]() (close genymotion) And xojo FINALLY runs the app in the emulator…Ĭreated a simple container, put an integter property ad it to the inspector behavior bit it is NOT shown in the inspector…Ĭustom controls with containers not working? Xojo cant run the emulator but if I oppen the emulator first xojo can run alogside Android studio?.Ĭlose all Android studio related… Same ErrorĬlose Genymotion? (no way that can be) Yes, Xojo sees Genymotion as Android Studio Try again, this time started the emulator before running the app, click run, and WTF? Fun fact, support for Genymotion was sugested SIX YEARS AGO… 45688 - Android : please don't use only the simulator from the Android SDK This days the Android emulator has many more features but flexibility is a plus.ġ0 minutes and xojo was frozen, kill the emulator, xojo responded … Harcode the use of an emulator instead of using the standard Android Debug Bridge is not a good sign. Launch again, this time just a button with no code, this time xojo launches the Android studio emulator instead using the already running Genymotion one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |