Flexible GUI

JT
Topic Author
Away
Administrator

22 Jan 2025 13:58 #319638 by JT

Replied by JT on topic Flexible GUI

blazini36 wrote:
The file browser is a little hard to navigate because it doesn't show the current directory, easy to get lost. Any chance you can add current directory at the top or something?

Do you have an example of what you mean? I'm having a hard time visualizing that...

JT

Please Log in or Create an account to join the conversation.

blazini36
Away
Platinum Member

22 Jan 2025 19:48 #319665 by blazini36

Replied by blazini36 on topic Flexible GUI

JT wrote:
The ini entry INPUT is now THEME gnipsel.com/linuxcnc/flexgui/ini.html#themes

Which file browser, the keyboard or the touch screen?

Good point on the flood and mist and I see no reason to disable them at any time and that has been fixed.

JT

THEME = touch overrides my qss. I get the touch file browser back be it's using whatever qss the theme uses instead of the one I specified with QSS =. Can I add the touch style file browser to my qss?

As for the file browser showing the current directory, just some bar at the top of the browser or maybe even a label that can display it above the file browser. Right now you see files in the directory that you are in....but you have no idea what directory you are in. I keep most of my NC files on a NAS so sometimes I move around a bit to get to the file. It's alot easier to navigate if you can see what directory you are currently browsing.

BTW, thanks for answering these questions. I can probably figure some of this out myself but that probably wouldn't help anyone else looking to work with Flex.

Please Log in or Create an account to join the conversation.

JT
Topic Author
Away
Administrator

22 Jan 2025 21:48 #319679 by JT

Replied by JT on topic Flexible GUI

blazini36 wrote:

JT wrote:
The ini entry INPUT is now THEME gnipsel.com/linuxcnc/flexgui/ini.html#themes

Which file browser, the keyboard or the touch screen?

Good point on the flood and mist and I see no reason to disable them at any time and that has been fixed.

JT

THEME = touch overrides my qss. I get the touch file browser back be it's using whatever qss the theme uses instead of the one I specified with QSS =. Can I add the touch style file browser to my qss?

As for the file browser showing the current directory, just some bar at the top of the browser or maybe even a label that can display it above the file browser. Right now you see files in the directory that you are in....but you have no idea what directory you are in. I keep most of my NC files on a NAS so sometimes I move around a bit to get to the file. It's a lot easier to navigate if you can see what directory you are currently browsing.

BTW, thanks for answering these questions. I can probably figure some of this out myself but that probably wouldn't help anyone else looking to work with Flex.

From the manual gnipsel.com/linuxcnc/flexgui/ini.html THEME is checked first then QSS so the first entry found is used.

I should be able to add the current directory to the touch file browser.

JT

Please Log in or Create an account to join the conversation.

JT
Topic Author
Away
Administrator

22 Jan 2025 23:40 #319685 by JT

Replied by JT on topic Flexible GUI

Sorry missed one of your questions and yes the touch screen file browser is here
gnipsel.com/linuxcnc/flexgui/touch.html#file-navigator

JT

Please Log in or Create an account to join the conversation.

blazini36
Away
Platinum Member

23 Jan 2025 09:24 #319700 by blazini36

Replied by blazini36 on topic Flexible GUI

JT wrote:
Sorry missed one of your questions and yes the touch screen file browser is here
gnipsel.com/linuxcnc/flexgui/touch.html#file-navigator

JT

Lol I think were moving past each other here. I see that "theme is checked first". I also have file_lw, I have the browser....that's not the issue.

The thing that is not really clear is that you can't use a qss file and still have any way to use the touch style widgets. It wasn't obvious until I looked in libflexgui and the python file that the THEME is just a premade qss file and the touch style widgets are just properties in the qss.

So I suppose the best way to have custom colors and the touch style stuff is just to copy the touch THEME qss out of libflexgui and stick it in the config directory, point at it with QSS and just modify it, otherwise it won't survive an update. I suppose this is probably where INPUT was going but that's probably a bit more difficult to impliment since it's written directly into the main qss.

Please Log in or Create an account to join the conversation.

blazini36
Away
Platinum Member

23 Jan 2025 10:58 #319703 by blazini36

Replied by blazini36 on topic Flexible GUI

I copied out the Qlistwidget from the touch theme to my qss and it works pretty much the same as the touch them but I noticed the same problem on both......

If you hit a directory with a file name that is too long it will resize the Qlistwidget horizonally and push the scroll bar out of view. Any idea how to fix this?

Please Log in or Create an account to join the conversation.

JT
Topic Author
Away
Administrator

23 Jan 2025 11:55 #319708 by JT

Replied by JT on topic Flexible GUI

blazini36 wrote:

JT wrote:
Sorry missed one of your questions and yes the touch screen file browser is here
gnipsel.com/linuxcnc/flexgui/touch.html#file-navigator

JT

Lol I think were moving past each other here. I see that "theme is checked first". I also have file_lw, I have the browser....that's not the issue.

The thing that is not really clear is that you can't use a qss file and still have any way to use the touch style widgets. It wasn't obvious until I looked in libflexgui and the python file that the THEME is just a premade qss file and the touch style widgets are just properties in the qss.

So I suppose the best way to have custom colors and the touch style stuff is just to copy the touch THEME qss out of libflexgui and stick it in the config directory, point at it with QSS and just modify it, otherwise it won't survive an update. I suppose this is probably where INPUT was going but that's probably a bit more difficult to implement since it's written directly into the main qss.

Yes, touch style widgets are defined in the qss file.

You can only apply style to a widget once AFAIK the second time over writes the first time.

I added the themes to the examples so they are easier to find.

I've possibly improved the docs about themes.

JT

Please Log in or Create an account to join the conversation.

JT
Topic Author
Away
Administrator

23 Jan 2025 12:26 #319709 by JT

Replied by JT on topic Flexible GUI

blazini36 wrote:
I copied out the Qlistwidget from the touch theme to my qss and it works pretty much the same as the touch them but I noticed the same problem on both......

If you hit a directory with a file name that is too long it will resize the Qlistwidget horizonally and push the scroll bar out of view. Any idea how to fix this?

The width is set here based on the width of the longest item. I'm working on making that an ini selection to turn that feature on but I need to fix the touch style sheets sliders to work as expected.

JT

Please Log in or Create an account to join the conversation.

JT
Topic Author
Away
Administrator

23 Jan 2025 13:56 #319715 by JT

Replied by JT on topic Flexible GUI

[FLEX]
TOUCH_FILE_WIDTH = True

[FLEX]
TOUCH_FILE_WIDTH = False

Please Log in or Create an account to join the conversation.

blazini36
Away
Platinum Member

24 Jan 2025 16:43 - 24 Jan 2025 18:14 #319767 by blazini36

Replied by blazini36 on topic Flexible GUI

Cool, that oughtta do it. I'll update my Flexgui as soon as I get done messing with HAL,

Having a little trouble with the GUI Estop. I have a hardware Estop as well, connected to halui. Both the GUI and the hard Estop work perfectly as long as I'm using one or the other. The hard Estop triggers the GUI just the same as the GUI Estop does.

The problem occurs when I have the hardware Estop set and push the GUI Estop button, the UI Estop will unset the Estop condition. Not quite sure how I stop that from happening.

Heres my HAL connections:

[code]##Estop Connections
net estop-NO-switch   => halui.estop.activate
net estop-NO-switch   => oneshot.estop.in     #Oneshot triggers reset from hardware Estop release
net estop-out   <= iocontrol.0.user-enable-out
net estop-out   => iocontrol.0.emc-enable-in
#net estop-out   => motion.enable
net estop-reset <= oneshot.estop.out
net estop-reset => halui.estop.reset
net estop-in    <= halui.estop.is-activated
net estop-in    => flash.estop.enable
net estop-led   <= flash.estop.out
setp flash.estop.hold-prec       false
setp flash.estop.hold-prec-inv   false
setp flash.estop.hold            false
setp flash.estop.flash-rate-ms   500
setp oneshot.estop.width         0.5
setp oneshot.estop.retriggerable false
setp oneshot.estop.rising        false
setp oneshot.estop.falling       true

[/code]

Just noticed another issue. I have the UI Estop button colors set in the ini file. If I ignore the hardware Estop, the button colors change as expected with Estop and power. If I set the hardware Estop, the UI states work fine, and the button labels change, but the button colors don't change.

Also, just tried the multi-state label. I can't get the hal pin to show up, am I doing something wrong?

Last edit: 24 Jan 2025 18:14 by blazini36.

Please Log in or Create an account to join the conversation.

Time to create page: 0.144 seconds

Flexible GUI

Attachments:

Attachments: