-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customer Waiting Area #81
Comments
I have the same question |
Bump. |
Bump Bump |
@alghanmi The assignment rubric does not say one way or another, is it supposed to be an "area" or are they all allowed to stand on one spot? |
I also am wondering this |
Personally, I think that they shouldn't be stacked on top of each other. If that was the case, I don't really see the point of listing it as a requirement since it's almost the exact same thing as having the home position off the screen, except that you change the home position to on the screen. I think Wilczynski might have wanted something like his own restaurant, where there was a line of customers and a line of waiters. |
We should be able to distinguish between customers in the waiting area. The way you implement this visually is up to you. In other words, if there are five customers waiting, I should be able to see five customers in your GUI in the waiting area. |
The website specifically mentioned that we needed separate positions for the waiter, and I did that. With the way I have implemented things (my customers overlap), having different customer positions means changing a lot of interaction. Given the amount of time that I have now, I can't really do anything, also while ensuring that I don't damage my system. I sincerely hope that is not a problem! |
@vikrantsinghal - there are a couple easy ways to offset the customers from one another, such that they can be easily identified. For example, you might use the customer's position in line (based on the number of waiting customers) as an 'index' of sorts to set a certain position on screen. Put this in the customerGui. When the waiter goes to pick them up, just retrieve this value from the customerGui so the waiter knows where to go. |
I thought of that. I don't mean to be rude, but I'll have to put in hacks in my code in order to implement the thing you said, which at this stage doesn't seem like a feasible option. The last line you wrote is easy to code, but the part at the beginning is difficult to create in a short while (and test), looking at my code structure. But thanks anyway. |
It's impossible to ensure all customers can be seen in the waiting area when an infinite amount of customers can be created and waiting for a table. Moreover, my waiting area has seats for only three customers. Realistically, those without a seat would be waiting outside. For my design, I can have a few extra customers standing along the "wall" but beyond that they will be blocking the entrance, cashier, host, and then within the restaurant. So how should we handle this? |
Are the customers allowed to overlap in the waiting area? Or are we supposed to place them in a grid-like layout?
The text was updated successfully, but these errors were encountered: