[Solved] Global Chr() problem

[BarryG]

The Global is outside of any conditional statements. The folding lines drawn are a bug that I've never reported.

Anyway, marking this as Solved because I think there must be a thread calling the variable before the Global line for it was reached.

[boddhi]

Looking at the image of your source, the 'folding line' beside the line numbers suggest that the Global has been declared within a conditional statement of some sort.

This is not always true. Particularly if you place a set of instructions inside the folding pair ";{" and ";}".

Code: Select all

;{ Procedures
Procedure A()
  [...]
EndProcedure

Global Variable

Procedure A()
  [...]
EndProcedure
;}

[DarkDragon]

The Global is outside of any conditional statements. The folding lines drawn are a bug that I've never reported.

Anyway, marking this as Solved because I think there must be a thread calling the variable before the Global line for it was reached.

Code: Select all

Debug Len(extdot$)

Check the length please to see whether the value has changed or write it into some file. Global is only for the compiler, there's no runtime interpretation of "Global". That means all code after the Global sees this variable as Global, all code before cannot. Make sure to use EnableExplicit and declare all variables.

[charvista]

I have never seen your screenshot, as it is apparently removed. [Edit: they appeared suddenly later ]
My thought:
If the debug uses a different font than your program, then chances are big that the debug font does not have the shape for that character, hence the emptiness.

[BarryG]

I used a MessageRequester too, and I tested with Len() for it. Null and 0 were the results.