I’m trying to add a Decker port to my Cloak of Darkness project
I could be using the Twee Bridge, since I have the Twine files, but I’m attempting a completely Decker-only way. I’ve just started and already learned about:
Next on the list is:
I’m really glad for this jam, cause I learned a lot through it. The way Decker uses variables is so different to what I’m used to. But I can now say I can use some Lil/Lua, creating and modifying variables/values, coding conditional statements linked to state and value of a widget, and make invisible buttons! 🎉
Nicely done!
One idea that might simplify this sort of deck in future projects would be to take advantage of Lil's ".." notation. Whenever you have a "path" to a deck part or attribute:
Cloak.widgets.FromCloakroom.show:"none"
A pair of dots next to one another act like a wildcard, substituting in each element of a list or dictionary. For example, you could hide every widget on the card "Cloak" like so:
Cloak.widgets..show:"none"
Often it's helpful to discriminate a bit more. We can write a "helper" function that queries a card for widgets whose name matches a glob-pattern and install it in the deck-level script (File -> Properties... -> Script...):
on find_wids card namePattern do extract value where key like namePattern from card.widgets end
Then, instead of writing something like
Cloak.widgets.FromCloakroom.show:"none" Cloak.widgets.FromCloakroom1.show:"none" Cloak.widgets.FromCloakroom2.show:"none" Cloak.widgets.FromCloakroom3.show:"none"
We could write
find_wids[Cloak "FromCloakroom*"]..show:"none"
Not only is this a bit shorter, it could make modifying the deck much easier: so long as you follow a consistent naming convention, you could add or remove more widgets without needing to update these scripts.
Thank you!
Good to know! I do try to keep it as simple/basic as I can with the ports, but I’ll keep this one bookmarked for the next time I mess around with Decker, that’s super useful! Thanks for the notes!
