Before this, users were only able to press a key when all other keys
were released to prevent a key from repeating. This works but when
typing you usually press the next key before releasing the current
one. This allows users to do exactly that while still blocking keys from
repeating.
Implement a new way of dealing with barcode events. This was necessary
because the old way of dealing with input coming from barcode devices
did not stop keyevents. This lead to all kinds of issues (eg. barcode
reader output being inserted as tender in a paymentline).
This new class inserts itself so that it handles all keyevents before
everything else. This means that it has authority on what keypress
events pass and which ones do not. It differentiates between 'real'
keyboard input and input coming from devices by buffering events. When a
certain amount of events come in fast enough, it is handled as a barcode
and a 'barcode_scanned' event is emitted on core.bus. When buffered
events are decided to not be a barcode, they are recreated and
redispatched.
Rebasing a merge commit with a lot of conflicts is a real pain as every
non-automatic conflicts should be redo manually (especially when there
is a lot of file rename that git cannot follow)
- Automatic bank reconciliation: failure to acknowledge that x * -1 == -x
- Interface: hide the 'partial reconciliation' sign when matching a transaction with an already registered payment
- restored icon of modules account_check_writing and l10n_us_check_printing
- removed payment_type from account.payment tree/view since those views are already used with a domain and the type can be inferred from the name given by a sequence
- account.payment field company_id wasn't stored and, so, 'Group By' failed
- fixed extensibility of register payment wizard through method get_payment_vals()
- since register payment fully pays selected invoices, the amount should be readonly
- if payment journal is called 'Payment Mode', payment_method should not be called 'Payment Mode'
- improved batch deposit template
- check memo length when registering a check
- in check printing, sort invoices by due date
- checks get a check number attributes when registered from the payment wizard as well
- when a module extends a method from account.payment it should be careful to check the selected payment method
When loading an action using a specific url, with
a view_type different than the default view of the action
(e.g. Project > Project > Issues has as view order
kanban, list, calendar, form, graph, and try to load
this menu action from an url, but by specifying another view_type
than 'kanban', for instance, 'list'), the default loaded view was
always the first view, and then a switch was done to go to the view_list.
It caused issues when using a filter needing a field available in the list
view but not in the kanban view.
It also lead to an issue in the reporting, when trying to load a reporting
action with a view not being the first one of the action
(e.g. Reporting > Project > Issues Analysis, switch to the second view
'Graph', and then refresh -> Error).
This revision makes so the view from the view_type url arg is directly loaded.
opw-640289
and the render of the buttons.
The sibar menu can depends on the current view and fields
states.
We therefore have to wait for them to be loaded before loading
the sidebar.
Before this rev., loading a report view (in the reporting menu),
leaded to a crash, due to this revision: ac92551406.
opw-640409
Joren Van Onder