I always had this problem with the commands especially on how you can make a snippet, inside of a snippet.
I am well aware of the {button}, {import}, and if else conditions, and I use it a lot actually. My main issue is when you press the button, I want to make sure only the imported snippet will appear. Meaning, it will look like (not) the main snippet.
I would like to make it when you press the button, as if a new page or the contents of the imported snippet will appear.
I'm hoping you could help me on this. My brain is exhausted from finding the answer in your forum, especially with the trial and errors. *sigh
P.S. I enjoyed Text Blaze A LOOOT! Hence why I'm really digging into this. Hoping to get an answer soon!
Thank you for the response!
Yes, I've been meaning to do the same on the video! Can't wait to try this out!
Also, one of my biggest struggle is that how significant the lag is once I try to execute the snippet. This happens when I place a bunch of imports and if conditions in one snippet, then import them into another snippet.
I would like to know some work around on this. Maybe I should lessen the amount of texts in a snippet for import? Maybe it is what it is? IDK. Anything would help! Thank you!
Could you provide a visual of your snippet on how it works? So I could try to rack my brain out as well
Is there a reason two of If statements have ==
My bad, here is the revised version,
{note: preview=no}{run: currsnippet=""
}{endnote}{note}{button: currsnippet="a"
; label=Snippet A}
{button: currsnippet="b"
; label=Snippet B}
{button: currsnippet="c"
; label=Snippet C}
{endnote}{if: currsnippet=="a"}Import Snippet A{elseif: currsnippet=="b"}Import Snippet B{elseif: currsnippet=="c"}Import Snippet C{endif}
Per my experience, even though "=" works, it is much better to use "==" as it corresponds to "is equals to" and is supposed to be used when comparing value. While "=" is used in setting a value.
Thank you for providing that, allow me just a moment to look into this.
Thank you for your patience, could you change the "denylisted_shown = 1" on the reset button into "denylisted_shown = yes"?
What's causing this issue is due to the Reset button setting the value for "denylisted_shown" as a number, the "not" function inside the Denylisted button wouldn't work since it only works for boolean.
Yep, since there are additional things that must be done if you wish to achieve a page effect like the snippet that I've made (the example that I have provided)
I'd be glad to help you with this one, ask me anything.
There we go, you've noticed it as well. I'd be glad to help you with the page effect, though I want you to provide how exactly your snippet is supposed to let's say work.
When you press "Denylisted", it shows up additional options, if that is the case and you wish to have a new page opened, you could put those additional options in the new page, like this one:
{note: preview=no}{run: currpage="base"
}{endnote}{note}{if: currpage=="base"}
You are on the Main Page
{button: currpage="denylisted"
; label=Denylisted}
{button: currpage="mypage"
; label=MyPage}
{button: currpage="otherpage"
; label=OtherPage}
{elseif: currpage=="denylisted"}{button: currpage="base"
; label=back}
You are on the Denylisted Page
Here comes the additional options!
{button: a=1
; label=dummybutton}
{button: a=1
; label=dummybutton}
{button: a=1
; label=dummybutton}
{elseif: currpage=="mypage"}{button: currpage="base"
; label=back}
You are on My Page
{elseif: currpage=="otherpage"}{button: currpage="base"
; label=back}
You are on the Other Page
{endif}{endnote}
Sure, good luck integrating your snippet with this one. I tried to make it as simple as possible.
Back in the early days of Text Blaze, the syntax was ==. Several years ago it simplified to =. Both still work interchangably though.
Hi, I stole this one to
just a question, is it possible to make the "back" button to only go back one step and not all the way back to base?
Yeps! you could change the "currpage" to which page you want it to go.
For example, since the diagram of the one that I have provided is only like this, the back button can only return to base..
Base
v
My Page, Other Page, Denylist Page
However, if you have more page like:
Base
v
OtherPage, MyPage, DenylistPage
v
OtherPage2, MyPage2, DenylistPage2
And you are currently on OtherPage2, you could set the "currpage" for the back button to be currpage=="otherpage", instead of "base".
Let me know if my explanation isn't clear. I'll try to explain it more in detail.
I think I got it, I need one "back" for every page? Can't have one "static" button?
That is actually possible, however it would be kind of harder to explain as it depends on how your snippet works. Here is how mine is set up.
This is like Master class degree in textblazing. I am on noob stage still, so I am sticking with the "one button" for each page for now. Ty for the help though 
Yep lol. So here, I have made some modifications to make it only have one button, kindly try to like study or understand how it works and if ever you have a question, feel free to drop it here.
{note: preview=no}{run: currpage="base"
pagename=""
pagelevel=1
}{endnote}{note}{if: currpage<>"base"}{button: if pagelevel==1
currpage="base"
elseif pagelevel>1
pagelevel=pagelevel-1
currpage=concat(pagename,pagelevel)
endif
; label=back}{endif}{if: currpage=="base"}
You are on the Main Page
{button: pagename="denylisted"
currpage=concat(pagename, pagelevel)
; label=Denylisted}
{button: pagename="mypage"
currpage=concat(pagename, pagelevel)
; label=MyPage}
{button: pagename="otherpage"
currpage=concat(pagename, pagelevel)
; label=OtherPage}
{elseif: currpage=="denylisted1"}
You are on the Denylisted Page
Here comes the additional options!
{button: pagename="denylisted"
pagelevel=2
currpage=concat(pagename,pagelevel)
; label=Denylisted Page 2}
{elseif: currpage=="mypage1"}
You are on My Page
{elseif: currpage=="otherpage1"}
You are on the Other Page
{elseif: currpage=="denylisted2"}
You are on the Denylisted Page 2
{endif}{endnote}