Can I suggest to restore Xailer's focus right before a "F9" (or mouse
clicked "Execute")
Let me explain :
After a F9, the focus of Xailer will rest on
- the "RIGHT MOST" tabs of "Code Editor" & on the "Form" that one had
"EVER" touched. (Am I correct with this observation ?)
For Example, if I have 1.prg ... 5.prg opened (in sequence)
If I had ever focused on 5.prg's Form, the focus will always be on
5.prg's Form no matter where I press F9 (Compile & Run)
ie. If I happened to go to 1.prg (modified the code ....) and then F9,
the focus will be back on 5.prg after the execution.
Is this behaviour configable ?
Thanks
David
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Xailer's IDE's focus after a F9
-
- Mensajes: 257
- Registrado: Mié Jul 19, 2006 8:48 am
Xailer's IDE's focus after a F9
David,
It seems that the problem is about the visible forms when you press F9. I
explain: if you have several forms visible when pressing F9, all of those
are hidden before executing the program. After program finishes, Xailer
restores all windows to their previous state, that is, making visible those
that were visible at beginning. This causes the code editor to change to the
corresponding tab of that form, one by one, and finally, the code editor
shows the tab corresponding to the last form been shown.
We'll review it ASAP. Thanks for the info. As a workaround, you could hide
the forms (pressing F12) you were not working on, so Xailer will not try to
make them visible nor will change the code editor to its corresponding tab.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
It seems that the problem is about the visible forms when you press F9. I
explain: if you have several forms visible when pressing F9, all of those
are hidden before executing the program. After program finishes, Xailer
restores all windows to their previous state, that is, making visible those
that were visible at beginning. This causes the code editor to change to the
corresponding tab of that form, one by one, and finally, the code editor
shows the tab corresponding to the last form been shown.
We'll review it ASAP. Thanks for the info. As a workaround, you could hide
the forms (pressing F12) you were not working on, so Xailer will not try to
make them visible nor will change the code editor to its corresponding tab.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
Xailer's IDE's focus after a F9
David,
It seems that the problem is about the visible forms when you press F9. I
explain: if you have several forms visible when pressing F9, all of those
are hidden before executing the program. After program finishes, Xailer
restores all windows to their previous state, that is, making visible those
that were visible at beginning. This causes the code editor to change to the
corresponding tab of that form, one by one, and finally, the code editor
shows the tab corresponding to the last form been shown.
We'll review it ASAP. Thanks for the info. As a workaround, you could hide
the forms (pressing F12) you were not working on, so Xailer will not try to
make them visible nor will change the code editor to its corresponding tab.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
It seems that the problem is about the visible forms when you press F9. I
explain: if you have several forms visible when pressing F9, all of those
are hidden before executing the program. After program finishes, Xailer
restores all windows to their previous state, that is, making visible those
that were visible at beginning. This causes the code editor to change to the
corresponding tab of that form, one by one, and finally, the code editor
shows the tab corresponding to the last form been shown.
We'll review it ASAP. Thanks for the info. As a workaround, you could hide
the forms (pressing F12) you were not working on, so Xailer will not try to
make them visible nor will change the code editor to its corresponding tab.
--
Regards,
Jose F. Gimenez
http://www.xailer.com
-
- Mensajes: 257
- Registrado: Mié Jul 19, 2006 8:48 am
Xailer's IDE's focus after a F9
Jose F. Gimenez wrote:
> David,
>
> It seems that the problem is about the visible forms when you press F9. I
> explain: if you have several forms visible when pressing F9, all of those
> are hidden before executing the program. After program finishes, Xailer
> restores all windows to their previous state, that is, making visible those
> that were visible at beginning. This causes the code editor to change to the
> corresponding tab of that form, one by one, and finally, the code editor
> shows the tab corresponding to the last form been shown.
>
> We'll review it ASAP. Thanks for the info. As a workaround, you could hide
> the forms (pressing F12) you were not working on, so Xailer will not try to
> make them visible nor will change the code editor to its corresponding tab.
>
Great workaround suggestion, less confusing now. I hope I won't forget it.
Thanks.
David
> David,
>
> It seems that the problem is about the visible forms when you press F9. I
> explain: if you have several forms visible when pressing F9, all of those
> are hidden before executing the program. After program finishes, Xailer
> restores all windows to their previous state, that is, making visible those
> that were visible at beginning. This causes the code editor to change to the
> corresponding tab of that form, one by one, and finally, the code editor
> shows the tab corresponding to the last form been shown.
>
> We'll review it ASAP. Thanks for the info. As a workaround, you could hide
> the forms (pressing F12) you were not working on, so Xailer will not try to
> make them visible nor will change the code editor to its corresponding tab.
>
Great workaround suggestion, less confusing now. I hope I won't forget it.
Thanks.
David
-
- Mensajes: 257
- Registrado: Mié Jul 19, 2006 8:48 am
Xailer's IDE's focus after a F9
Jose F. Gimenez wrote:
> David,
>
> It seems that the problem is about the visible forms when you press F9. I
> explain: if you have several forms visible when pressing F9, all of those
> are hidden before executing the program. After program finishes, Xailer
> restores all windows to their previous state, that is, making visible those
> that were visible at beginning. This causes the code editor to change to the
> corresponding tab of that form, one by one, and finally, the code editor
> shows the tab corresponding to the last form been shown.
>
> We'll review it ASAP. Thanks for the info. As a workaround, you could hide
> the forms (pressing F12) you were not working on, so Xailer will not try to
> make them visible nor will change the code editor to its corresponding tab.
>
Great workaround suggestion, less confusing now. I hope I won't forget it.
Thanks.
David
> David,
>
> It seems that the problem is about the visible forms when you press F9. I
> explain: if you have several forms visible when pressing F9, all of those
> are hidden before executing the program. After program finishes, Xailer
> restores all windows to their previous state, that is, making visible those
> that were visible at beginning. This causes the code editor to change to the
> corresponding tab of that form, one by one, and finally, the code editor
> shows the tab corresponding to the last form been shown.
>
> We'll review it ASAP. Thanks for the info. As a workaround, you could hide
> the forms (pressing F12) you were not working on, so Xailer will not try to
> make them visible nor will change the code editor to its corresponding tab.
>
Great workaround suggestion, less confusing now. I hope I won't forget it.
Thanks.
David