Now that the UI is responsive enough, we should switch to enabling selection based on mouseenter, which is a blocker for some important interaction features (see below). This may require significant redesign on on the JavaScript/HTML side as my earlier experiment with this didn’t seem to work well – I think the issue what that the root div is rebuilt every time the selection state changes, and when an element is rebuild under the mouse, it re-triggers mouseenter. But more investigation required.
Now that the UI is responsive enough, we should switch to enabling selection based on
mouseenter, which is a blocker for some important interaction features (see below). This may require significant redesign on on the JavaScript/HTML side as my earlier experiment with this didn’t seem to work well – I think the issue what that the rootdivis rebuilt every time the selection state changes, and when an element is rebuild under the mouse, it re-triggersmouseenter. But more investigation required.TableViewRelated issues:
989
265
913
981
Related StackOverflow questions:
Done/dropped:
drawBarChartcalled multiple times (10+ times) for singlemouseenter(and as mouse moves within bar)listenersEnabledtoggle workaround (best I have for now)mouseleaveandmouseenterfired when element is removed/added while under the cursor?mousedown) from “set state” (mouseenterandmouseleave)SelState(persistent/transient)FigandselectionResulttoSelState, running the analysis once for each of persistent, transientSelStatein each.jsfront endmouseleaveUIHelperstodraw-functionsRendererUIHelperscolorShadetoUIHelpersBarChartSetNot for nowbar_fillwhen transiently selectedTableViewisUsedintoUIHelperstableRow_isUsedto include transient selectionmouseleaveevent lost (maybe if mouse moves quickly andmouseentertakes too long?)LineChartdrawFig(handler tied to initial value offig!)ScatterPlotMatrixView: CSS to distinguish transient from persistent selection