Skip to content

Conversation

@kwvanderlinde
Copy link
Collaborator

@kwvanderlinde kwvanderlinde commented Nov 27, 2025

Identify the Bug or Feature request

Fixes #5814

Description of the Change

This enables both horizontal and vertical lines for JTable at the look-and-feel level. Individual tables can then decide whether to display the lines using their showHorizontalLines and showVerticalLines properties. Most tables leave these properties disabled, but these editable tables enable the lines:

  1. The Speech table in the Edit Token dialog.
  2. The table in the Edit Table dialog.

The inclusion of lines makes these tables easier to use as the user is now aware that extra blank rows exist at the end of the table for them to extend the table. To further improve the UX for these tables, the row selection highlight has also been disabled so that the current cell's highlight is visible without having to strain the eyes.

There are some other editable tables, but they are more specialized and do not use a default JTable. E.g., the token properties in Edit Token. Such tables do not have the same usability issues, or already do not follow the table L&F on this point, so they have not been changed.

Possible Drawbacks

Should not be any.

Documentation Notes

Editing the Speech table in the Edit Token should be clearer in 1.19 compared to 1.18 and earlier. Old (top right cell selected for editing):
image
The same situation now looks like:
image

And similarly in the Edit Table dialog:
image
is now:
image

Release Notes

  • Added lines to the Speech table of the Edit Token dialog, and the main table of the Edit Table dialog, and remove the row selection highlight leaving only the cell selection highlight.

This change is Reviewable

It is now called `MapTool#configureLaf()` since it doesn't really set up anything JIDE-specific aside from LAF
properties. The code has also been unwrapped from the surrounding `LookAndFeelFactory.UIDefaultsCustomizer` since that
is just a callback that gets immediately invoked, and this isn't JavaScript.
It is now update to individual tables to decide whether they need borders. Most table leave the borders disabled. The
only tables to enable them are the ones that need to support editing by the user, including the addition of new rows:
- The Speech table in the **Edit Token** dialog.
- The table in the **Edit Table** dialog.

While there are other editable tables, they are more specialized and so do not have the same usability issues.
This makes is much clearer which cell is being edited as the UI for indicating that is not obscured by the row
highlight. Since uneditable tables don't need such feedback, and since row selection is sometimes a key feature for such
tables, the highlighting has been left in place for those tables. The only affected tables are thus the **Edit Token**
dialog's speech table, and the **Edit Table* dialog's table.
@kwvanderlinde kwvanderlinde self-assigned this Nov 27, 2025
@github-actions github-actions bot added the bug label Nov 27, 2025
@kwvanderlinde kwvanderlinde force-pushed the bugfix/5814-table-cell-borders branch from e72a7a9 to 3d28efe Compare November 27, 2025 06:27
@kwvanderlinde kwvanderlinde moved this from Todo to Awaiting-Review in MapTool 1.19 Nov 27, 2025
@github-project-automation github-project-automation bot moved this from Awaiting-Review to To-Be-Merged in MapTool 1.19 Nov 28, 2025
@cwisniew cwisniew added this pull request to the merge queue Nov 28, 2025
Merged via the queue into RPTools:develop with commit 0afe030 Nov 28, 2025
4 checks passed
@github-project-automation github-project-automation bot moved this from To-Be-Merged to Merged in MapTool 1.19 Nov 28, 2025
@kwvanderlinde kwvanderlinde deleted the bugfix/5814-table-cell-borders branch November 28, 2025 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Merged

Development

Successfully merging this pull request may close these issues.

[Bug]: No borders around Speech entries in Edit Token

2 participants