Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Categories
- 2.1K All Categories
- 200 Site Announcements
- 66 News and Announcements
- 134 General Discussion
- 846 Fractal Mapper
- 214 Fractal Mapper General
- 626 Maps and Symbols
- 32 Skwyre Virtual Table Top
- 29 Skwyre General Discussion
- 3 Skwyre How-To
- 364 AstroSynthesis
- 273 AstroSynthesis General
- 91 AstroSynthesis Plug-ins and Scripts
- 105 The Keep
- 105 The Keep General
- 59 ScreenMonkey General
- 18 ScreenMonkey Setup and Configuration
- 311 Inspiration Pad Pro
- 311 Inspiration Pad Pro General
- 135 NBOS Character Sheet Designer
- 135 Character Sheet Designer General
Minor quirk with eachchar
The table indicated by eachchar can't have spaces in the name. The workaround is easy of course -- removing the spaces -- but I mention it in case someone else runs into this.
The example from the help text works:
table: eachcharexample
[ Necromancer >> eachchar mangle]
table: mangle
[{$1} >> lowercase]
[{$1} >> uppercase]
It gives results like this, as expected: NeCrOManCeR
Normally, IPP lets me get away with spaces in table names, but not, it turns out, with eachchar:
Example with spaces in table names:
table: eachchar example
[ Necromancer >> eachchar mangle this]
table: mangle this
[{$1} >> lowercase]
[{$1} >> uppercase]
It yields (missing)(missing)(missing)(missing)(missing)(missing)(missing)(missing)(missing)(missing)(missing)
The "eachchar example" table name works. The Console tab, however, shows 11 occurrences of Missing Table: mangle (one per letter passed to eachchar).
In my attempted usage, IPP went spinning off into an infinite loop until it crashed, so I didn't have the chance to see any Missing Table messages. I don't know how that happened, but once I removed the space from the table name, it worked as intended.
Comments
Yep, this is a good hint. IPP should probably not allow tables with spaces at all, just to prevent the weird confusions they create when its trying to decide if something is meant as a table or table & parameter.
I like the flexibility of having spaces and even some punctuation in table names. It makes the table names easier to read (for me, anyway), and it can cut down on editing and mistakes if I'm copying and pasting. For example, if I'm generating an object with several lines like
Object Function: [@Object Function], it's easier to paste the same text repeatedly (twice in this line, and again for theTable: Object Functionline) instead of having to fix or retype half the text I enter.I just need to be careful of special circumstances like making eachchar table names monolithic.