Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 581517

Summary: Avoid firing event if already hidden
Product: [Technology] NatTable Reporter: Dirk Fauth <dirk.fauth>
Component: CoreAssignee: Dirk Fauth <dirk.fauth>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 2.0.5   
Target Milestone: 2.1.0   
Hardware: PC   
OS: Windows 10   
See Also: https://git.eclipse.org/r/c/nattable/org.eclipse.nebula.widgets.nattable/+/199868
https://git.eclipse.org/c/nattable/org.eclipse.nebula.widgets.nattable.git/commit/?id=0623a5759bd79e4a8cce3c07ba6bf8baac1ae6df
Whiteboard:

Description Dirk Fauth CLA 2023-02-13 05:49:20 EST
With 2.0 the HideColumnByIndexCommand and the HideRowByIndexCommand where introduced. The handling of hiding columns or rows was simple in the past, as only visible columns/rows could be hidden via the user interface. With the introduction of the mentioned commands, it is now also possible to fire commands for already hidden indexes.

In such cases the resulting event should be either only fired for the affected columns/rows or there should be no event at all, if no column/row was affected.
Comment 1 Eclipse Genie CLA 2023-02-13 05:50:53 EST
New Gerrit change created: https://git.eclipse.org/r/c/nattable/org.eclipse.nebula.widgets.nattable/+/199868
Comment 3 Dirk Fauth CLA 2023-03-31 03:45:25 EDT
Fixed with 2.1.0