Search found 3 matches
- Mon Apr 05, 2021 11:56 am
- Forum: MapTool
- Topic: 1.8.4 Bug: return(a, b) evaluates macro.return if set to 1
- Replies: 2
- Views: 1757
Re: 1.8.4 Bug: return(a, b) evaluates macro.return if set to 1
Thanks for your response, I will file a bug for this. I don't normally assign something to "macro.return" multiple times, this was just the shortest possible example I could imagine. The "production code" which was affected by the error is this: [h: '<!-- ==== void switchToCurren...
- Sun Apr 04, 2021 8:43 am
- Forum: MapTool
- Topic: 1.8.4 Bug: return(a, b) evaluates macro.return if set to 1
- Replies: 2
- Views: 1757
1.8.4 Bug: return(a, b) evaluates macro.return if set to 1
The following code snippet aborts with "must not happen" but should not: [h: macro.return = 1] [h: return(0, "true found")] [h: assert(0, "must not happen")] Replacing the first line with [h: macro.return = 0] or [h: macro.return = 2] or [h: macro.return = "anythin...
- Mon Dec 28, 2020 8:36 am
- Forum: Macros
- Topic: Force frame to foreground on windows
- Replies: 0
- Views: 6614
Force frame to foreground on windows
I have a frame with a bunch of macroLinks on it (like a rule book index list). Now I can click on a link and it opens the current linked rule section. But the frame with all the links is still in the foreground and the new opened frame with the rule I have clicked is in the background of this frame ...