I’ve just gotten this Mail:
This was a decade long Xojo bug from MacOS Lion times…
This in strong contrast to the rapid reaction and fixes from @Garry 
Have a nice Weekend!
And who is to say it’s actually fixed.
Well, it probably is. Martin is pretty reliable when reporting.
However, if you have an API 1 project you have to update to using DesktopTable and while you don’t have to do the whole API 2 upgrade once you start getting into the new controls and windows you’re kind of forced to do most (all?) of the project. And for us there’s simply no way that we’re going to do that.
Lion was 14 years ago. Fixed now…
Yeah I received several that are many years old that are in the “new” desktoplistbox
Mixing and matching is supposedly possible but any time I ever tried it was all or nothing
IIRC there was point where once you used you had to go all the way. I think that might have been DesktopWindow but I use Xojo so little that I don’t remember. Funny enough, I’ll be using Xojo a bit in the upcoming weeks. I’m sure it’ll be a PITA.
you know the paths between Xojo and Objo once were very close
while one was on downward vertex the other developed and improved a lot…
And he read this Forum…
READ THAT MARTIN:
I read two or three (probably) bugs reports about DesktopTable, and finally go to the documentation and ask for DesktopTable and the anwser was in the page that talk about what will come.
REMEMBER:
I do not have access to any cponfidential information. I just what is available (issues for example) as with Jade (there were some issues reports during “beta” time (I suppose it was beta time).
Have a nice Sunday.
I found what I forgot in the entry above:
From Roadmap:
These items are planned for upcoming releases of Xojo:
Item
Description: DesktopTable
A modern, performant upgrade for the classic DesktopListBox control.
The problem is that Xojo puts a lot of things on their roadmap and they often take years to come to fruition. They’ve needed a real table control for over a decade and only now, when there’s real competition in their space, are they willing to provide the things that users have been asking for all that time.
I really hope that what’s coming is not just a scrolling area which contains container controls though…
If this is what I think it is, it is NOT fixed, they swizzled the NSScroller class to ‘control’ how the slider is drawn. A real fix would be to dump that 1990’s listbox in the garbage and build upon a NSTableView, it’s possible as I did the ground work for it, but to do a complete implementation would be a fairly large job, and I made the decision that the Xojo market for such an add-on is too small to be worth the time.
If the contents of the list are small enough, you could even fake it with a canvas in a NSScrollView, albeit you have to manually intercept and reverse all the mouse vertical co-ordinates, because they get borked by Xojo’s framework.
So this ‘fix’ doesn’t really inspire much confidence from me, unless of course they’d paid me to be the one to have made 
I did try to sell 'em my AppKit, but you know their glorious CEO, why spend money to buy something externally, when you can spend more money to have people invest months or years in trying to figure out how to do it.
Not saying this is what happened but… you know that if they had your encrypted classes, they have the source, right? The IDE has to extract them for compiling, so encryption is worthless in protecting from Xojo.
Which is why I tell people building Libraries for themselves is a waste. Literally throwing out the source code. At least “encrypted” classes can be recovered.
With Buoy we went with packages being allowed to contain binaries, source or a mixture of both.
it depends… we live in the open source code world
If they did just that, it doesn’t create any more confidence in Xojo as a company, or even their current technical capabilities.
The thing is, when they got caught parsing the string for System.Version (exactly as Apple told them not to) on the issues ticket they were spoon fed the correct code / declares for getting the version. Their fix was to update the string parsing… which got broken a few macOS betas later…
We know they don’t accept input from the outside, to such a fault that it causes problems.
Yeah, I remember that. Geoff was so insistent that it HAD to be done the way they were doing it. Oh well, at least I don’t have to worry about dumb shit like that any more.
That bug hit me so hard, it’s the day I realized I needed to find another development platform.