XamlSpreadSheet events on user cell value (Cell value range) changed

Status: New

Tomas B Fri, Dec 11 2020 5:22 AM

Hello,

We want to keep track of changes made to the XamSpreadsheet-data to enable an external save button if necessary.

That includes the following ways to change data:

Manual changes from the user
Changes via the Context Menu
Changes via shortcuts (clipboard with one or multiple cells)

Currently there is no singular event to support this requirement. Keeping track of the changes is currently (to my knowledge) possible in two ways:

Convert the data and compare the raw values for any changes (which is expensive for larger Spreadsheets).
Use the existing events:
- EditmodeExiting-Event
- and CommandExecuting-Event
  - Get new value from Clipboard and parse it to match the cells (for paste event)
  - check against current values if data gets changed through the action.

We suggest an event that gets triggered when data or format changes in the Spreadsheet containing the changed cells including previous and current value as well as address of cell. This also should be capable to deal with ranges so only 1 event received for paste on multiple cells is used.

For use this is more a bug than a feature since save button state cannot be determined with existing implementation or have to use events which are triggered very often (with scrolling) which results in slow performance of big files due comparison detection in our code.

XamSpreadsheet

Offline Tomas B over 3 years ago in reply to Brian Lagunas
Hi Brian Lagunas,

Thank you for your suggestions. We already tried both solutions and they did not fill our needs.

To your suggestions:
- WorkbookDirtied Event: This was the first event we tried to use since the name suggested that this is exactly what we want, however this event also gets triggered for example when the user starts scrolling through the excel-worksheet (If I had to guess it is probably due to some internal lazy loading) and we don´t want to enable the safe-button just because the user is scrolling and no data changed. Since the additional information that come with this event are very generic and say nothing towards the actual change that triggered the event, this event cannot be used to determine the save-button enabling.SpreadsheetMinimalPrototype.zip
These answers are of course based on our limited knowledge with the events. If we missed a crucial point you are very welcome to point it out to us, we would be happy if there is already an existing and simple solution for our problem in the product.

I attached a minimal prototype with which you can verify our problems. If you start scrolling the WorkbookDirtied-Save button gets enabled (though it should not) and if you paste a value the EditModeExiting-Save button does not get enabled (though it should).
- Cancel
- Up 0 Down
- More
- Cancel
Offline Brian Lagunas over 3 years ago

If you are only wanting to know when to enable/disable your save button, why are you trying to compare the data? It would be safe to assume that if the EditModeExiting event fired, something was edited and therefore you should turn on your HasChanges flag which would enable the save button. Also, have you tried the WorkbookDirtied event? This event is invoked when a change has been made to the workbook that might require a save.
- Cancel
- Up 0 Down
- More
- Cancel