I type it out, then click in another field and it reverts to the default name. This is generally true throughout the IDE, but I get hit on control names, especially. Tabbing does not tell the IDE to accept the new information. This was discussed before, including Norman. I cannot be the only one to get these 'simply to found' bugs.Īdd a line of code (where you want, but in the code editor),Īnd I found the cursor - usually - in the find field (or elsewhere), but not in the Code editor, where I left it before the run…Ĭontent-Type: text/plain charset=us-ascii Continue reading Introducing Xojo Desktop single platform and Xojo Enterprise. That feeling comes from the number of misfeats I fall into in my simple daily use of the IDE. Xojo 2014 Release 2 was unleashed today and in addition to many improvements, updates and new examples, we’ve introduced 2 new Xojo license options. I stopped reporting these because of that feeling. My deep feeling is that the Xojo engineers are working deeply in the beast and do not have much time to resolve these 'annoyances'. SOME FIELDS in the IDE accept a Tab (or a Click Elsevhere) and validate the change. I rate this as a nasty usability bug as - if you're not paying attention - you'll get bitten by it when you try to compile and get a TypeMismatchException. System Info: MacOS X 10.8.5 with Xojo 2014r1.1 Workaround - After creating the property desired, click on the 'Default' field of the inspector pane, then Tab out.

Make a new property, then re-select the 'foo' property - it'll still show type as 'Integer' in the inspector pane!!! It'll take you back to the code editor, but the type indicator (badge?) on the property will show '1' with a circle, indicating a numeric type.

Click on the Inspector and change the type to 'String', then try to tab out. Now create a new class (a new module would probably work just as well). To replicate, create a new project and save it somewhere.