Nightmare in API 2.0

[Chris_O_Brien]

Trying to transition my primary project from RecordSet to RowSet going from API 1.0 to 2.0 was a big in itself, but I got through it. Now I need to change one class from a ListBox to DeskTopListBox…

I can understand the need to change some of the event and method names due to changes like one to zero base referencing. I can even understand name convention changing for consistency, but why did you decide to deprecate the old events and methods completely?

[MarkusR]

there are some menüs in the ide to move to api2.
for some other issues maybe use your own sub class or extends.

[Emile_Schwarz]

Are-you using 2022r3 ?

[Chris_O_Brien]

Yes, 22R3. I was getting away with not needing to change my classes up to now but an EventDefinition is no longer firing reliably which I figured may be related to me using the ListBox. It’s hard to know what the best approach to take is now

[Beatrix_Willius]

@Chris_O_Brien

EventDefinition is no longer firing reliably which I figured may be related to me using the ListBox

Haven’t seen that before. Please try to isolate the problem.

[TimStreater]

You can’t partialy deprecate something.

You shouldn’t try to do too much at once. I suggest you have the API1 class and the equivalent API2 class with a slightly different name, in your app at the same time. Then you can move each instance over, one by one. When there are no more instances left of the old class, delete it and do a global name change for the API2 class.

See also:

API1 to API2 conversion experience

As I’ve no development I feel like doing on my app at the minute, I decided it was the time to attempt the conversion. A number of things have cropped up. Start with two copies of the project. One is for trying things, the other is for applying permanent conversion steps to. I have a number of small windows with only a few controls in each; these converted easily, with no compilation errors, and worked OK when tested. Such steps can then be applied to the clean copy. Having done that, SAVE! Thi…

[Chris_O_Brien]

Thanks Beatrix - Ya, I’ve decided to at least work around it - Worrying though.

[Emile_Schwarz]

@TimStreater

I suggest you have the API1 class and the equivalent API2 class with a slightly different name, in your app at the same time.

Have-you tried that with Xojo 2022r3 ?
If no, try, then feedback what you found.

[TimStreater]

I don’t have any API1 classes to try it on.

[Chris_O_Brien]

Thanks Tim. It’s good advice and I’ll probably take that route. I toyed with the idea of changing to Jim Kay’s excellent DataView for the added features, but with the new grid control on the way, changing is a less attractive idea.