@emre any chance on getting [?prompt] to work with custom keyboard?
Ive redesigned my price override system using menus with custom keyboard and custom product buttons. The flow is press price override, select the order, key in the new price and press the price override reason button. this then changes the price and adds the override reason as an order state. this works perfectly for the defined reason buttons, what id like to do is use the Other (Specify Reason) button with the [?prompt] to open a keyboard to type a reason that isnt listed on one of the buttons and add that as an order state
if i add the prompt expression to the custom keyboard it doesnt bring the popup keyboard up it just adds the expression as the order state
This works fine, however if i press my other reason button with the [?prompt] this is what happens, the order state just displays the prompt. i want the prompt keyboard to open so whatever i type becomes the order state
im going to update my discount setup the same way so would be handy to be able to manually type additional reasons that arent any of the buttons displayed on the screen
Can we also get the <hover> tag to work in the custom keyboard settings along with font, size, panel etc?
Would you not put the prompt in the price change action of the rule triggered by the button?
Arent these values in custom keyboard just the equivilent of automation command values? ie string iput value? hence the lack of prompt?
After the name of the auto command theres a colon where you put the command value so ive left that blank and put thr prompt in the action in the rule instead but it doesnt work, the price changes but the prompt doesnt come up
Unless i need to put [:commandvalue] in the custom keyboard format in my menu and leave the prompt in the action, dunno if that will work ill try it tonight
Price from keyboard entry yea, command value is part of the setting “string” for each button made using the custom keypad settings.
It comes after the colon right at the end of the setting “string” on each button so if i manually type :manager override on the manager override button setting it will add the order state manager override
If i do :missing parts it adds missings parts as the order state
This workd great for those “static” buttons but for the Other button i dont want a set value like i do for manager override etc i want to be able to use the prompt to enter a reason
Im not sure if i can do this with the custom keyboard setup on a menu
Cant see why could wouldnt be able to once its triggered a automation command executed rule it should not be any different to any other button/automation…
