Does this have static boxes for the orders or do they adjust based on the order size?
They are not static. They adjust according to the longest/tallest order in each Row.
Order marked as Complete …
Completed Task disappears after 5 minutes. It still exists, but is no longer Displayed …
1 Like
When I press 1, Autohotkey clicks a box and then it press Order Ready, but I press the button one time
1 Like
I rolled back custom keyboard changes and added keyboard handling feature to “Automation Command Button” widgets. So when you map a keyboard key (shortcut / hotkey) to a button widget it will work when mapped keyboard key pressed. I’ll give more detailed information when we release next update.
2 Likes
Autohotkey is a great solution too. I use it a lot with Pulover’s Macro Creator to test user inputs.
@emre, I am working on this idea for a Recall List …
The Up/Down arrows track position number, and I use ToggleIf to select the appropriate position …
But if we currently have position #1 selected and we click the up arrow, I cannot figure a way to “deselect” card number 1.
EDIT: Never-mind - sorted that ^ out - just Refresh the Entity Screen!
I don’t really know how many positions are in the Widget, so I don’t know how to constrain the Max position number to stop at the last Card when using the ‘down’ arrow.
EDIT: I did a quick query for that ^ to count number of tasks where Completed = 0.
I have 1 hurdle yet to overcome:
How to process my “recall” button to feed the selected Task ID or Identifier to Script so that I can switch the Task Type back to the main Kitchen Widget.
EDIT: I am now storing Position numbers with Identifiers in Program Settings, so I am almost complete!
3 Likes
For next update I added Left, Right, Up, Down commands to navigate on widget. These commands also scrolls widget to bring selected item into view.
4 Likes
LOL, of course! All that work I did in Automation for arrow keys (kinda proud), and you add a feature to do it for me… cool!
1 Like
So far, this is what I have, and it works, but there are some small problems when it comes to switching the Task Type that I believe to be “speed related”. That is, if you are too fast, then Tasks get missed and don’t transfer between the main Task Type (left) and the Recall Task Type (right), or vice-versa.
I can only assume it is because the Task Type switching is done via JScript with SQL. And because of that, I needed to use some Execute Automation Command with Delay “trickery” to try to overcome the problem. It works, if you work “slow” and wait for the updates to happen, but as we know, speed is everything.
Regarding that ^ I think some of the new features coming in next release might alleviate those issues, hopefully.
It works via clicking the buttons on the screen, or via mapped keyboard commands, so the Bump Bar device should work. NOTE: this display is being done using the v5.1.60 Beta which has the keyboard hooks for Automation Command buttons.
It starts with 4 Orders on the main display (left) and no orders in the recall list (right).
The sequence of the operation seen is this, and can be performed using the keyboard:
1 Complete order in position 1 of main display
1 Complete order in position 1 of main display
1 Complete order in position 1 of main display
down Select order in position 1 of recall list
backspace Recall highlighted order (pos 1 of recall list)
down Select order in position 1 of recall list
down Select order in position 2 of recall list
backspace Recall highlighted order (pos 2 of recall list)
4 Likes
I am following you closely on this @QMcKay I think the bump bar idea would be awesome for my quick service restaurant. They complain a lot about how its currently working and this looks to solve most of their complaints. I wish I could contribute but man my time is so limited lately.
3 Likes
LOL, thanks for that @Jesse. I will probably never have a Bump Bar, but the whole idea is cool so that is why I have an interest in helping develop a solution. I can imagine that many restaurants would have this type of device.
And because I can use the keyboard or the buttons on-screen, it is a good option to keep grease contained to the lower part of the screen, rather than all over it like I currently experience at my burger/fry shop.
4 Likes
Would be nice to have an option for that @emre. Right now I just have the Complete minutes set to 1 and then they go away.
How they go away? They added to recall list as uncompleted? In fact I doubt I fully understood recall idea. If it is used for undoing purposes leaving completed items under the list does that. If it is just about how we display these maybe we only need to improve how we display completed items.
PS: I implemented duplicate command to duplicate a task under a different task type.
1 Like
Yes.
They are marked as complete on main Widget, then inserted into Tasks table as a Recall Task with Complete set to 0.
Same works in opposite direction:
They are marked as complete on Recall Widget, then inserted into Tasks table as a “main BB Task” with Complete set to 0.
Yes. Well, except the Recall command will only recall the last completed item. It does not have a “queue” of completed items, so Recall only works once. Also, if the Task has disappeared from the Widget, then Recall command does not work at all.
So the idea I came up with was to switch the Task Type and mark it NOT Complete so we have a “queue” or LIST of orders that we can “recall”. In code, I have this limited to 8 Orders, but it could be virtually infinite.
Personally, I don’t think that is necessary. In general, completed items appear fine, then disappear after a timeout period. I think it works good as-is. But for reasons I mentioned above, I was looking for a larger “undo list” than what you provided with Recall Command.
I think that will work well. It should save the need for all the crazy Automation I did to make this work. And the “Recall List” Task will operate just as demonstrated above, I think 
One of the main things I feel is a neccesity if Im reading this thread correctly is quite often on the bump bar, you would hit #1 5 times in a row, and the first 5 orders come off, I dont really see the purpose of pressing once to highlight because if you do make a mistake you should just be able to press recall and that order yu just bumped should appear back in slot #1
Right. And that is exactly how current implementation works with the Recall command. But you are limited to 1 recall only.
If we can increase the Recall “queue” so that it is not limited to only the last Order Completed, then it would work better.
The idea of having a “visible recall list” as I have shown was just another idea that could be done. Someone in this thread mentioned that. In which case, you need to be able to select the Order you want to recall using arrows, then hit the recall button.
In the Tradition of SambaPOS, there should be no reason we can’t have both, and you choose how you want it to operate. In fact, I have both the above described systems working together right now, but you could use one method or the other if you so choose…
1 Like
I can increase it but I thought if I allow more recalls people will make more mistakes. If we assume people can press 2 instead of 1 and add a recall function to fix that we should also assume people can press recall 3 times instead of pressing 2 times. My solution might not be good but quickly thought that solution.
1 Like
Hmm. In fact I unintentionally disallowed recalling removed items but I think if we limit it for items that still stays on screen we can remove recall limit. Bringing back an item that does not appears on screen anymore does not feels right to me. Your list is better.
1 Like
The recall column looks pretty good. To be honest a lot of the times when you need to use recall it was for something trivial like what were the sides for the last order or to check something so having the column you can glance at recently completed tickets quickly
1 Like