Advanced Search

blazini36 wrote:

"What would the open function do?"

If you use flexqss to make a qss file then close it, your done. You can't edit it after the fact without some File->open type function. There's an awful lot of different selections to make having to make them in 1 sitting.

"Can you elaborate on apply the background colors?"
How do you change the background color without using a theme in the ini? If you specify a qss, the theme doesn't work.....or at least that's what I'm seeing. From my setup, it's either use a flex theme or the background is white.....and my qt theme is dark on my Debian VM. Designer preview shows my ui as dark, launching LinuxCNC with a qss specified it is white....so maybe I'm missing something.
 

I can see the usefulness of being able to open a qss file and set the various widget stylesheet properties.

Yes it is either use a theme or create your own qss stylesheet and use that.

As for the main window background color I need to add that but in the mean time...

JT

So I understand correctly that you have the Progressbar of the currently running program twice? Once under the G-code and once in the G-code properties?

But usually one have its G-code in one directory

Am I the only one who uses folders for different projects?
I have a huge problem when I upload files to a user's machine and they are in a folder and then I leave. Then they call me and it is very difficult to direct them to the correct folder because they don't know where they are. Plus most of my friends use Windows so they are looking for C:\

No, you do not need two LAN ports, one port and a dedicated Ethernet switch will do,
but you do need two different IP addresses on the 7I92s.

I would suggest 10.10.10.10 and 10.10.10.11 and a host address of 10.10.10.100.

In addition for efficiency the reads should be queued, that is, instead of:

addf 7i92.0.read servo-thread
addf 7i92.1.read servo-thread
__________________________________ bunch of other addfs

addf 7i92.0.write servo-thread
addf 7i92.1.write servo-thread

You should have:

addf 7i92.0.read-request servo-thread
addf 7i92.1.read-request servo-thread
addf 7i92.0.read servo-thread
addf 7i92.1.read servo-thread
__________________________________ bunch of other addfs

addf 7i92.0.write servo-thread
addf 7i92.1.write servo-thread


This is more time efficient as is does not wait for the first 7I92s response
before requesting read data from the second.