So I know that & and | work like a boolean AND and OR but is there anything that works like an XOR?
Depending on what you're trying to do, either a combination of ! and = (for a scalar boolean value, logical XOR is the same as "not equal to") or possibly bits.xor[].
TLDR eval->dd.say isn’t passing rich-text into the dialogizer In your Dialogizer deck, on the rich-text card, you mention that it’s easier to style by throwing rich-text into a field and having it parse using the eval method. So I’ve got a field, i’ve got it set to invisible in the card script, I’ve got a button that does the eval method. Everything is working well except that it isn’t showing the styling I’ve set in the field. I’ll mention, just as I typed this I tried to add a hyperlink in the same way (just manually add it to the field) and it also didn’t pass through the parsing operation.
Forgive me, I’m one of those dudes who got by in the 00s by just manually deleting html and css stuff and adding it back to “create my own myspace profile”. Like, that’s my level of coding know-how. I’m sure this question is voiced annoyingly; I’m trying to use words I’m not fluent with. Thank you for everything you do here IG.
Ok forgive me, I didn’t follow your operation faithfully, I now see. Your method was to use a button to point at one field that itself pointed at another field (which contained the rt formatted text). I was skipping the middle-person field and apparently, by doing that, it doesn’t render the rt formatting. I’m leaving this post because it may come up in the future; perhaps IG (or someone else) could simply verify that this was indeed my problem and if anything maybe propose how I might’ve skipped the middle-person step and kept the RT formatting.
eval is a handy tool for making code snippets visible in the documentation, but it's not often needed while making projects with dialogizer. And it's probably working against you here.
This:
dd.open[deck] dd.say[yourcoolfield.value] dd.close[]
should be enough to play a scene written in a rich text field, with all of the formatting intact.
It's important that you point dd.say at the field's .value (which includes the rich text formatting) and not .text (which is plain text only)
If you strip it down and just put the above code snippet (with "yourcoolfield" renamed to be correct for your project) does it work?
I’ve got another, probably totally silly question, (I promise I look through all the documentation, the problem is that I’m basically illiterate in basic coding). As you’ll see in this video (how do you folks get those cool embedded videos to happen without using youtube?) I’m running a card script which evals the field on the left (called cardscript; yes i know the text above the field has a space, trust me it’s labled without the space). I’ve defined a (dunno what to call it) thing called “fields” which I want to use as a bucket to hold all of the fields i wish to make invisible at when I click “eval below”. As you can see, when I just define the thing as ’source’ it works, but when I add a comma and include ‘cardscript’, not only does it fail to include cardscript, but now source remains visible.
Secondary issue: The !alert works, but does not retain the richtext formatting.
to get ahead of “why are you doing this in fields”, the answer is, “I’m trying to teach myself how to code AND how to code in Decker and it’s a ton of friction having to click back and forth between widgets and interact, into the card script etc. and theoretically, it shouldn’t matter provided I do this correctly."
It's totally fine to be new and have questions! Decker is a pretty friendly environment to try things and figure them out. And I think most of the things that look like videos in the thread are actually gifs. I know I use a screen-to-gif recorder when I need to make a small example of something.
Okay, I think these are your main questions:
1) How can I make Decker use the whole list of widgets I defined earlier?
You just need a tiny change to how you're referencing them. You need two periods, instead of just one in this case.
fields..show:"none"
2) How can I make my !alert use my rich text formatting?
In-line commands run by dialogizer don't carry over any of the rich text features. I'm pretty sure they're just run as code.
However, you can point to another field's value inside of your !alert[] in the same way you point to source.value inside of dd.say[].
!alert[problem.value]
I know it's another step, and another thing to have to manage while you're editing but it should be pretty straightforward.
Another thing that I think might help you sometimes is the ScriptViewer contraption. You can have it display the card script and let your edit it from your card in interact mode instead of having to use a workaround with eval. And because the ScriptViewer only displays scripts that exist elsewhere you can safely delete the ScriptViewer contraption when you're done.
Just another possibility, in case it helps!
Hi, I noticed a discrepancy in behaviour between native decker and exported HTML decker and was wondering if anyone knew why.
Basically wanted a looping sound to play “on view” of the very first card in the deck:
on view do
play[“sound1””loop”]
end
In native decker, this seems to work. I believe I also got it to work in web decker directly. But I am finding in a web decker protected export from native, it only plays the sound once (and weirdly, after clicking into the deck). However, if you do it as a second card you view through some other trigger, the same code works in web / native.
Are there a special considerations for doing “view” actions on the very first card?
Many thanks in advance if anyone knows…
As a general rule, web applications are not allowed to start playing sound without user interaction. Web-Decker attempts to start its audio subsystem when the user first clicks or types on the keyboard. It's possible there's some additional inconsistency in behavior, but what you're describing sounds to me like normal webapp sandboxing constraints.