HMGforum.com

- Fixed: WindowsVersion() function to recognize 'Windows 7'. Reported by Mustafá Lopez.

- Fixed: 'Cosmetic' problem with memo edit window in data-bound grid with Windows 7.

- Modified: Data-bound Grid.

* From this release filtered tables (set filter / set deleted / index...for) records can be modified and appended.

* All changes to the table (excepting delete and recall) will be always buffered.

* To commit the pending changes, the method 'Save' (Alt+S) must be used.

* To undo changes, the new method 'ClearBuffer' (Alt+U) must be used.

* When changes be made:

- New records will go to the end of the grid.

- If a key field is edited and its content changed, it will remain in its current position.

- If a field used in a filter expression is edited and its content changed, it will remain in place.

- 'Save' method, will cause that order and visibility of records be updated according new values committed to table.

- There will be separate 'Save' code for core RDDs and contrib ones. In this release you'll find three sections: 'Core',
'SqlMix' and 'PgRdd' ('SqlMix' and 'PgRdd' will be implemented in future releases).

- Fixed: Problem with 'Capture' method. Reported by Claudio.

- Modified: Fix on Textbox (introduced in 3.0.20) temporarily reverted (again) since it created new problems (more research is needed to solve the original problem without create 'colateral damage').

Download: site

Thanks a lot Maestro

Best Regards

--

Esgici

Thanks a lot Roberto, for this new release.

With best regards,

Roberto Lopez wrote: <...>
- Modified: Data-bound Grid.
<...>

There is a little error in the Grid samples from Grid.27 to Grid.33.

You must add the following line a the program start:
If this change is not made, you'll get an error in 'Set Value' test.

THX!

Hello Roberto,

thank you very much for the new release. The new behavior of the grid sounds like a good decision.

I am so excited for the sql-save-support.

Raumi

raumi75 wrote:Hello Roberto,

thank you very much for the new release. The new behavior of the grid sounds like a good decision.

I am so excited for the sql-save-support.

Raumi

This new way was inspired by your request about PostGre.

Having fully buffered edit and completely separate 'save' code for each contrib RDDs should make the support for those nice and easy... at least, I'll try to do so

Hello Roberto,

Thanks a lot for this version. Day by day, HMG is becoming my dream development platform, which I expected from VFP, but didn't get

Besides SQLMIX, there is a function, hb_dbcreatetemp(), which creates a temporary table. I hope, temporary table created with this function will also support buffered edit with grid

With best regards.

Sudip

Roberto Lopez wrote: This new was way inspired by your request about PostGre.

Having fully buffered edit and completely separate 'save' code for each contrib RDDs should make the support for those nice and easy... at least, I'll try to do so

I understand. After all there was no problem saving the data to pgrdd. Only refreshing the grid caused the problem. This way, you can save all content and then simply requery the data and fill the grid again. Very smart! Again, thank you for your work.

Raumi

raumi75 wrote: I understand. After all there was no problem saving the data to pgrdd. Only refreshing the grid caused the problem. This way, you can save all content and then simply requery the data and fill the grid again. Very smart! Again, thank you for your work.
Raumi

Besides that, I've concluded that the user experience is better, if sorting and visibility (index and filter) are updated when the user decides to do it, saving the changes to the table and giving him the choice to undo these changes for any RDD, not only SQL.

In the case that you want to experiment with Postgre RDD saving, you'll find a (currently empty) section for that in 'DataGridSave' procedure.

The buffer is simply an array (four elements per cell) containing: logical row, logical col, value and physical row.

For new (appended records) since it has not a physical row number yet, I assign negative count number to each new record.

So, the first record will have -1 as physical record number, the second -2 and so on.