AI: it refuse to stop using the old API while giving me its answer

AI
1

I asked an AI from a large group (not a startup), and after 30 minutes it continue to gives me pre-2019 API code when I stated Xojo 2025r3.1.

So, I gave up and I will do something completely different.

That is what happens when facing a stuborn machine.

I wanted to copy/paste its answers to speed up the process to see if my idea is good / does not lead in a too complex code/design/whatever.

PS: AI does not know it does not know; I had many instances - not Xojo related - when it gaves me wrong answers and I send it proof of that.
Sometimes I am asking me if some of its sources have wrong (on purpose ?) information.
I now have to do something else and let the graphical interface I had in mind (different than the current implementation) and try to concentrate on something else. Tomorrow will be a different day.

2

If even AI can’t make the transition from API1 to API2, just imagine how difficult and frustrating it must be for a human developer. Oh… wait a minute… :face_with_raised_eyebrow:

3

Unfortunately, I understand how hard it is for the average Xojo developer (knowing its average age: this is mine too !).

In short and clear: this transition is learning a new language without helping tools, with less than optimum (human) memory.

In the above case, the human I am was asking myself “What is this instruction” (Ex. Instruction to set the AllowHierarchical Row to True, AddRow top instead of AddFolder… of course I forgot these names) when I copy/paste provided code and get confirmation by Xojo at reading error times.
NB: I have not done anything constructive since 14h00 this afternoon, time I started to poll the AI.

4

In the beginning, yes.
These days, I don’t remember API1 terms anymore so it’s just a matter of time before you use API2 fully (or mostly fully, as not everything has a replacement).
AI, on the other hand, won’t forget API1.

2 Likes
5

Its not.

API2 was a well-intentioned but badly implemented change, and everyone knows about the fallout.

Right now, my projects offer me both API1 and 2 terms in the autocomplete.

At some point, it’s caused me to have both terms in my code despite my efforts to resist the changeover.

I find it hard to guess which terms are which, and don’t want to switch due to fears about changing indices causing hard to trace bugs.

6

Two more info:

a. Original API disappeared from the Documentation / the AutoComplete (for new project / project saved with > 2019 IDEs,

b. AI gave unknow instructions (forget or unknow to me, but I understand what it means) or fantasy instructions (that are used elsewhere).

Usually, I ask an AI because either I forget how to do or I need to get an advice on how to do it (first time I have to do that).
This time it was to know how to do / if it is not too complex to implement that new graphic interface I had in mind instead of asking here.

7

You can still activate the old API1-items for autocomplete in new projects. Just check the Options/Preferences under Coding/Autocomplete.
Did AllowHierarchicalRow ever exist in API 1? It does not show up.

You also could use Claude Code for complete coding. It seems well aware of API 2.

8

No. Those properties that begin with “Allow…” are all API2. That’s one change I continue to hate.

9

As is, I would say AllowHierarchicalRow does not exists in Xojo (but somewhere else or AI hallucinates).

Or, it’s the name of a Property you can only set in the IDE; OR…

The way the AI want to add a Hierarchical Row is strange… It uses .AddRow, then want to set a Hierarchical Property for that Row.

10

Gemini knows about the current API.

I suspect Google does not likes the free mode and do whatever is possible to motivate its users to take a paid subscription. THAT is IMHO.

11

True, but it still mixes API1 and API2 with about any answers.

12

Gemini too knows about API 2.

And it mix code (Xojo and certainly other code) in its answers…

Not a prime time help (excepted if paying customer says otherwise).

13

You’re right: it’s AllowExpandableRows.

14

I certainly disagree with this. I am very grateful to API2. In my opinion, it has made the language clearer. I transitioned to API2 early and have not had difficulty with it. Whatever the “fallout”, for me, it has been a vast improvement.

3 Likes
15

That’s good. I won’t rehash all the old discussions, pleased it is working well for you.

2 Likes
16

Or… bear with me here… generative AI just generates random noise until that random noise could be classified by its pattern recognition engine as matching the request.

1 Like