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

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.

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:

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.

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.

3 Likes

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.

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.

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.

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

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.

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.

1 Like

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

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).

You’re right: it’s AllowExpandableRows.

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

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

2 Likes

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.

2 Likes

I have found that Claude is helpful for identifying problems with my code, helping to fix bugs and making suggesitons for improvement. HOWEVER, I need to remind Claude that I am using Xojo 2025 v3, API 2 before i start. The best way I have found is to ask claude to generate a skill (ask Claude what that is), and then add that to itself. Then it remembers each time and behaves appropriately. It is also helpful to remind claude that iOS, MAcOs, Android and Web apps behave somewhat differently and give examples of the differences. You can also get Claude to update the skill whenever it finds a problem - something that should b einclided in included in the Xojo interface to Claude, if it is not there already.

1 Like

I started a new discussion with "Xojo 2025r3.1: ", and it returns Xojo code for God knows what (sometimes), but nearly always in the same discussion.
It is sorry, but I do not care.

Next time I will follow another path: I will ask for a design (fake code design): somethink like “I want to do this” (finality of the method) can you give me hints ?
Hoping to get “Open,” “read all”, “resize using the image ratio and resized to be displayed”, “display it”, “then save it as png”.

Hi Emile Schwarz!

I’m so sorry you’ve wasted your time with AI.

Let me share my experience. It’s worked for me.

Philip is on the right track.

Let me tell you that there are currently many courses that promise you code assisted by AI at incredible speeds. DON’T BELIEVE THEM.
When AI has the capacity to learn from the users, for example, with methods called SKILLS, it can improve over time. There will come a point when the likely answers will be very accurate, since the AI ​​learns from all its users.

My suggestion is not to discourage yourself. AI will greatly improve the answers and the ability to generate more and more.

The unfortunate thing is that it depends on the POPULARITY of a programming language. As long as users ask the AI ​​questions and there’s a group focused on teaching acceptable answers, it will continue to work. There can even be several answers to the same question.

Thank you José,

Gemini told me yesterday the inverse (I shared data collected from it / other parts of the internet / NOT Xojo related).

This may change as the Engineers works on the subject.

I will test that with data I already shared a month or to ago (Still not Xojo related).

I will not. I will only continue to use it as a reminder when I forgot how to do something / when needed.

Recently, I asked Gemini how do do this:

With a bit of work, it is OK / I do not take time - yet - to implement it…

1 Like