If a list contains a node which is not a field (e.g. a button), it will
not be found in the fields so we'll have an error trying to get 'type'
from undefined.
Clickable many2one fields for tree views
========================================
This addon provides a separate widget to allow many2one fields in a tree view
open the linked resource when clicking on their name.
You can also define a system parameter to have this behaviour for all the
existing many2one fields in tree views.
Installation
============
Install it the regular way.
Configuration
=============
If you want to have all many2one fields clickable by default, you have to
define in *Configuration > Technical > Parameters > System parameters*, a new
parameter with name `web_tree_many2one_clickable.default` and with value
`true`.
Usage
=====
For the widget option, you need to add `widget="many2one_clickable"` attribute
in the XML field definition in the tree view.
For example:
`<field name="partner_id" widget="many2one_clickable" />`
will open the linked partner in a form view.
Known issues / Roadmap
======================
* You cannot deactivate clickable behaviour for an specific many2one field if
you configure the system parameter.
* The value of the system parameter is retrieved for each many2one field
present in the view instead of only once.
The focus introduced on the 16.0 migration is causing a flickering effect
that is a bit annoying and does not make complete sense, because if you
click more than once the cursor is positioned at the end of the text,
which makes it difficult to edit the input.
The counterpart of these changes is that to edit the input using the
keyboard we will have to click on the field. Although this is how the
module has been operating since its inception.
Before this patch, when navigating inputs hitting <kbd>TAB</kbd>, you were stopped before any numeric step input.
Now, you can navigate as usual and use Odoo without a 🐁.
@moduon MT-4657
If you're using a tablet and click on the ➕ or ➖ buttons created by this module, the result was that the numeric input related to that button got focused.
On tablets, that means that the on-screen keyboard pops up. This usually triggers a layout recalculation and becomes clunky. Besides, it's useless, because if you wanted to use the keyboard, you'd have clicked on the input by yourself, and not in one of those buttons.
After this change, when using a touch screen, if you click on the +/- buttons, you won't auto-focus on the input. Thus, the keyboard won't show up.
@moduon MT-4472
Before this patch:
- On a tablet, buttons wouldn't display (big screen; can't hover).
- On a PC, fields would make layout jumps while hovering.
@moduon MT-4472
Mobile screens benefit most from this module's enhanced usability.
However, since the events used for displaying/hiding the +/- buttons depend on mouse, at the end you'll never see these buttons on mobile screens.
Thus, here's a new approach: smaller screens *always* display the buttons.
Besides, inputmode is now decimal, just like upstream float fields.
@moduon MT-4396
Xander De Matteis
Eduardo De Miguel
Raf Ven
Kévin Roche
Stéphane Bidoul
Jairo Llopis
Simone
黎伟杰
Alexandre Díaz
Anand Kansagra
Guewen Baconnier
Artem Kostyuk
Atchuthan, Sodexis
Antonio Espinosa
Holger Brunn
Pedro M. Baeza
Carlos Roca
Andrea Stirpe
mymage
Rémi
Andrea Stirpe
Thanakrit Pintana
ellbristow
claudiagn
BT-nstuder
oihane
dufresnedavid
achulii
Jairo Llopis
Ivorra78
dsolanki
Corneliuus