Mensaje
De
29/11/2006 02:51:41
Walter Meester
HoogkarspelNetherlands
 
 
a
28/11/2006 12:39:22
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
General information
Foro:
Visual FoxPro
Category:
Problemas
Título:
Environment versions
Visual FoxPro:
VFP 7 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
ID de la conversación:
01172633
ID del mensaje:
01173148
Views:
16
Hi dragan,

Thanks for your reply, but I can't help there still is a bug.

See details of my case.

It occurs when SET STATUS ON (as oposed to SET STATUS BAR ON) and only when there is code in the init of the form.

I can't see the relation to your situation below. I'm not using ?? anywhere in my program and SET TALK is set to off, so there should be no output to the form anyways. It prevents the form being instatiated to appear but is listed in the windows menu, while other forms continue to work as advertised.

I can't see why the behaviour should occur with SET STATUS ON and not with SET STATUS BAR ON

It certainly is a bug in my eyes. It was VERY difficult to track on what is going on here.

Walter,






>>Hi aleksey, it is a bug. see my message at BUG: CTRL+S misbehaviour Thread #1121615 Message #1121615
>>
>>I send it to you, but never got a reply from you.
>
>Look up my reply in that thread. This behavior of Ctrl+s is somewhere deep in the bowels of the OS - and fixing that there would actually screw things up elsewhere.
>
>As Aleksey said, "in this scenario" - it means (IMO) that the ? command is doing a console-type output, and that's where the behavior applies. You can't possibly expect that the mechanism of console output would be written from scratch, not to use any of system services, to prevent the behavior of ctrl+s to toggle scrolling on/off. I wouldn't expect that to be touched ever, it's too deep in old code.
Previous
Next
Responder
Mapa
Ver