Will converting to API 2 be mandatory in next future?

[Arnaud_N]

@Paul_Lefebvre

If you really want to stick with Desktop API 1, I think these steps might be helpful for some of you:

I, for one, thanks Xojo of providing these steps, and others hints which show that API 1 is still available and somewhat supported by Xojo.
I fail to see how these efforts can’t appease anyone who bothered about the move to API 2.

[Arnaud_N]

@Thom_McGrath

Str is an odd one because the expanded version would be String, which isn’t acceptable. Format already exists, so their options for renaming were pretty limited.

ToString(), AsString(), StringValue(), StringFrom(), FromString(), …
I can see a lot of choices.

[Rick_Araujo]

@Sam_Rowlands

I found the moment you save the project, it loses the API 1.0, so the next time you open it. it’s API 2.0 only.

Switching editing autocomplete modes during the edition could be great. Defaults to API 2 when opening a project, but with something like alt+E 1 and alt-E 2 (⌥E1 ⌥E2 for mac) we could go back and forth.

[Bob_Keeney3 (Bob Keeney)]

For those that want to force the API 1 to always show in the AutoComplete open the Xojo prefs file and make sure the key “Show Deprecated Autocomplete Items” is set to true. That should allow you to continue seeing API1 calls in autocomplete in newer versions of Xojo. This isn’t exposed in the IDE preferences (I think it should be).

[Tim_Parnell]

I peeked out of curiousity and this is super easy to do with @Thomas_Tempelmann’s Prefs Editor

[Bill_Heavens]

Are there other settings that are not exposed?

[Thomas_Tempelmann]

Now wait a minute here, buddy. Why is that app working in Dark Mode??

[Tim_Parnell]

Because you got Dark Mode mostly working, my job is the Hex editor

[John_McKernon]

Wow, hip, hip, hooray! Many, many thanks to @Bob_Keeney3, @Tim_Parnell, and @Thomas_Tempelmann for unlocking the secrets of this non-obvious but blindingly useful option and making it so easy to do

[Louis_D]

On Windows, the preferences are found in the registry, in HKEY_USERS. Using Regedit, search in keys for Xojo as a full word . Set the value of to 1 in order to see deprecated autocomplete.

[TimStreater]

For macOS, I found it in:

/Users/tim/Library/Preferences/

and I can change it with a text editor. Not that I need to, as I’m API2 only now, but it’s good to know what is stored there.

[Tim_Hare]

So would a quick fix be for Xojo to expose that item in preferences? Is there a feedback item? @Paul_Lefebvre?

[Anthony_G_Cyphers]

Should definitely be a preference we can set in the IDE if the recommendation is to wait for project conversion until needed. I’ve personally been converting things as I come to them, but I know many others aren’t doing that.

[Julia_Truchsess]

@Beatrix_Willius

the change of Paint to Paintering

PaintAt()

Edit: I see someone beat me to it, sorry

[Jerry_Fritschle]

@Julia_Truchsess

@Beatrix_Willius

the change of Paint to Paintering

PaintAt()

Edit: I see someone beat me to it, sorry

For double-buffering, it’s

PaintAt(TwoCoats as Boolean)

[Thomas_Tempelmann]

Uh, you shouldn’t change preferences (.plist) files directly in macOS, because the system (cfprefsd) keeps a cached version of the prefs and may overwrite your file changes. That’s why I made Prefs Editor. Or use the “defaults” Terminal command.