2 hours ago
Yep Yep Yep.... Back to work on Windows Widgets, and a rewrite to the List widget system. By extension, that performs updates to the ListBox, ComboBox and all Widgets that display selectable text entries.
However, I got a bit of a breakthrough, and the List widget no longer requires certain dependencies. Unfortunately, its child class widgets still have dependencies due to having scrolling viewports, but not a basic List.
And have also discovered why NONE of the List based widgets were able to be set invisible! Yep, the .visible= property will soon be working with those widgets as they do all the others. Once done, I will re-verify the .enabled= property on all of the above, and ensure that invisible widgets don't accidentally respond to input of any sort (which would be hilarious but suck).
I know... I know... I have in the initial post that I want to have two more facets of keyboard input added to Windows Widgets, and that being the ability to [TAB] from one widget to another like any other Windows application, or the ability to have widget-defined hotkeys, such as having [Ctrl]+[X] being a hotkey because someone set a button to say "Exit" (noting the underscore beneath the 'x' in Exit).
However, when one uses such options, the widgets that are now under the user's control must reflect that in some way. And within Windows applications, it is a thin 'dotted' line that is drawn along the inner border surrounding the widget's test, if any. Button widgets have a dotted line inside their rectangular shape. And if the CheckBox widget (for both Check or Option circle variations) has text, the helpful text would also have a dotted line. And the List based widgets would have their highlight bar appear in a different shade when it is active.
Meticulous as I was at the onset, I already have all the graphic rendering code in a BASE set of scripts. So finding them will be a breeze. However, additional values indicating which widget is active vs all others will be necessary.
But now..... Time for a steak burrito.
However, I got a bit of a breakthrough, and the List widget no longer requires certain dependencies. Unfortunately, its child class widgets still have dependencies due to having scrolling viewports, but not a basic List.
And have also discovered why NONE of the List based widgets were able to be set invisible! Yep, the .visible= property will soon be working with those widgets as they do all the others. Once done, I will re-verify the .enabled= property on all of the above, and ensure that invisible widgets don't accidentally respond to input of any sort (which would be hilarious but suck).
◄► ● ◄► ● ◄► ● ◄► ● ◄►
I know... I know... I have in the initial post that I want to have two more facets of keyboard input added to Windows Widgets, and that being the ability to [TAB] from one widget to another like any other Windows application, or the ability to have widget-defined hotkeys, such as having [Ctrl]+[X] being a hotkey because someone set a button to say "Exit" (noting the underscore beneath the 'x' in Exit).
However, when one uses such options, the widgets that are now under the user's control must reflect that in some way. And within Windows applications, it is a thin 'dotted' line that is drawn along the inner border surrounding the widget's test, if any. Button widgets have a dotted line inside their rectangular shape. And if the CheckBox widget (for both Check or Option circle variations) has text, the helpful text would also have a dotted line. And the List based widgets would have their highlight bar appear in a different shade when it is active.
Meticulous as I was at the onset, I already have all the graphic rendering code in a BASE set of scripts. So finding them will be a breeze. However, additional values indicating which widget is active vs all others will be necessary.
But now..... Time for a steak burrito.


![[Image: QrnbKlx.jpg]](https://i.imgur.com/QrnbKlx.jpg)
![[Image: sGz1ErF.png]](https://i.imgur.com/sGz1ErF.png)
![[Image: liM4ikn.png]](https://i.imgur.com/liM4ikn.png)
![[Image: fdzKgZA.png]](https://i.imgur.com/fdzKgZA.png)
![[Image: sj0H81z.png]](https://i.imgur.com/sj0H81z.png)
![[Image: QL7oRau.png]](https://i.imgur.com/QL7oRau.png)
![[Image: uSqjY09.png]](https://i.imgur.com/uSqjY09.png)
![[Image: GAA3qE9.png]](https://i.imgur.com/GAA3qE9.png)
![[Image: 2Hmnx1G.png]](https://i.imgur.com/2Hmnx1G.png)
![[Image: BwtNdKw.png%5B]](https://i.imgur.com/BwtNdKw.png%5B)