Hi Karl-Heinz,
Karl-Heinz wrote:i entered 'Activate screen' in the command window, but the '?' output is still not visible. Anyway, for the moment 'Set Alternate' does what i need.
Yupp, "Activate Window Screen"
alone is not enough... Yesterday I was debugging and ? went once to screen - which resulted in me kicking off the post, but checking no further. Came home today, tried a few variations and am now even more puzzled - currently ? output sometimes gets output, BUT OFTEN NOT to screen/form I expect from reading code and props - I must be getting old or debugger throws off internal timing and I need to sprinkle DoEvents inside....
Sigh - the original code was meant to be run inside other app sometimes puzzles, as some of the scetions might make sense in such surroundings. Slooow work, but as _screen.Print, my function with many parameters AND set alternate work (even if not as comfortable as used), I will get there.
First I will try to reactivate the classlib I deleted due to it referring a totally missing other classlib - perhaps this clears some things up. Vcx hacking again...
btw. There´s a FoxConsole.ini, but it seems the values are ignored ? i ve tried these settings but they have no effect.
CompileOnSave=.T.
SaveCmdText=.F.
the names suggest that:
- The source code is automatically compiled -> but it doesn ´t happen.
- The values entered in the command window are not added to the vRunFoxCmd.txt -> but they are still added.
This
might stem from elsewhere and not be related to the FoxRun.Exe, as this has that .cfg file. Will step through load and watch if/when this is accessed or written
Keep them coming - I'll work more on it later, but have other pressing stuff. Hope you are enjoying vfp9!
regards
thomas