Unexpected results when changing grid.cellHeight

I'm using the latest Plus update.
I have several grids that display expenses with grid.cellHeight = .55 and 
fontsize = 7 so I can get as many visible rows as possible.
The user has the option to change the Items column from entryfield to a 
combobox so they can select another item.
When it's a combobox it's hard to read when the cellHeight is set at .55 so 
I set it to change to cellHeight=.65.
(see code below)

Once the cellHeight is changed, a small slice of the text in the Items cell 
is separated from the rest of the text.
To fix this I've just set the cellHeight = .65 all the time but I thought I 
would report this in case it happens to be a bug.

if form.pmd.value
   form.BIDDER2DATAMODULE1.inv1.rowset.clearFilter()
   form.BIDDER2DATAMODULE1.inv1.rowset.indexName = "Item_Cat"
   form.itemsgrid3.columns["column1"].editorType = 4
   form.itemsgrid3.columns["column1"].editorControl.dropDownWidth =
30
   form.itemsgrid3.columns["column1"].editorControl.dataSource := ;
form.BIDDER2DATAMODULE1.inv1.rowset.fields["item"]
   form.itemsgrid3.columns["column1"].editorControl.dropDownHeight =
20
   form.itemsgrid3.cellHeight = .65
else
   form.itemsgrid3.columns["column1"].editorType = 1
   form.itemsgrid3.cellHeight = .55
endif
form.itemsgrid3.refresh()
form.itemsgrid3.setfocus()

Ted

 

I'm using Windows Vista and the newest Plus update 2.6.1.4 that just came 
out.
It did it before the update also. I was hoping this update would fix it.

Ted

"Geoff Wass [dBVIPS]" <gswassREMOVE_ME@attglobal.net> wrote in
message 
news:MPG.2258e257df11693498a046@news.dbase.com...
> In article <r1ihVFbkIHA.960@news-server>, tedfanderson@gmail.com
says...
>> I'm using the latest Plus update.
>> I have several grids that display expenses with grid.cellHeight = .55
and
>> fontsize = 7 so I can get as many visible rows as possible.
>> The user has the option to change the Items column from entryfield to
a
>> combobox so they can select another item.
>> When it's a combobox it's hard to read when the cellHeight is set at
.55 
>> so
>> I set it to change to cellHeight=.65.
>> (see code below)
>>
>> Once the cellHeight is changed, a small slice of the text in the Items

>> cell
>> is separated from the rest of the text.
>> To fix this I've just set the cellHeight = .65 all the time but I
thought 
>> I
>> would report this in case it happens to be a bug.
>>
>
> Ted,
>
> Are you using the latest version of dBASE PLUS (2.6.1.4 came out this
> week)? If not, give that a try. A lot of changes were made to the GRID.
>
> If this doesn't help, which version of dBASE are you using and on which
> version of Windows?
>
> -- 
> Geoff Wass [dBVIPS]
> Montréal, Québec, Canada
>
> .|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
> .|.|.| ---------------------------------------------------------- |.|.|.
> .|.|.|             IT Consultant http://Geoff_Wass.com            |.|.|. 

In article <r1ihVFbkIHA.960@news-server>, tedfanderson@gmail.com says...
> I'm using the latest Plus update.
> I have several grids that display expenses with grid.cellHeight = .55 and 
> fontsize = 7 so I can get as many visible rows as possible.
> The user has the option to change the Items column from entryfield to a 
> combobox so they can select another item.
> When it's a combobox it's hard to read when the cellHeight is set at .55 so

> I set it to change to cellHeight=.65.
> (see code below)
> 
> Once the cellHeight is changed, a small slice of the text in the Items cell

> is separated from the rest of the text.
> To fix this I've just set the cellHeight = .65 all the time but I thought I

> would report this in case it happens to be a bug.
> 

Ted,

Are you using the latest version of dBASE PLUS (2.6.1.4 came out this 
week)? If not, give that a try. A lot of changes were made to the GRID.

If this doesn't help, which version of dBASE are you using and on which 
version of Windows?

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

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.

In article <ti9oxOikIHA.960@news-server>, ted@battensplus.com says...
> I'm using Windows Vista and the newest Plus update 2.6.1.4 that just came 
> out.
> It did it before the update also. I was hoping this update would fix it.
> 
> Ted


Ted,

I'll have to let dBI handle this. I'm out of ideas.

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

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.

Hi Ted,

One of the fixes in 2.61.4 was to have the height of a the columnComboBox 
control match
the current grid.cellHeight.  Previoiusly, the columnComboBox's height was 
always the same
and did not change at all when the grid.cellheight was changed.

If you used a smaller grid.cellHeight than the default height, your 
columnComoBox's will
now match the smaller cellHeight which may cause the text in the 
columnComboBox to appear
partly hidden by the border of the columnComboBox.

> I'm using the latest Plus update.
> I have several grids that display expenses with grid.cellHeight = .55 and 
> fontsize = 7 so I can get as many visible rows as possible.
> The user has the option to change the Items column from entryfield to a 
> combobox so they can select another item.
> When it's a combobox it's hard to read when the cellHeight is set at .55 
> so I set it to change to cellHeight=.65.
> (see code below)
>
> Once the cellHeight is changed, a small slice of the text in the Items 
> cell is separated from the rest of the text.
> To fix this I've just set the cellHeight = .65 all the time but I thought 
> I would report this in case it happens to be a bug.

Just to be sure I'm understanding you correctly, are you saying that
changing the grid's cellHeight after the grid is visible on screen, results
in some incomplete repainting of the grid that appears to leave a slice of 
text
visible somewhere in the grid?

If yes, an alternative workaround is to try calling grid.refresh() to see if 
it repaints
the grid properly.

Can you post a screen shot showing the painting problem (to dbase.binaries) 
?
(Be sure to refer back to this thread from the binaries post).

Thanks,

- Marty -

Martin Kay
dataBased Intelligence, Inc.