Hot Door CORE Forum
Column View cell display issues - Printable Version

+- Hot Door CORE Forum (http://hotdoorcore.com/forum)
+-- Forum: All forums (http://hotdoorcore.com/forum/forumdisplay.php?fid=1)
+--- Forum: Bugs (http://hotdoorcore.com/forum/forumdisplay.php?fid=5)
+--- Thread: Column View cell display issues (/showthread.php?tid=346)



Column View cell display issues - Rick Johnson - 05-23-2023

When I double-click a cell in a Column View to do an inline edit in macOS AI 27, CORE 0.8.1, the text first appears highlighted, white on black. When deselected, it becomes black on black, or invisible. This is true in all UI options.

In Windows, the text is always black on white.

In macOS, the entire cell is opened as a text editing area, but in Windows the text edit field is much smaller than the cell.

As a workaround, I set the editable vector values to all false, to call a dialog to edit the contents on a double-click (my callback tracks time between clicks to determine the second click). Ignoring my double-click tracking, the first time the user clicks in the column view after focusing the panel, the ValueChanged callback gets called twice, opening the cell for editing (even though its editable is false). Subsequent clicks call ValueChanged only once. It's interesting that it calls ValueChanged even if it's the same row, so the [row] value hasn't really changed.

As a workaround for that, I set a callback for CellClicked. It gets called the first time one clicks a cell in a row. If the user clicks a different column in that row (a different cell) or a different row, cell clicked does not get called, as I would expect. In that case, I'm guessing CellClicked is meant to refer to a double-click that opens an editable cell for inline editing, so clickedColumnIndex can't be called either for simple row selection.

I hope there are workarounds for the display issues and false double-clicks, and that they can be improved.


RE: Column View cell display issues - Rick Johnson - 11-28-2023

Clicks in a column view are still problematic in CORE 0.8.2.