Options
Extra Curly Brace appearing in menu snippet
- Extra Curly Brace appearing in menu snippet
-
Extra Curly Brace appearing in menu snippet
JakeNT > 2023-10-31 11:17
I made a snippet that pops up a menu to insert the date for today, yesterday or a custom date. If I select today or yesterdays date it inserts an extra curly brace into the output but it doesn't do that for the custom. Any idea how I can stop the curly brace from outputting on the today or yesterday selections? (The reason for the custom option is this date selection is embedded within another snippet otherwise i'd just type the date manually). Thank you for any help, I just found this application today and i've already got tons of ideas how to integrate it into my workflow.
-
RE: Extra Curly Brace appearing in menu snippet
Jean Lalonde > 2023-11-01 08:44
Code:{Menu:{Now:MM/dd/yyyy}|{Now-1d:MM/dd/yyyy}|Custom~{Input:Custom Date}}
Hi JakeNT,
This looks like a bug. Your syntax is logic and should work. I don't recall testing nesting of placeholders the way you do. I'll look at it.
Jean -
RE: Extra Curly Brace appearing in menu snippet
Jean Lalonde > 2023-11-01 09:43
I investigated this issue. The problem relates to the order of processing placeholders in strings containing multiple placeholders. Currently, in your example, QAP is processing the {Input:} placeholder after the {Menu:} placeholder. If QAP was expanding the {Input:} placeholder before the {Menu:} placeholder there would be no issue... But QAP would always ask for the custom date before showing the menu which is not we want...
There is no simple solution to this problem if I want to make sure I don't break the code for other scenarios. I'll put it on my to-do list but, in the meantime, I have no better solution than to manually delete the unwanted "}". -
RE: Extra Curly Brace appearing in menu snippet
JakeNT > 2023-11-01 09:50
(2023-11-01 09:43)Jean Lalonde Wrote: I investigated this issue. The problem relates to the order of processing placeholders in strings containing multiple placeholders. Currently, in your example, QAP is processing the {Input:} placeholder after the {Menu:} placeholder. If QAP was expanding the {Input:} placeholder before the {Menu:} placeholder there would be no issue... But QAP would always ask for the custom date before showing the menu which is not we want...
There is no simple solution to this problem if I want to make sure I don't break the code for other scenarios. I'll put it on my to-do list but, in the meantime, I have no better solution than to manually delete the unwanted "}".
No worries! Thank you for checking on it Jean! It's a fantastic application and it's helping me a ton already with my workflow. Thanks again for everything!