When you create a custom control from a canvas, container control or some other base class its not unusual to use raise event to create new events like “BeforeButtonPressed”, “AfterButtonPressed” or to just make it so you;r control can implement normal events like Open, Close, etc and pass then along.
You’ll see code using raiseevent to cause these events to be raised on any instances.… Read the rest
A lot of times when you need to create a menu at runtime you don’t know the number of items and those items may require some additional data to be handled correctly like a folder item, window reference etc. And in cases like this a subclass of MenuItem makes sense so you can add properties to the subclass and implement the action event to handle that extra data.… Read the rest
No. Not at my place 😛
Sometimes you NEED to test your app and whatever remediation you have put in place and need a reliable way to make your app crash
Here it is
Dim p As ptr
p.Byte(0) = 123
Those two lines. Insert them anywhere you might put normal code and book your app will crash.… Read the rest
An interesting question posed by a relatively new user came up on the forums. It had to do with how the Array() function worked and how he could force it to return an array of variants to call his method.
His method was defined like
BuildMenu( base as menuitem, params() as variant)
And he would call it like
Result = BuildMenu (base, Array ("Run", False, "Edit", "Rename", "Delete") )
and this would build up a menu from the base item and append menu items to it.… Read the rest
In a different forum a user reminded me of a speed tip that had cropped up once or twice over the years. It has to do with popupmenus.
Basically on older versions of macOS if you did
PopupMenu1.ListIndex = -1
For i As Integer = 0 To 1000
PopupMenu1.AddRow Str(i)
NextThis behaved not so badly although there is a slightly faster variation
But on Mojave this is noticeably slow.… Read the rest
If you’re a developer and work in light and dark modes and switch back and forth all the time this is a handy utility to grab.
It makes switching between the two modes fast and simple.
I know a lot of you don’t want to mess with Xcode BUT there are some really handy things it can help you with and you don’t have to write any Swift or Objective-C code.
Since you can drop a plist into Xojo to supplement or replace certain keys at some point you may need to create one.… Read the rest
Suppose you are creating a new container control to encapsulate some functionality onto this new control. You’re already thinking about “encapsulation” which is a good thing.
Why, when you create this new container, would you then make all the controls on it public so code outside the container can change it ? That seems like it would be a good way to ruin the encapsulation you’re trying to achieve.… Read the rest
Not for your children (although that is important too since kids can be incredibly harsh and will pick on kids with names that they think sound different or odd)
This is to do with naming methods, properties, and just about everything else in your Xojo projects.
A good name indicates a number of things to anyone who reads the code.… Read the rest
Sometimes its nice to be able to know what class defined a property or method. Introspection makes this mostly knowable.
The reason I say “mostly” is that something the introspection metadata does not tell you is if the property definition is local or inherited. So you cant tell for sure if a property in a subclass is one defined in the subclass or the inherited one from the superclass.… Read the rest