How to avoid pushbuttons when TApplication:lUseReturn == .T.?

[Mahanimann]

The TApplication:lUseReturn works fine, except that it jumps to- and sets
focus to pushbuttons. On the next K_ENTER the button is pushed, a behaviour
that I don't want (do anybody, at least when the form/dataset is in
EDIT-mode?)
So my question is: Suggestions on how to let K_ENTER only jump to
data-controls, not buttons etc? (No matter if the form/oDataSet are in VIEW
or EDIT-mode)
Thanks for any reply.
Paal

[ignacio]

Paal,
I am afraid that is not possible. I never liked the lUseReturn property. Now
you can see why.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:[email=470ac6e8@ozsrv2.ozlan.local...]470ac6e8@ozsrv2.ozlan.local...[/email]
> The TApplication:lUseReturn works fine, except that it jumps to- and sets
> focus to pushbuttons. On the next K_ENTER the button is pushed, a
> behaviour that I don't want (do anybody, at least when the form/dataset is
> in EDIT-mode?)
>
> So my question is: Suggestions on how to let K_ENTER only jump to
> data-controls, not buttons etc? (No matter if the form/oDataSet are in
> VIEW or EDIT-mode)
>
> Thanks for any reply.
> Paal
>

[NoName]

Paal,
I am afraid that is not possible. I never liked the lUseReturn property. Now
you can see why.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Mahanimann" <paaldalen@gmail.com> escribió en el mensaje
news:[email=470ac6e8@ozsrv2.ozlan.local...]470ac6e8@ozsrv2.ozlan.local...[/email]
> The TApplication:lUseReturn works fine, except that it jumps to- and sets
> focus to pushbuttons. On the next K_ENTER the button is pushed, a
> behaviour that I don't want (do anybody, at least when the form/dataset is
> in EDIT-mode?)
>
> So my question is: Suggestions on how to let K_ENTER only jump to
> data-controls, not buttons etc? (No matter if the form/oDataSet are in
> VIEW or EDIT-mode)
>
> Thanks for any reply.
> Paal
>

[Mahanimann]

> I am afraid that is not possible. I never liked the lUseReturn property.
> Now you can see why.
No, not really But I leave it for now, K_TAB *is* the Windows way so
I'll try to get used to it
Thanks for the reply.
Paal

[Mahanimann]

> I am afraid that is not possible. I never liked the lUseReturn property.
> Now you can see why.
No, not really But I leave it for now, K_TAB *is* the Windows way so
I'll try to get used to it
Thanks for the reply.
Paal

[notengo]

Mahanimann,
> The TApplication:lUseReturn works fine, except that it jumps to- and sets
> focus to pushbuttons. On the next K_ENTER the button is pushed, a behaviour
> that I don't want (do anybody, at least when the form/dataset is in
> EDIT-mode?)
I don't like the lUseReturn feature but you can try to play with
TButton:lTabStop and TButton:nModalResult (setting it to mrNONE).
Regards,
José Lalí­n

[notengo]

Mahanimann,
> The TApplication:lUseReturn works fine, except that it jumps to- and sets
> focus to pushbuttons. On the next K_ENTER the button is pushed, a behaviour
> that I don't want (do anybody, at least when the form/dataset is in
> EDIT-mode?)
I don't like the lUseReturn feature but you can try to play with
TButton:lTabStop and TButton:nModalResult (setting it to mrNONE).
Regards,
José Lalí­n

[Mahanimann]

> I don't like the lUseReturn feature but you can try to play with
> TButton:lTabStop and TButton:nModalResult (setting it to mrNONE).
Yes I have done that and it makes K_ENTER "miss" the buttons. But then
again the K_TAB also do that so I have startet to dislike lUseReturn myself.
Thanks,
Paal

[Mahanimann]

> I don't like the lUseReturn feature but you can try to play with
> TButton:lTabStop and TButton:nModalResult (setting it to mrNONE).
Yes I have done that and it makes K_ENTER "miss" the buttons. But then
again the K_TAB also do that so I have startet to dislike lUseReturn myself.
Thanks,
Paal