Notes |
|
(0054297)
|
hgbot
|
2012-11-16 15:55
|
|
|
|
(0054298)
|
hgbot
|
2012-11-16 16:59
|
|
|
|
(0054300)
|
dbaz
|
2012-11-18 04:52
|
|
The fix is not good.
Having a fix with several concatenated "child" structure is a way to guarantee that if the final component (or any in the middle) is moved (from a container to another one), the action is not going to be performed.
There are several possibilities to ensure that always is going to work:
If the component is a direct child of the component, give the last child a "name" (in case it doesn't have already one), and do something like
OB.POS.terminal.$.<given-name>.model.processChangedCustomers();
If it is not a direct child, you can define an event listener in the last child and then from OB.POS.terminal set a "waterfall". The WebPOS is plenty of them, so you can check how are they made. Also you can consult here to obtain more information about how it works:
http://enyojs.com/docs/events.html [^] |
|
|
(0054351)
|
hgbot
|
2012-11-20 18:15
|
|
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 91fd15bea60d17e2613f7ec8046a4ff2c457d48a
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Tue Nov 20 18:15:41 2012 +0100
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/91fd15bea60d17e2613f7ec8046a4ff2c457d48a [^]
Fixed issue 22331. Orders will be automatically saved if the connection returns.
---
M web/org.openbravo.retail.posterminal/js/components/terminal.js
M web/org.openbravo.retail.posterminal/js/pointofsale/model/pointofsale-model.js
M web/org.openbravo.retail.posterminal/js/utilities.js
---
|
|
|
(0054525)
|
hgbot
|
2012-11-27 11:29
|
|
|
|
|
Reviewed at @cde372d8864d |
|