Enhanced Images (layers) for FG 3.0 CoreRPG (and rulesets based on CoreRPG)

[Bifford]

Don’t use it in Unity. See comments at the top of this page.

Aw man. Missed that! Thanks

[Weissrolf]

I would like to use layers to place pointers underneath the player tokens (auras, light). This usually is a hassle, because player tokens always supersede pointers when they are on top of each other. My idea was to place the pointers in the middle layer in order to be able to grab/move pointers that are centered beneath a player token. Unfortunately even on the lower layers player tokens from the top layer supersede pointers and thus the token is grabbed/moved and not the pointer.

Is there any way around this?

[Trenloe]

I would like to use layers to place pointers underneath the player tokens (auras, light). This usually is a hassle, because player tokens always supersede pointers when they are on top of each other. My idea was to place the pointers in the middle layer in order to be able to grab/move pointers that are centered beneath a player token. Unfortunately even on the lower layers player tokens from the top layer supersede pointers and thus the token is grabbed/moved and not the pointer.

Is there any way around this?

The tokens on the bottom layer are just indicators of what's on the top layer, to assist with unmasking,etc. - if you move them on the bottom layer the master token on the top layer doesn't move. So move them out of the way and draw your pointers.

[Weissrolf]

Thanks for the quick answer!

Indeed, but once I switch to the top layer those tokens move back to their original position. So every time I need to move the pointer I also need to move the token first, which leaves me were I began without using layers. If those tokens are only indicators, would it not be better to give them lower grab/move priority over objects that originate on the lower layers (aka pointers should be on top of them and be movable)?

I suspect that the latter is not possible within FGC, so unfortunately layers don't seem to be the solution to the token vs. pointers problem. Same problem applies to pins on the lower layers.

[Trenloe]

If those tokens are only indicators, would it not be better to give them lower grab/move priority over objects that originate on the lower layers (aka pointers should be on top of them and be movable)?

That can't be done in an extension. The hierarchy is built into the image control.

[Weissrolf]

Just as suspected. Bad luck. Thanks for the help anyway.

[Weissrolf]

Would it be possible to disable the indicator tokens on lower layers via switch or via commenting out some lines in the code?

[Trenloe]

...via commenting out some lines in the code?

You can do this in your local copy.

In the extension scripts\manager_layer_tokens.lua file put if true then return; end as the first line in the showLayerTokens function.

function showLayerTokens(windowinstance, sourcelayer, targetlayer)
	if true then return; end
	local sourceLayerScale = 1;
	local targetLayerScale = 1;
...
...

[Weissrolf]

Thanks for the code, I will give it a try!

Edit: Unfortunately this causes some problems, especially with pointers on the middle and lower layer. So I will leave it at that and just keep moving things around.

[Weissrolf]

I noticed that tokens placed on the lower and middle layer cannot use "reset individual token scales" (CTRL + middle-clicked or menu dial). On the upper layer it seems to work.

Feature request: Keyboard short-cuts to quickly switch layers instead of having to mouse-click.

Thanks for the extension!