If you get the green tick at startup you are already dead. Once the VS crashes the green tick, iirc, shows up all the time. The device confusion is related to this. Non existent devices are considered even if deleted or redefined, … The only way to create a device is at the beginning of the project in the wizard? Restarting Crossbox changes nothing.
These days the only way to test was to restart the whole box. Define the device at project creation. (Situation improved using Bonjour). Afterwards coding worked but synchronizing/transferring the files on compiling the first time failed. VS froze - not responding. When I revisited VS without rebooting the machine exactly what Jolyon described did happen. Green tick appeared. - Don’t test that states you get weird results and waste time. Had nothing to do with devices and communication among them - in Jolyon’s case maybe the initial spark but no the root cause he suffers from later on.
What I don’t remember exactly but I don’t think that’s very important - Project creation took a long while but finished, pressing compile crashed the IDE. I think that was in the state - restart after VS crashed, no reboot, defining the device in the project wizard (manually).
Again this is my experience from early days in the beta 6.0 beta cycle and has nothing to do with the current state. Since Marc was confused about the tick, I thought it could be helpful to provide an input based on my former experience. I have no such experience since the last version provided in the Beta or Gamma … I don’t remember exactly. Since the VMs (Win32 on VirtualBox) have been deleted, I cannot assist with precise revision numbers.
Thanks for the observations michael - fascinating stuff indeed!
Marc/Brian - hopefully the new build will fix things. I shall try it as soon as it appears (it’s not in my personal downloads area as yet). Fingers crossed!
But that happened in the Beta. I do not experience any problem at the moment. I just thought, because you talked about two different boxes with different behavior maybe the root cause could be a missing driver or a different one. I developed in the emulator until today because I was waiting to get a good Android device at a fair price. Nexus 7 and/or Nexus 10. The emulator was very slow first, but then I found the check-box to enable acceleration. In order to be fair, Oxygene hints with a warning in case a non accelerated device is detected. I looked at it and thought that’s correct:) Fingers crossboxed too!
Good news! Initial indications are positive. After installing the new build VS starts with the “normal” charcoal Crossbox indicator and “Crossbox: N/A” text.
Upon opening a Nougat project it updates to the correct device (currently unattached) with the caution icon indicating that Crossbox needs updating.
Upon opening a Cooper project is updates to the “Please select a device” prompt and the drop-down does now list my AVD’s (again, I don’t currently have any actual device attached).
So on the face of it, it all looks to be sorted (YAY!) but my working day has begun so further exploration will have to wait until I get home this evening (I used LogMeIn to access my home Mac for this so far).
Drat. My Windows 8 VM is useless via LogMeIn - when the VM captures the mouse the pointer disappears and I have no clue where my mouse is at. Sorry, this will have to wait until I get home this evening.
michael: “If you get the green tick at startup you are already dead.” — did you ever report this? i don;t recall anyone ever bringing this issue up, except for Jolyon now.
Marc. Do you remember the short discussion we had during the alpha/beta before version 6.x was released. Such a thing never happened again after you fixed, whatever you fixed. Topic about problems when replicating files on first compile - iOS, OSX. As that thread had been a long one I simply waited, since the problem went away. There could have been to many possible causes - VirutalBox, no Bonjour first, …, new Crossbox already announced… - After installing Bonjou and the New Beta everything worked fine,…
I have the impression that after VS freezes or ‘crashes’ some ‘global’ object that does contain the device information does survive. Maybe a temporary file or a lock?. And I think that confuses the plugin at startup. When you create project and manually define a device that cannot be reached … therefore can be different reasons. While you create a project and someone unplugs the device you cannot stop creating the project.
What happens after startup. The devices not reachable are grayed out. That works correct. Iirc, even if you delete such a device the device count is still higher than the ‘working’ devices. What you see does not match the internal information. Honestly, I don’t remember this very detail. If things work then the whole Oxygene + Crossbox works very reliable, rock solid.
Another Issue I encountered once in VS2012 after having turned off the user experience service. The assemblies have not been deleted in the target folders. After turning on the service again things improved and an IDE update seemed to have fixed the whole issue. Afterwards I simply uninstalled the VS Pro …
I think one of the reasons could be that most of the users use the full VS. Maybe integrated vs. isolated … no idea. I use the pure Oxygene for .net. That’s all in the first place for the moment. I bought a HDMI adapter for my Mac Book. Copied the business computer, use the XCode and try to avoid anything else, because I can stay on an old OS for years … this way and hope Sidney Fox will visit me one day because of my Book:)
What I meant with ‘dead’ is - If the add-in enters this state, it does not make sense to test a lot except for what I described. If creating a project and manually specifying a device works … then you run into the same issue. Specifying a device manually seems to help in a first place, but I would suggest - only define devices manually if the recognition together with Crossbox works. In case of Coca you have a Mac in order to test. Not talking about Android.
