Replies: 4 comments 2 replies
-
Yes. In the docs at hash routing there's a section about this. The section is something like - "sometimes my route form is an alert". Just load the form in the alert with route=False. alert(MyForm(route=False)) Although obviously this won't be part of back forward navigation. |
Beta Was this translation helpful? Give feedback.
-
Thanks Stu. My idea was actually to have the forms added to the history stack even though they were in an alert. For example, let's say we have My initial work-around idea is to have a blank form with a This way you can still add to the stack but still have the alert. Your idea #240 might help with some of this if While I am writing this - I am not actually sure if this is really that valuable - the main reason for me initialling calling an alert was so that I didn't have to unload the page - routing makes this a whole lot easier since you don't have to manually cache the form... |
Beta Was this translation helpful? Give feedback.
-
I can't see it being a feature that's easy to add. Mostly because when an alert is opened anvil the form that opens it might depend on the return value... |
Beta Was this translation helpful? Give feedback.
-
I would like to have a crack at doing this ... but it is going to take me some time to get up to speed with the code (and my proficiency!!) I have only just started using hash routing so I am still finding my way around it but would really like to contribute. |
Beta Was this translation helpful? Give feedback.
-
Is there any way to use routing with forms loaded in alerts?
I often use forms loaded in to alerts to edit data while the MainForm stays loaded with other data.
These alerts can be called from modules or other forms
Is this even possible?
Beta Was this translation helpful? Give feedback.
All reactions