Imagine my surprise when I learned that I'd accidentally redefined 0 to a string. I'd love for the interpreter to check that variables begin with non-numeric values like most languages do. Maybe underscore and letters?

Ah, gotcha. Thanks.

However, it seems kind of undesirable to let people create variables from numbers, doesn't it? Most languages impose limitations, even Basic does. Variables have to start with letters or underscores, that sort of thing. I'll add that to the feature requests.

Okay, I think I found the issue. I had a call to GetCurPos like this: GetCursorPos>X,Y,0 That's where it overwrites 0 with crIBEAM or CRNormal That's supposed to be the cursorType. I'm not using the function correctly apparently. I don't recall where I arrived at 0 for cursor type. Turns out I don't...

It is a bit frustrating dealing with line numbers. Is there any way I can see the line number of the file being included and not the whole conglomeration? For instance, my main routine has 300 lines, but I'm getting errors on line 600. It'd be more useful to know the line number of the included file...

Yes, I'll get to that today for you. There's a lot of stuff that will break like database stuff, applications you don't have, etc. Do you want the image files? I still can't reproduce it reliably, so I'm not sure I can tell you exactly how to do it. But hopefully I can spend some time experimenting ...

Actually, I do see something really weird and have no idea why this happening. A bunch of variables are being reassigned to: crIBEAM. Any idea what that is? Nothing I'm doing in my code, intentionally at least. TabX is set from reading a CSV file. There is 0 being assigned that weird value.

But the expression is:

If>NUMFOUND>0

Is it evaluating NUMFOUND to 1 and then evaluating 1 as 0?


Actually, it was 0 being reassigned. Gah!

BTW: Doing it with

If>NUMFOUND=1

That works. But last time I checked 1 is also > 0. Weird.

SRT>DropAnchor // Here's how this will work: // Compare current anchor with the last one. If it is different, then we need to scroll to top then scroll down N SetFocus>CurWindow Let>Img=SR_%Field%_Anchor Let>Msg=Field=%field% Img=%IMG% If>Img<>LastAnchor GoSub>Scroll2Top Let>N=SR_%Field%_Scroll GoS...

Here's an example of one of the weird things I'm experiencing. I "closed" up some of the functions in another file included by this file. Ran the program, hit a breakpoint, stepped through a bit of code and then hit the big red X to stop executing. I saw my main program file has overwritten my inclu...

Ah, gotcha. And if you're assigning a new variable the unset variable, what will the new variable be?

Let>NewVar=UnsetVar

If>NewVar={"UnsetVar"}
Boohiss
endif

How do you check if a variable exists? I see the assigned function, but I thought there was another way that's a bit less code.

This morning had a new symptom. In one of my include files I had hidden the top subroutine by pressing the '-' sign. Ran the program, it aborted due to an error. Then I went into my main program, with the Include statements, and it had been overwritten by the include file, including the closed subro...

That is cool. Glad I stumbled across this.

Okay, I could swear I tried that, but I guess not. Thanks!