Help: INPUT limitations in LibToken macros?
Moderators: dorpond, trevor, Azhrei
Forum rules
PLEASE don't post images of your entire desktop, attach entire campaign files when only a single file is needed, or generally act in some other anti-social behavior.
PLEASE don't post images of your entire desktop, attach entire campaign files when only a single file is needed, or generally act in some other anti-social behavior.
Help: INPUT limitations in LibToken macros?
For some reason my INPUT code in a library token macro to fetch dice rolls do not seem to work correctly. The Label part works, but the TEXT entry part is not displayed correctly. The same code works fine in a normal token. Is there some limitations or things I should be aware of when using the INPUT function from a Library token macro?
Re: Help: INPUT limitations in LibToken macros?
Would need to see the code, but be aware you need to have an active token to use data off of it. This is usually done with "Apply to Selected" on the macro property or with in the code to chose another token like getSelected() along with switchToken().
A macro on a token assumes that token is the active token, lib tokens don't.
A macro on a token assumes that token is the active token, lib tokens don't.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools