Groups > dBase > dBase SQL Servers > Re: Lost effect of default Pushbutton




Lost effect of default Pushbutton

Lost effect of default Pushbutton
Thu, 3 Jan 2008 10:06:17 -0700
Since changing my program to run with Firebird it has lost the ability of 
pushbuttons to react to the default = true setting.  For instance, when a 
dialog window that has an OK button with default = true, normally pressing 
<enter> would have the same effect as clicking the OK button.  Now it 
doesn't have any effect and the mouse has to be used.  Has anyone else seen 
this?

Dain Lochridge 

Post Reply
Re: Lost effect of default Pushbutton
Thu, 3 Jan 2008 16:18:18 -0800
I agree with Andrew, others are using Firebird and have never complained of 
such a thing.
See below help for the CuaTab Setting.  This will cause the OK default 
button to be ignored.

CuaTab
Determines cursor behavior when you press Tab while a control has focus.

Property of

Browse, Editor, Grid

Description

When cuaTab is true, pressing Tab moves to the next control in the form's 
tab order. When cuaTab is false, pressing Tab moves to the next field in a 
Grid or Browse object or moves the cursor to the next tab stop in an Editor 
object.

The same applies to pressing Shift+Tab, except that the movement is in 
reverse.

"Dain Lochridge" <deloch@hotmail.com> wrote in message 
news:q0eVU2iTIHA.1304@news-server...
> Since changing my program to run with Firebird it has lost the ability of 
> pushbuttons to react to the default = true setting.  For instance, when a 
> dialog window that has an OK button with default = true, normally pressing

> <enter> would have the same effect as clicking the OK button.  Now it

> doesn't have any effect and the mouse has to be used.  Has anyone else 
> seen this?
>
> Dain Lochridge
> 

Post Reply
Re: Lost effect of default Pushbutton
Thu, 03 Jan 2008 23:19:04 +010
Dain Lochridge schrieb:
> Since changing my program to run with Firebird it has lost the ability of 
> pushbuttons to react to the default = true setting.  For instance, when a 
> dialog window that has an OK button with default = true, normally pressing

> <enter> would have the same effect as clicking the OK button.  Now it

> doesn't have any effect and the mouse has to be used.  Has anyone else seen

> this?

I really doubt that this can have anything to do with the database you 
Post Reply
Re: Lost effect of default Pushbutton
Fri, 4 Jan 2008 00:43:22 -0800
"Geoff Wass [dBVIPS]" <gswassREMOVE_ME@attglobal.net> wrote in
message 
news:MPG.21e7965790d8fb0b989dc8@news.dbase.com...
> In article <q0eVU2iTIHA.1304@news-server>, deloch@hotmail.com
says...
>> Since changing my program to run with Firebird it has lost the ability
of
>> pushbuttons to react to the default = true setting.  For instance, when
a
>> dialog window that has an OK button with default = true, normally 
>> pressing
>> <enter> would have the same effect as clicking the OK button. 
Now it
>> doesn't have any effect and the mouse has to be used.  Has anyone else

>> seen
>> this?
>>
>> Dain Lochridge
>>
>>
>>
>
> Dain,
>
> This is from the on-line help:
>
> The default property will only work when SET CUAENTER is set to ON. When
> CUAENTER is OFF, the Enter key emulates the Tab key and merely shifts
> focus to the next control.
>
> Do you have any SET CUAENTERs in your code and is yourProg.INI setup
> correctly in this regard?

Yes, Geoff is correct, my quick check in the online help revealed CuaTab. 
Kicking myself<g>

Greg Hill

Post Reply
Re: Lost effect of default Pushbutton
Fri, 4 Jan 2008 01:03:56 -0500
In article <q0eVU2iTIHA.1304@news-server>, deloch@hotmail.com says...
> Since changing my program to run with Firebird it has lost the ability of 
> pushbuttons to react to the default = true setting.  For instance, when a 
> dialog window that has an OK button with default = true, normally pressing

> <enter> would have the same effect as clicking the OK button.  Now it

> doesn't have any effect and the mouse has to be used.  Has anyone else seen

> this?
> 
> Dain Lochridge 
> 
> 
> 

Dain,

This is from the on-line help:

The default property will only work when SET CUAENTER is set to ON. When 
CUAENTER is OFF, the Enter key emulates the Tab key and merely shifts 
focus to the next control.

Do you have any SET CUAENTERs in your code and is yourProg.INI setup 
correctly in this regard?

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.
Post Reply
<< Previous 1 2 Next >>
( Page 1 of 2 )
about | contact