Is there a way for me to affect the display of grid cells?
I have a grid attached to a datasource. One of the columns in the datasource is
"summary", which indicates that this row is a summary row, and I'd like to
highlight this with a different background colour.

I cannot though find an event that allows me to customise this, even to choose a
different cell type.

For the primary column, I've changed its background colour to be a gray, so it
looks "fixed", but customisation of rows seems to be lacking. Is this the case? Any
suggestions on how to achieve my purpose?

/Matthew Jones/

(I just realised that I used the British "customisation" and the USA "gray", so
please forgive such translation issues!)

Look at Grid and it's Columns collection - it does allow color and
control type changes.

Raul


On 7/31/2013 11:19 AM, (Matthew Jones) wrote:
> Is there a way for me to affect the display of grid cells?
> I have a grid attached to a datasource. One of the columns in the datasource is
> "summary", which indicates that this row is a summary row, and I'd like to
> highlight this with a different background colour.
>
> I cannot though find an event that allows me to customise this, even to choose a
> different cell type.
>

And can I find out how high a row is? I can get a RowCount, but to set the height
of the grid to match, I need the height. It appears to be there in the read-only
protected RowHeight, but it is not exposed.

/Matthew Jones/

Yes, but there is no event to modify it per-row. Or would it be safe to use the
dataset events? Seems pretty dodgy to me to adjust the columns of a grid as it
reads the dataset.

/Matthew Jones/

Matthew,

<< Is there a way for me to affect the display of grid cells?  >>

Not per-row, no.  I'll be working on this in an upcoming build, though.

Tim Young
Elevate Software
www.elevatesoft.com

>  It appears to be there in the read-only
> protected RowHeight, but it is not exposed.

I made it public, and it works. Would be nice to have this formally exposed,
perhaps with a value to indicate the header height or other chrome.

/Matthew Jones/

Tim,

> Not per-row, no.  I'll be working on this in an upcoming build, though.

That would be an important feature. I need it quite often. Please think
about adding it quite soon.

At the moment I create a html-table on the fly and load it into a TPage
component. (See attached screenshot). Just a workaround - but the look
and feel is not perfect and it flickers a lot when changing the content.

Another workaround would be to create a sort of grid by using panels.

Regards Uli

Matthew,

<<I
made it public, and it works. Would be nice to have this formally exposed,
perhaps with a value to indicate the header height or other chrome.
>>

I'd like to enlarge the rowheight of a TGrid and found this old post from you.
Do you mean, that you were able to change the grid's RowHeight? If so, can you give me a hint what you changed in the sources?

Thanks Uli

Uli Becker wrote:

> Do you mean, that you were able to change the grid's RowHeight? If
> so, can you give me a hint what you changed in the sources?

I can't remember the details, but you can just edit the framework
source to suit your needs.

> It appears to be there in the read-only protected RowHeight, but it
> is not exposed.

I would think that I just commented it out in the protected section,
and moved it to public. I tend to add comments with my initials so I
can repeat them.

After editing the framework, you must restart the IDE as it caches it.

And finally, I understand EWB version 2 will eliminate this need by
allowing more flexibility, when it is out.

--

Matthew Jones

Matthew,

> I can't remember the details, but you can just edit the framework
> source to suit your needs.
> I would think that I just commented it out in the protected section,
> and moved it to public. I tend to add comments with my initials so I
> can repeat them.

I was able to do that, but changing the value doesn't change the real
rowheight.

> And finally, I understand EWB version 2 will eliminate this need by
> allowing more flexibility, when it is out.

You are right - no need to workaround these issues. Let's hope that v
2.0 will come out soon.

Uli