View Single Post
Old 03-13-2023, 11:56 PM   #824
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
I have been going through the Qt6 Tab Order and setProxy documentation, making a lot of additions to NV's pyQt code for tabbing. Still a lot more testing and fixing to do.

There are 3 qtextedits, actually. 1 each for plain, markdown and html. They occupy the same location but 2 are always hidden, their focus proxy (for tabbing) given to the visible/enabled one, and then they are disabled.

In View Mode, the visible/active qtextedit is Read-Only, which is probably why the tab won't stop there.

Note that tab goes in one direction (the opposite direction down under), and shift+tab goes the opposite. I have also been testing the use of the arrow keys that pick up where the tab left off when it stops in a 'group' of widgets, such as a radio-button group that allows only one 'on' at a time.

The dropdown combobox doesn't yet show 'focus' as visually different; I am going to look at its css and its other attributes to fix that issue.

BTW, all of the widgets are enabled for accepting focus via tabbing, clicking, and the mouse wheel. There is nothing else available that they don't already have now.


To be continued.


DaltonST
DaltonST is offline   Reply With Quote