Mathew:

I'm with Steve on this.  That notion, that the grid is suppose to gets its data just from a Dataset, is silly, otherwise, why would it be permitted to use it without one.

Another bug with the 1.03 Grid, if you set a column to Visible False and then back to Visible True - it doesn't bring it back properly - it messes up the grid, doesn't paint properly.  

With or without a dataset.....

Walter

<Walter Matte> wrote:
> Mathew:
>
> I'm with Steve on this.  That notion, that the grid is suppose to gets
> its data just from a Dataset, is silly, otherwise, why would it be
> permitted to use it without one.

Okay, I am quite likely wrong. I tend to make my own pretty grid from
panels as I like to have large text and small detail text in the same rows.

--
Matthew Jones

Phillip,

This is now fixed.  The issue, in general, was that there was a logic error
introduced in 1.03 for the non-visible grid columns - the cell elements were
being removed to conserve memory, but that's a no-no because they are needed
to store the data, among other things.  At any rate, it makes the whole
grid logic much, much easier to deal with, so the change was an improvement.

Tim Young
Elevate Software
www.elevatesoft.com

Walter,

<< Another bug with the 1.03 Grid, if you set a column to Visible False and
then back to Visible True - it doesn't bring it back properly - it messes up
the grid, doesn't paint properly. >>

This is fixed now also.  See my reply to Phillip in this thread as to the
cause.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim.

Thanks for the build 2 update. It is an amazing product and much better than working with ASP.net and Oxygene.
Writing to a read only column seems to work fine now.
However showing and hiding columns I still get an "DOM Exception: NOT_FOUND_ERR (8)
when trying to show the columns again IF the columns are right next to each other.
e.g.
 grdResults.Columns[7].Visible := cbxRadios.Checked;
//  grdResults.Columns[8].Visible := cbxRadios.Checked;
 grdResults.Columns[9].Visible := cbxRadios.Checked;
// grdResults.Columns[10].Visible := cbxRadios.Checked;
 grdResults.Columns[11].Visible := cbxRadios.Checked;
// grdResults.Columns[12].Visible := cbxRadios.Checked;
works OK, but taking out the comment characters and including columns 8, 10, or 12 will give an error.
Again doesn't matter if Visible or Hide & Show are used.

Sorry that should have been "Writing to a non-visible column seems to work fine now".

PhillipH:

I have a test program that Hides and Shows columns.  In 1.03B1 is did not redraw, but it works fine with 1.03B2.  The columns change properly to invisible and visible again - with a small redraw error in the Header if the column is sorted.  But it works.

Do you have a small test program - you should email it to Tim, or submit it via an incident report.

Walter

PhillipH:

OK - I see - if you do two columns beside each other and Hide them - they Hide fine.

They will not SHOW.

// Hide Works
procedure TfrmSelSearch.Button1Click(Sender: TObject);
begin
 grdSearch.Columns.Column[1].Hide;
 grdSearch.Columns.Column[2].Hide;
end;

// SHow does not - but if you only Hide [1] - then Show Works
procedure TfrmSelSearch.Button2Click(Sender: TObject);
begin
 grdSearch.Columns.Column[1].Show;
end;


Walter

PhillipH wrote:

Work Around - Unhide them from RIGHT to LEFT - it works!


grdResults.Columns[12].Visible := cbxRadios.Checked;
grdResults.Columns[11].Visible := cbxRadios.Checked;
grdResults.Columns[10].Visible := cbxRadios.Checked;
grdResults.Columns[9].Visible := cbxRadios.Checked;
grdResults.Columns[8].Visible := cbxRadios.Checked;
grdResults.Columns[7].Visible := cbxRadios.Checked;


Walter