Closed (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
… Read the rest
If you’re like some coders you like to have “clean” compiles
No warnings. No errors. Nothing.
So when a new one does popup you can inspect it, fix it, and return to a pristine state. Its one way to make sure new issues dont crop up very earliy in your work cycle.
Often you get a lot of “Unused event parameter” or “Unused method parameter” warnings.… Read the rest
- find the bug
- write a test to show the bug
- write the code to fix the bug
I’d made some changes to a client project and while I wasnt specifically fixing a bug I did alter a behaviour that resulted in one.
Turns out I didnt have a test already in place to reveal this change and that cost me a couple hours to track down, write the test, and fix the bug I’d caused.… Read the rest
Simply read the file from beginning to end and instead of always appending lines always INSERT the line just read at the front of the listbox.
t = f.OpenAsTextFile // open selected text file
While Not t.EndOfFile
x = t.ReadLine
and the list will appear “reversed” as if you read from the end back to the beginning