My problem is very clear and straightforward.
When you want to display 3 different text box objects with a single notification tool, you either have to add 3 different notification tools or struggle with variables.
Why do we have to go through all this trouble?
It might seem like a small problem, but it's a frustrating one when you overthink it.
MIT app engineers need to look into this.
I hope this problem is solved soon.
Eto
You can't just expose them in a hidden Arrangement?
I didn't understand what you meant.
Place your Text Box Components on an Arrangement Component. Hide the Arrangement, Show it when the App needs to display the notifications.
Major question though - why do you need to display 3 text boxes at the same time - or perhaps that's not what you mean? Do you mean you have 3 messages/texts and any one of the three could be displayed? If so, make a simple List Component, add the messages to the List, call the relevant List Item when showing a Notification.
What I mean is this:
Old PIN in the first notification
New PIN in the second notification
New PIN verification in the third notification
etc. To do things like that and to make the interface look better, we need to use a notification tool.
You're right in what you mean, but depending on your interface design, we might want to use a notification tool.
I even want to.
A Notification Component though is exactly that - it notifies.
You can mimic the appearance of a Notifier with an Arrangement.
I’d say that if you have multiple call to ShowChooseDialog or ShowTextDialog, when the AfterChoosing or AfterTextInput event is fired you don’t know to which one it refers.
Using a global variable ‘notifierId’ should disambiguate ( or adding an Id parameter to the notifier )
With this block, to do the example I mentioned above, we need to create a different system with variables, as you said.
I want to use a notification tool instead of a text box component for the design.
The problem can be most easily solved by adding "title" and "message" variables to this block.
Alternatively, you could simply add a parameter to this block, such as "save data to variable" for "save data to tinyDB"
By the way, the solution you mentioned, "we can do it with a variable," is correct. However, in large projects, there can be more than just a PIN.
If you need additional functionility in your notifier, try something like my SimpleDialog extension, you can place whatever you want in the dialog, and similarly handle the outputs anyway you want. There are many such dialog extensions available...
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
