badly structured drinks menu

[YtvwlD]

As @derf said in #17:

Drinks should be visibly grouped by price (e.g. one line for each price). the current status makes the payment take quite a while if one really wants to search for the bought drink and not click on the next one matching the price.

[nomaster]

The API does not consider buying something, but rather depositing money. Maybe it's better to improve upon that first.

[YtvwlD]

Well, that used to be the case.

Since a60450c the API supports buying drinks.

[nomaster]

This is great! Thanks for all the contributions, @YtvwlD!

Is this implemented in all frontends?

[YtvwlD]

It is implemented in the web frontend, QMLeteroid, and in Meteroid for Android (if someone could make a new build and publish it - @Donnerbart?).

If someone uses another client, this will still work, but show as n/a in the audit log.