API v1 & API v2 third-party component woes

I have a project that has all my program logic done in API 2.

However I need to use a third-party UI component that’s encrypted and is written in API 1. I do not have the source code.

Unfortunately it seems to call some code from API 1 that no longer exists in API 2 (or is called something else) so I get a hard crash when I try to run it in the debugger.

The auto-upgrade feature has also not been successful.

What are my options here? Is there a way I can have my cake and eat it too?

How can I even get Xojo to create an API v1 project at this point?

Show us the crash log.

Not sure how to get the crash log on Windows, but shortly before the Xojo IDE disappears, I get this dialog:

Well, you could just add a method with the right name and parameters to the right class and avoid the problem (as a workaround).

But otherwise, you’d need to ask the developer to make it compatible with the new version.
Or buy a copy with source code, so you can fix it yourself.

3 Likes

Add a method to App named SleepCurrentThread and in that method simply turn around and call the API2 equivalent (don’t know what that is, sorry).

2 Likes

@Christian_Schmitz and @Tim_Hare Thank you, that gives me a direction to work towards!

Unfortunately this component wasn’t available with source or I would have purchased it. I have reached out to the author though so we’ll see what happens. In the meantime I will begin adding translation methods to try to work around the issues. Cheers!

for the good search on this forum, what is this extension named ? and what does it do ?
may be there is another plugin that does the same and that is updated…
so that future users searching here can find it easier ?

That is the best way. He update the component and you just pay for the update to the current version of whatever 3rd party component you chose to include in your app.

By the error, looks like (but not sure) ActivityViewer – piDog Software

And as they offered a “lifetime license”, probably update fees are not due.

1 Like

except from the flicker-free on windows, this does not seems to be too difficult to re-write with xojo only ?

Seems it has more functionalities, I don’t know. Whatever. It seems “not hard to achieve” for most of the functionalities but some people like to buy blocks of solutions to avoid wasting time doing that themselves, maybe that’s the case or it does something not so easy we aren’t perceiving right now. Have in mind that the concept of easy/hard varies from user to user.

1 Like