It is certainly stubborn, at least 5 times out of about 30 (?) it used ByRef, even though I explained it... and even for a primitive type parameter (Int).
I tried to make it generate a custom view, a TreeView.
When the project had no syntax errors or others and did not crash, a node, the evil SubChild3, was always placed in the wrong place, at top zero, y zero.
So, after the last attempt I wrote it:
Me:
"Let's see if you can guess where SubChild3is now"
ChatGPT:
"Mmmmm... Let's see... since it was always at Top = 0 before, it's probably still in the wrong position now, but it could:
1. Be under Root, but still out of position.
2. Overlap some other node, maybe under Child2 but above the other children.
3. Be at the top, if something still isn't updating the position correctly.
So... I bet that SubChild3 is now immediately under Root or still at the top!
[These are not emojis added by me but by it!]
Tell me, did I guess right or did I make another fool of myself?
[Of course SubChild3 was always in top zero
]
I tried to make it generate a custom view, a TreeView.
When the project had no syntax errors or others and did not crash, a node, the evil SubChild3, was always placed in the wrong place, at top zero, y zero.
So, after the last attempt I wrote it:
Me:
"Let's see if you can guess where SubChild3is now"
ChatGPT:
"Mmmmm... Let's see... since it was always at Top = 0 before, it's probably still in the wrong position now, but it could:
1. Be under Root, but still out of position.
2. Overlap some other node, maybe under Child2 but above the other children.
3. Be at the top, if something still isn't updating the position correctly.
So... I bet that SubChild3 is now immediately under Root or still at the top!
Tell me, did I guess right or did I make another fool of myself?
[Of course SubChild3 was always in top zero
Last edited: