Odoo/addons/barcodes/models/__init__.py, branch 14.0 The current checkout of upstream Odoo [REF] barcodes, stock, point_of_sale: one nomenclature per company 2018-09-10T11:33:42+00:00 William Henrotin whe@odoo.com 2018-08-29T13:36:31+00:00 95a9572da3a8f2134ea6d5ff917c7c17526f6ee7 This commit adds a many2one between barcode.nomenclature and res.company and removes Many2one pointing toward a nomenclature record. This aims to improve the usability and allows using nomenclature in inventory adjustment where a `nomenclature_id` field was set. 
This commit adds a many2one between barcode.nomenclature and res.company
and removes Many2one pointing toward a nomenclature record.

This aims to improve the usability and allows using nomenclature in
inventory adjustment where a `nomenclature_id` field was set.
[MERGE] forward port branch saas-15 up to e0422bfd6c5 2018-02-01T15:40:13+00:00 Christophe Simonis chs@odoo.com 2018-02-01T15:40:13+00:00 920aa6174c938bbfc0864a95ff3d8ebbe3132387 






[FIX] barcodes: delay between keys
2018-01-31T12:47:17+00:00

Nicolas Martinelli
nim@odoo.com

2018-01-31T11:41:31+00:00

513fad42a0bdebd5378fb9472bc7084e91435884

In order to detect if a barcode scanner is being used, we detect the
delay between keypresses. The value is hardcoded to 55 ms. However, in
the case of a bluetooth scanner, this delay is often not enough,
resulting in an incorrect capture of the barcode.

We add the config parameter `barcode.max_time_between_keys_in_ms` which
allows the user to fine tune this delay for his hardware.

opw-806398





In order to detect if a barcode scanner is being used, we detect the
delay between keypresses. The value is hardcoded to 55 ms. However, in
the case of a bluetooth scanner, this delay is often not enough,
resulting in an incorrect capture of the barcode.

We add the config parameter `barcode.max_time_between_keys_in_ms` which
allows the user to fine tune this delay for his hardware.

opw-806398







[FIX] Various P3-related import changes
2017-04-28T07:06:53+00:00

xmo-odoo
xmo@odoo.com

2017-04-28T07:06:53+00:00

b4429c2a91889bf60b56e0c7909c844d357363f7

* LDAP import: python-ldap is not python3-compatible, pyldap is

  Warning: only supported from debian Stretch (current testing)?
  https://packages.debian.org/search?searchon=names&keywords=pyldap

* implicitly relative imports
* imports of moved or removed stdlib modules

issue #8530





* LDAP import: python-ldap is not python3-compatible, pyldap is

  Warning: only supported from debian Stretch (current testing)?
  https://packages.debian.org/search?searchon=names&keywords=pyldap

* implicitly relative imports
* imports of moved or removed stdlib modules

issue #8530







[MOV] barcodes: Reorganised file structure.
2016-06-07T15:43:35+00:00

Ranjit Pillai
rpi@odoo.com

2016-02-03T12:50:43+00:00

cb313ac19f369a61811c430de39a53637ccd99ff












[ADD] barcodes: onchange-like mechanism to react to scans in form view
2015-09-01T11:25:52+00:00

Arthur Maniet
arthurmaniet@me.com

2015-07-08T06:08:25+00:00

2df4060c776c7a6a946f2b7a164ff7bbbe5e854a

For a model to use it, it must :
- Inherit barcodes.barcode_events_mixin and override on_barcode_scanned(self, barcode)
- Add <field name=barcode_scanned widget=barcode_handler/> to each form view that
  should listen to barcode events and trigger on_barcode_scanned.

The method on_barcode_scanned works just like an onchange.





For a model to use it, it must :
- Inherit barcodes.barcode_events_mixin and override on_barcode_scanned(self, barcode)
- Add <field name=barcode_scanned widget=barcode_handler/> to each form view that
  should listen to barcode events and trigger on_barcode_scanned.

The method on_barcode_scanned works just like an onchange.