Rectangle and Black Only Foreground.

In dBase PLUS 2.6.1.2 and .3, the foreground color remains black regardless 
of the coded color. If the background is also black, the coded text does not 
appear (black on black). My app uses white on black rectangles with buttons 
superimposed as an opening screen. The only workaround I have found is to 
lay a White on Black TexLabel to identify the rectangle. Having black text 
showing up in rectangles throughout the system makes the workaround a 
cumbersome alternative.

To reproduce, place a rectangle control on a form and set the colorNormal 
porperty to white on black. There does not appear to be a Theme property for 
rectangles.

Rectangle colors appear as coded in versions prior to point 2 or 3. So my 
workaround so far is to stay with 2.6.1.1. The grief with comboboxes not 
dropping down when given focus (in certain instances) is the other reason I 
stay with 2.6.1.1. It appears that with the new properties given us such as 
selectAll, the dropDown property has been messed with somehow. Combos always 
drop down as coded in 2.6.1.1.

Thanks.

Bob Buchanan
www.rvspacemanager.com 

Hi Bob,

> In dBase PLUS 2.6.1.2 and .3, the foreground color remains black 
> regardless of the coded color. If the background is also black, the coded 
> text does not appear (black on black). My app uses white on black 
> rectangles with buttons superimposed as an opening screen. The only 
> workaround I have found is to lay a White on Black TexLabel to identify 
> the rectangle. Having black text showing up in rectangles throughout the 
> system makes the workaround a cumbersome alternative.
>
> To reproduce, place a rectangle control on a form and set the colorNormal 
> porperty to white on black. There does not appear to be a Theme property 
> for rectangles.

Okay - are you saying that the problem is that the Text on your rectangle is 
not White
and is, therefore, difficult to read?

If thats the case, the next release will allow you to fix this easily as a 
systemTheme property
has been added to all form controls in 2.61.4 which is approaching final 
beta test now.

> Rectangle colors appear as coded in versions prior to point 2 or 3. So my 
> workaround so far is to stay with 2.6.1.1.

Okay.

>The grief with comboboxes not dropping down when given focus (in certain 
>instances) is the other reason I stay with 2.6.1.1. It appears that with 
>the new properties given us such as selectAll, the dropDown property has 
>been messed with somehow. Combos always drop down as coded in 2.6.1.1.

Are you refering to the autoDrop property?
If yes, we did alot of work on that to ensure that it worked reliably for 
2.61.2 and .3.

In fact, in earlier versions the autoDrop behavior was very unreliable.
Either a combobox would open multiple times upon receiving focus and then 
close
or sometimes, it would require more than one mouse click to open it.

Have you added code to try and force the dropdown to open, such as by
calling onSetFocus() or stuffing the keyboard buffer?
If yes - you should remove any such code and retest it.

Please email me or post in a newsgroup message a form that illustrates the 
problem.
You are the first person to report any autodrop issues with the combobox 
since 2.61.2 shipped.

Prior to that we had numerous complaints about autodrop.

Thanks,

- Marty -

Martin Kay
dataBased Intelligence, Inc.

Hi Marty -- sorry for the delay in getting back to you. The two problems I 
mention are not happening in V 26.1 -- so have continued usage with that and 
have be very busy. My application deals with RV Parks and Campgrounds - so 
in the spring, Northern parks are opening and wanting reservation software. 
The opposite happens in the early fall.

The Rectangle Problem is OK now in V Point 4 -- by setting the systemTheme 
to false. That was not necessary in Point 1. In 2 and 3 it did not work at 
all. The only forground color available is Black.

The autoDrop property problem still exists in Point 4. Well, it's a little 
better. In Version Point 2 or 3, the combobox would not autoDrop, and when 
clicked, would not stay dropped. So a selection could not be made. It now 
will drop if clicked and a selection "can" be made.

I will try to create a test for you to pound on. It's in a pretty complex 
part of my system so will have to eke out some code that will make it 
happen. Just creating a simple combobox with autoDrop works -- but the way I 
am using it -- it does not.

In the meantime, I will stay with Version 26.1, because both of the above 
items work just fine.

Bob Buchanan
www.rvspacemanager.com

"Marty Kay" <mkay@databi.com> wrote in message 
news:T9ixCwihIHA.636@news-server...
> Hi Bob,
>
>> In dBase PLUS 2.6.1.2 and .3, the foreground color remains black 
>> regardless of the coded color. If the background is also black, the
coded 
>> text does not appear (black on black). My app uses white on black 
>> rectangles with buttons superimposed as an opening screen. The only 
>> workaround I have found is to lay a White on Black TexLabel to identify

>> the rectangle. Having black text showing up in rectangles throughout
the 
>> system makes the workaround a cumbersome alternative.
>>
>> To reproduce, place a rectangle control on a form and set the
colorNormal 
>> porperty to white on black. There does not appear to be a Theme
property 
>> for rectangles.
>
> Okay - are you saying that the problem is that the Text on your rectangle 
> is not White
> and is, therefore, difficult to read?
>
> If thats the case, the next release will allow you to fix this easily as a

> systemTheme property
> has been added to all form controls in 2.61.4 which is approaching final 
> beta test now.
>
>> Rectangle colors appear as coded in versions prior to point 2 or 3. So
my 
>> workaround so far is to stay with 2.6.1.1.
>
> Okay.
>
>>The grief with comboboxes not dropping down when given focus (in certain

>>instances) is the other reason I stay with 2.6.1.1. It appears that with

>>the new properties given us such as selectAll, the dropDown property has

>>been messed with somehow. Combos always drop down as coded in 2.6.1.1.
>
> Are you refering to the autoDrop property?
> If yes, we did alot of work on that to ensure that it worked reliably for 
> 2.61.2 and .3.
>
> In fact, in earlier versions the autoDrop behavior was very unreliable.
> Either a combobox would open multiple times upon receiving focus and then 
> close
> or sometimes, it would require more than one mouse click to open it.
>
> Have you added code to try and force the dropdown to open, such as by
> calling onSetFocus() or stuffing the keyboard buffer?
> If yes - you should remove any such code and retest it.
>
> Please email me or post in a newsgroup message a form that illustrates the

> problem.
> You are the first person to report any autodrop issues with the combobox 
> since 2.61.2 shipped.
>
> Prior to that we had numerous complaints about autodrop.
>
> Thanks,
>
> - Marty -
>
> Martin Kay
> dataBased Intelligence, Inc.
>
>
>
>
>