loadkybdmacro command in Micros3700

[savissimo]

please help! i created a macro in micros 3700. In this macro i created steps:
1. step - add menu item to a guest check
2. step - work something in ISL script and use loadkybdmacro command to create keystrokes
3. step - add second menu item to the guest check

The main problem is that this macro never comes to step 3 because i used loadkybdmacro command in ISL script. The question is, how can i add second menu item to the guest check and still use loadkybdmacro command in ISL script? I`ve also tried to put something else on step 3(for example insert some characters...) but nothing happens...

 

[pmegan]

Make sure the "Prompt for operator entry" box is checked for your macro. I think that should let it accept the keystrokes you're sending before hitting step 3.

Pat

 

[DrZogg]

Tough.

A macro has 16 lines, cant you use Function Number functions and not use a SIM? What are the desired keyboard strokes the SIM provides?

STeve

 

[savissimo]

Pat, box "Prompt for operator entry" is checked, but i get the same result...

Steve,
The keystrokes are creating special condiment and inserting date and day. The date and day are calculated in the script...
So, in ISL file:
first keystroke is special condiment
second is day and date(which are actually the data that goes in special condiment)
third is @key_enter

It`s not the problem with the number of macro lines. Even if i put only loadkybdmacro @key_enter in the event, the system will never go to third step of the macro.

Anyway, i changed the logic, and switched to combo meals so now there is no need for third step of the macro because all menu items are in combo meal now. Anyway, it would be good to know why macro stops working with SIM and loadkybdmacro command as a step...

Thanks everybody.

 

[DrZogg]

Hi again,
Glad you found a way to get the desired result. I am guessing here, but it could be to do with an object hierarchy, and within that hierarchy where you are returned to once the SIM is completed. You would expect to be returned to the function that called the SIM (ie the macro).
Goodtimes. Its a pity we dont have breakpoints or able to view variable values as we program.
Steve