If I try to assign a value to a TGrid column that has its Visible property set to False, I get the following error message:  "Unable to get value of the property 'childNodes': object is null or undefined".

If I set the column's Visible property to True, I don't get the error.

Steve

Steve,

<< If I try to assign a value to a TGrid column that has its Visible
property set to False, I get the following error message:  "Unable to get
value of the property 'childNodes': object is null or undefined". >>

I think I already fixed this one for the next build (Chris Holland reported
it), but I will double-check.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

<< I think I already fixed this one for the next build (Chris Holland reported
it), but I will double-check.>>

Sorry, I did do a search first before starting a new thread but looks like I missed Chris's post.  Thanks Tim.

Steve

When I try to assign a value to a hidden column using ...
grdResults.Cells[7,1] := 'Red';
I get an error ...
"Unable to get value of the property 'attachment': object is undefined"

Also Hiding / Showing columns during runtime either with ...

 grdResults.Columns[7].Visible := cbxRadios.Checked;
or
 if cbxRadios.Checked =  True then grdResults.Columns[7].Show
 else grdResults.Columns[7].Hide;

results in a messed up grid for the columns in question. i.e. the column widths and grid lines go haywire. Is there a repaint command I need to call ?

EWB 103.1

> When I try to assign a value to a hidden column using ...
> grdResults.Cells[7,1] := 'Red';
> I get an error ...
> "Unable to get value of the property 'attachment': object is
> undefined"

You should be setting it in the underlying dataset I think. I don't know about the
grid, but perhaps marking the field not visible might work?

/Matthew Jones/

Yeah, still seems to be a problem with 1.03 B1.  I get this error now when trying to assign a value to a cell where the column is hidden: "TypeError: element is null".

<< You should be setting it in the underlying dataset I think. I don't know about the
grid, but perhaps marking the field not visible might work? >>

Matthew, that's no good in my case because I don't use the grid with datasets.  I populate the grids from a PHP app which retrieves the data from a MySQL database.

On 1/23/2014 8:03 PM, Steve Gill wrote:
> Matthew, that's no good in my case because I don't use the grid with datasets.  I populate the grids from a PHP app which retrieves the data from a MySQL database.

However if this works with dataset you could just populate the dataset
from your php.

Raul

> Matthew, that's no good in my case because I don't use the grid
> with datasets.

Sure, but you can use the dataset component directly, adding rows and putting data
in the columns. You don't need to do the server link.

/Matthew Jones/

<< Sure, but you can use the dataset component directly, adding rows and putting data
in the columns. You don't need to do the server link. >>

Thanks but I really don't feel like changing dozens of lines of code just to get around a bug with the column visibility.  We have built our own infrastructure for exchanging data and the solution is to rewrite everything?

<Steve Gill> wrote:
> << Sure, but you can use the dataset component directly, adding rows and putting data
> in the columns. You don't need to do the server link. >>
>
> Thanks but I really don't feel like changing dozens of lines of code just
> to get around a bug with the column visibility.  We have built our own
> infrastructure for exchanging data and the solution is to rewrite everything?

I don't know if it is a bug or what, but my understanding is that the grid
is supposed to get its data from (and be controlled by) a dataset (is that
the right name, not sure away from my computer). It is the natural way. If
changing a dozen lines is too much, then obviously the thing to to is to
look at the framework code and work out what the problem is, and then patch
the framework to fix it. I've dug into a few of the framework components,
and of course been able to identify exactly what the problem is and tell
Tim for a fix. I really like that the framework is EWB code and not some
horrible other javascript thing - makes it easy to modify or take ideas
from.

--
Matthew Jones