17df8c547a
Since odoo/documentation#903, the guideline for the location of new resource (images, downloadable files, RST includes...) files is to place those inside the directory of the RST page that references them. For example, if `doc1.rst` has a reference to `image.png` and to `download.zip`, the file structure should look like this: ├── parent_doc/ │ └── doc1/ │ │ └── image.png │ │ └── download.zip │ └── doc1.rst │ └── doc2.rst ├── parent_doc.rst Before this commit, most of the resource files were still located inside 'media' directories holding all the resource files referenced by RST pages located at the same level as these directories. In the example above, a single 'media' directory would hold all the resource files referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from figuring out easily which resource file was referenced by which RST page and, thus, lead to unused resource files piling up in the repository. It also made it more complicated to define codeowners regex rules because a team could not simply be assigned to `/some_page.*` but needed to be assigned to both `/some_page\.rst` and to the location of 'media'. In order to help new content writers figure out the guideline when taking examples from other RST pages, this commit retroactively applies the guideline to existing resource files and 'media' directories. The left-over resource files that are not referenced by any RST page are removed. task-2497965 Part-of: odoo/documentation#2064
42 lines
1.4 KiB
ReStructuredText
42 lines
1.4 KiB
ReStructuredText
====================
|
||
Connect a Footswitch
|
||
====================
|
||
|
||
When working, it is always better to have your two hands available.
|
||
Using Odoo’s *IoT Box* and a footswitch will allow it.
|
||
|
||
In fact, you will be able to go from one screen to another and perform
|
||
actions by using your foot and the footswitch. Really convenient, it
|
||
can be configured in a few steps.
|
||
|
||
Connection
|
||
==========
|
||
|
||
Connecting the footswitch to the *IoT Box* is easy, you just have to
|
||
connect the two by cable.
|
||
|
||
If your footswitch is a `supported
|
||
one <https://www.odoo.com/page/iot-hardware>`__, there is no need to
|
||
set up anything since it will be automatically detected when connected.
|
||
|
||
.. image:: footswitch/footswitch_01.png
|
||
:align: center
|
||
|
||
Link a Footswitch to a Workcenter
|
||
=================================
|
||
|
||
To link the footswitch to an action, it needs to be configured on a
|
||
workcenter. Go to the workcenter you want to use the footswitch in and
|
||
add the device in the *IoT Triggers* tab. Then, you can link it to an
|
||
action and also add a key to trigger it.
|
||
|
||
.. image:: footswitch/footswitch_03.png
|
||
:align: center
|
||
|
||
Note that the one that is first in the list will be chosen. So, the
|
||
order matters! In the picture above, using the footswitch will, for
|
||
example, automatically skip the current part of the process you work on.
|
||
|
||
.. note::
|
||
When you are on the work order screen, a status button indicates if you
|
||
are correctly connected to the footswitch. |