Xojo has no “friend” scope (see https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.cbclx01/cplr044.htm)
In other words there is no way to indicate that one class or method can call the protected / private methods of another class. Either the methods are public, and any other code can use them, or they are protected so only the class & subclasses can use them, or private and then only that class can access them.… Read the rest
Took a few minutes last night and helped out another member of the Xojo world.
Seemed like he was a bit stuck and what I pointed out got them back on track.
And then I got several messages :
Norman, you are a FUCKING treasure to this community.
… Read the restNobody tries to help as much as you do.
Recently my wife and I took my mom with us when we went on a ski trip.
While there I came across a couple guys who were paragliding and it looks like so much fun!
Maybe next year I’ll give this a try 😛
Theres a long thread on the Xojo forums about Color shouldnt be a reserved property name
It really isnt. This is JUST the IDE preventing you from using the name IN the IDE
It causes no confusion.
The title of this article was, at one time, a recommended way for figuring out the current session in a Web 1.0 app
The compiler has NO issue sorting out whats a variable, whats a data type, and whats a method call.… Read the rest
The official line is “if you want to run Big Sur you MUST use a version newer than 2019r3.2” – at least for desktop apps (web apps arent affected in the same way)
But you CAN actually get 2019r1.1 to work for desktop apps on Big Sur
Here is what I have done to be able to run Xojo 2019r1.1 on Big Sur (Intel) – and to successfully DebugRun and Build Desktop applications:
Replace these files in the Xojo 2019r1.1 application bundle with those from 2019r3.2:
Contents/Resources/SDKStubs/macosx10.14/System/Library/Frameworks/AppKit.framework/AppKit.tbdClosed (Already Exists) – 6
Closed (by Design) – 38
Closed (Duplicate) – 32
Closed (Misc) – 25
Closed (Not Actionable) – 3
Closed (Not Reproducible) – 38
Closed (Won’t Implement) – 7
Fixed – 5
Fixed & Verified – 91
Implemented – 2
Implemented and Verified – 9
Needs Review – 6
Reproducible – 141
Resolved – 2
Reviewed – 189
Verified – 29
Open – 365
Closed – 259
In code I’ve been writing I’ve found a need to be able to “add properties” – but not in a conventional way.
Normally I’d just add a property to some class in my Xojo code and be off & running. But now I’m needing to be able to define “classes” (They’re not really classes) in a way that they can be added EVEN AFTER the application has been compiled.… Read the rest
I’ve seen others comment that they’ve run into slow downs with API 2.
I’ve been trying to sqeeze every last ounce from a large app and ran into this one. I’d suspected it might be a hit but measuring it indeed shows there is a hit – not tens of seconds but when you want EVERY last microsecond these few add up.… Read the rest
I know this was posted about years and years ago. Its probably been a decade or more since this was last written about.
But I ran into it again and had to say to myself “Oh right you cant do this this way because the App method will return nil at this point”
The situation is I wanted to put a custom menu item subclass into the menu bar.… Read the rest
A while back I started thinking that some of the new style Xojo is using is awkward but it never really struck me why it felt that way.
After working with new releases for a while I know what I find strange.
Sometimes you tell an instance to do something.
var someInteger as Integer
var s as string
s = someInteger.ToString