Skip to content

Conversation

@kwvanderlinde
Copy link
Collaborator

@kwvanderlinde kwvanderlinde commented Sep 16, 2025

This change is Reviewable

kwvanderlinde and others added 22 commits July 26, 2025 22:10
_Fix applies to both PointerTool and StampTool_

When releasing the mouse, we grab the current drag state before it gets cleared, so that we know whether the user was
dragging the map. This is in lieu of a more comprehensive change to `PointerTool` and `StampTool` that would isolate
different user actions to ensure this kind of thing can't happen.
…-menu-when-dragging-map

Do not show token popup menu while dragging map
This is more wasteful, but is identical to 1.17 behaviour and avoids the possibility of stale selection data in case the
zone has not been rerendered after a selection chnage.
`TokenRenderer` applies the token opacity, so callers do not need to pass it in. They should only pass additional
opacity, such as that used to indicate a dragged token.
…acity

Remove redundant application of token opacity
…ace-condition

1.18 - Fix getSelected() stale results
All the modifications of `MacroButtonProperties` still have to be gated behind a null check since campaign properties do
not have `MacroButtonProperties`.
…-editor

1.18 - Fix macro editor for campaign properties
The associated `HtmlDocument` constructor no longer has `isJavaBridgeInjected` or `isBaseUrlInjected` parameters since
these have to be `false`.
This make `cachelib` be consistently applied to HTML5 content again.
1.18 - Fix "Visible over FoW" setting for stamps
1.18 - Remove LibGDX renderer and other minor fixes
@cwisniew cwisniew added this pull request to the merge queue Sep 16, 2025
Merged via the queue into develop with commit 38b39ff Sep 16, 2025
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants