| 31 |
andreas |
1 |
Buttons
|
|
|
2 |
=======
|
| 150 |
andreas |
3 |
* Add command ^BMF
|
|
|
4 |
- Set video on off
|
| 31 |
andreas |
5 |
|
| 121 |
andreas |
6 |
Missing features
|
|
|
7 |
================
|
| 361 |
andreas |
8 |
* Add more commands (as always)
|
| 102 |
andreas |
9 |
* Crack the encryption of TP5 internal file.
|
|
|
10 |
* Crack the encryption of passwords in resources.
|
|
|
11 |
* Implement panel to panel audio communication.
|
| 361 |
andreas |
12 |
* Implement commands to control a list
|
| 31 |
andreas |
13 |
|
| 104 |
andreas |
14 |
Known errors
|
|
|
15 |
============
|
| 361 |
andreas |
16 |
* While Views are working it is poosible that when another page is shown and
|
|
|
17 |
switched back to the previous page the view doesn't react any more. Here the
|
|
|
18 |
framework simply forgets to send mouse events to the widget. I found no way
|
|
|
19 |
to restore the internal event table to what it should be.
|
|
|
20 |
|
| 439 |
andreas |
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 |
|
| 102 |
andreas |
34 |
Documentation
|
|
|
35 |
=============
|
|
|
36 |
* Add documentation for configuration files
|