| Line 1... |
Line -... |
| 1 |
Bargraphs
|
- |
|
| 2 |
=========
|
- |
|
| 3 |
* A bargraph with a slider button can't be moved free as long as a mouse press
|
- |
|
| 4 |
on the bargraph is active. This must be implemented.
|
- |
|
| 5 |
|
- |
|
| 6 |
Buttons
|
1 |
Buttons
|
| 7 |
=======
|
2 |
=======
|
| 8 |
* Add marquee function
|
- |
|
| 9 |
* Implement text area buttons completly
|
- |
|
| 10 |
* Add command ^BMF
|
3 |
* Add command ^BMF
|
| 11 |
- Set video on off
|
4 |
- Set video on off
|
| 12 |
- Text area an input masks
|
- |
|
| 13 |
- Bargraph control
|
- |
|
| 14 |
|
5 |
|
| 15 |
Missing features
|
6 |
Missing features
|
| 16 |
================
|
7 |
================
|
| 17 |
* Add more commands (as always)
|
8 |
* Add more commands (as always)
|
| 18 |
* Crack the encryption of TP5 internal file.
|
9 |
* Crack the encryption of TP5 internal file.
|
| 19 |
* Crack the encryption of passwords in resources.
|
10 |
* Crack the encryption of passwords in resources.
|
| 20 |
* Implement panel to panel audio communication.
|
11 |
* Implement panel to panel audio communication.
|
| 21 |
* Implemet commands to control a view
|
- |
|
| 22 |
* Implement commands to control a list
|
12 |
* Implement commands to control a list
|
| 23 |
* Implement a joystick
|
- |
|
| 24 |
|
13 |
|
| 25 |
Known errors
|
14 |
Known errors
|
| 26 |
============
|
15 |
============
|
| 27 |
* On a mobile device the surface may become a destructive look if the app is
|
- |
|
| 28 |
suspended and loose network connection. In this case a new connection is
|
- |
|
| 29 |
established, which work, but the surface can't be drawn. This leads into loss
|
- |
|
| 30 |
of graphics. Seen this on a Samsung tablet Galaxy A7.
|
- |
|
| 31 |
|
- |
|
| 32 |
* Sometimes the application crashes on mobile devices. It seems that the Qt
|
- |
|
| 33 |
framework may be the course. But it could be that the handling of that
|
- |
|
| 34 |
framework is wrong. This would be my fault.
|
- |
|
| 35 |
|
- |
|
| 36 |
* While Views are working it is poosible that when another page is shown and
|
16 |
* While Views are working it is poosible that when another page is shown and
|
| 37 |
switched back to the previous page the view doesn't react any more. Here the
|
17 |
switched back to the previous page the view doesn't react any more. Here the
|
| 38 |
framework simply forgets to send mouse events to the widget. I found no way
|
18 |
framework simply forgets to send mouse events to the widget. I found no way
|
| 39 |
to restore the internal event table to what it should be.
|
19 |
to restore the internal event table to what it should be.
|
| 40 |
|
20 |
|
| - |
|
21 |
* On Linux with Wayland objects may look incomplete or they look like
|
| - |
|
22 |
something is above them and hiding them partly. This is a problem with Qt6
|
| - |
|
23 |
and Wayland. The same binary on X11 works as expected.
|
| - |
|
24 |
|
| - |
|
25 |
* Views are resetting to initial state when they are on a page drawn the second
|
| - |
|
26 |
time.
|
| - |
|
27 |
|
| - |
|
28 |
* If there are too many objects on a page or subpage, views may become
|
| - |
|
29 |
unresponsive. It is very likely that this is because it takes too much time
|
| - |
|
30 |
to draw all the objects and the internal event loop of Qt6 is missing some
|
| - |
|
31 |
events. Then some objects, like the scroll area of a view will not get any
|
| - |
|
32 |
mouse events any more. The same can happen on any other type of object.
|
| - |
|
33 |
|
| 41 |
Documentation
|
34 |
Documentation
|
| 42 |
=============
|
35 |
=============
|
| 43 |
* Add documentation for configuration files
|
36 |
* Add documentation for configuration files
|