Repository navigation
Releases
Releases · RadicalES/robot-qt-browser
main v3.6.11
Release 3.6.11
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.10
Release 3.6.10
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.7
[3.6.7] - 2026-08-27
Fixed
- The side-docked keyboard held its column before it had ever been raised.
3.6.6 fixed this for the keyboard that docks along the bottom and missed the
one that docks down the side — which is what a 1024x600 panel uses, so on a
T431 the black band was still there on first load. Down the side it is the
width that is given and taken back, and that only happened on a change of
state; the column now starts collapsed, as the bottom one does.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.6
[3.6.6] - 2026-08-27
Fixed
- The keyboard reserved an empty black band before it had ever been raised.
On first load the space under the page was taken but no keys were drawn. The
panel's height is set from the QML root'sheightChanged, which fires on a
change, and the root loads already zero-high — so no height was ever set and
the layout used the size hint instead. Raising the keyboard once, by the
toolbar button or by tapping a field, corrected it, which is what made it
look like a state problem rather than a missing initial value.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.5
[3.6.5] - 2026-08-24
Fixed
- The lock screen forced a window wider than a narrow panel. Its code field
asked for a fixed 560px, and with the reveal button and margins that came to
more than a 720x1280 T440 has — so the window could not be as small as the
screen, and the compositor gave it decorations and pushed part of it off the
edge. The field now follows the width available, as the rest of the screen
already followed the height.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.4
[3.6.4] - 2026-08-24
Changed
- The clock sits at the end of the toolbar. It was between the keyboard
button and the Lock and Info actions, which put a read-only display in the
middle of the things you press. The controls read as a group now.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.3
[3.6.3] - 2026-08-24
Fixed
- The lock screen ran off a short panel. It was laid out for a tall one — a
T440 at 720x1280 looked right, a T431 at 1024x600 lost its field and button
off the bottom once the toolbar had taken its share. Every size now follows
the height actually available, and on a very short panel the product mark is
dropped rather than the field: the mark is decoration, the field is not.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.2
[3.6.2] - 2026-08-24
Fixed
- A terminal switched to Secure while running had no way to sign off. The
lock button was created only when security was on at startup, so a terminal
that booted Open and was later marked Secure locked itself correctly and then
offered nothing to lock it again. Security is a setting that changes while the
terminal runs, so nothing may depend on its value at startup. - Home, Remote and Back worked while the terminal was locked, on the page
behind the lock — so anybody could navigate a terminal they had not signed on
to, and the operator did not come back to what they left. They are disabled
while locked. WiFi, LAN, SCADA state and Info stay reachable on purpose:
those fix a terminal rather than drive it.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.1
[3.6.1] - 2026-08-24
Changed
- The package describes what it actually is. The description had been
written for a different product — "Kiosk browser for embedded Linux robots …
for Raspberry Pi CM4 and Raspberry Pi 5" — naming neither amd64 nor the
ITPC-200, and none of what a buyer chooses it for. This is not only apt
metadata: the catalogue oncdn.radsys.iobuilds its download listing from
this field, so editing the website would not have changed it. - The package says which terminals it runs on, in
X-Radical-Products, so
the catalogue can show it without a second list on the website that drifts.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browsermain v3.6.0
[3.6.0] - 2026-08-24
Added
- A terminal can lock, and ask who is signing on. A terminal in a packhouse
is a shared machine: it runs unattended between transactions, and whoever
walks past gets whatever the last operator left open. It now behaves like a
desktop — it asks who you are before showing the page, and locks itself again
when nobody has touched it. - The site decides, on the server. A terminal marked Secure Terminal
hassecurity=SECUREin the setuprobot-scada-clientpublishes, and that
is what turns this on. Switching it back to Open removes the lock within
seconds, with no restart and no visit — the setting is followed while the
terminal runs, not read once at boot.WB_SECURITYonly decides for a
terminal the server has never spoken to. - A worker signs on with one value, keyed on the pad or presented as a
card. Cards and scanned badges arrive fromwsrobot's websocket, which
serves every reader on the terminal over one socket, and the[0]a
multi-reader terminal prefixes is stripped — it is decoration on a card
number, not a different card. The card option only appears when a reader is
actually connected. - Signing on is a check, not an authentication. It posts the Robot API's
publishLogonand reads the answer; a refusal shows the server's own wording,
because "Invalid Card Number / Worker not found" is what whoever the operator
calls will recognise. Being refused and being unable to ask are different
states and read differently. - Locking signs the worker off, with
publishLogoff— on the idle timeout,
on the toolbar's lock button, and on shutdown. A terminal switched off
mid-shift would otherwise leave a session nobody closes, and the record would
say the worker never went home. - The lock timeout is in Settings, defaulting to five minutes. Whether a
terminal locks is not a setting there: a terminal that could switch its own
lock off would not be a secure terminal.
Changed
- The lock covers the page and not the toolbar. WiFi, LAN, SCADA state and Info
stay reachable without signing on, because a terminal whose network has died
has to be fixable at the terminal, and none of those show a customer's data. - The page keeps its state behind the lock, so unlocking returns the operator to
exactly where they were. An idle lock never costs somebody their work.
Fixed
- A page could put a dialog on top of the lock. A page asking for HTTP
credentials does it in a modal dialog, so a terminal meant to be asking who
you are instead showed a password box for a page nobody had signed on to see.
The request is refused while locked and the page reloaded on unlock, when
there is somebody to answer it. - The keyboard swallowed every keystroke on the lock screen. The Keyboard
button focused the web view unconditionally, and while locked that view is
hidden — so the panel appeared and the typing went into a page nobody could
see, which reads exactly like a keyboard that does not work. - The idle countdown ran from the last touch rather than from the sign-on,
so a terminal observed on hardware locked three minutes after a worker signed
on instead of five. The five minutes belong to their session.
Install
Packages are available from the Radical ES Debian repository:
sudo apt update
sudo apt install robot-browser