- Posts: 1931
- Thank you received: 394
Gmoccapy - A new screen for linuxcnc
- newbynobi
- Offline
- Moderator
-
Less
More
12 years 8 months ago #44094
by newbynobi
solved!
ver. 0.9.9.9.14
- The usage of "EMBED_TAB_LOCATION = box_coolant_and_spindle"
will not hide the velocity widgets any more, plasma handles
that one now over tool_info_panel
Norbert
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Is it possible to hide the cooling and/or spindle control groupbox?
I tried to load a gladevcp and set its location in .ini file to "EMBED_TAB_LOCATION = box_coolant_and_spindle", but it causes not only coolant and spindle, but also feed override and velocity box to disappear.
I'm aware i can simply delete or hide those frames directly in gmoccapy.glade, but i think a less intrusive way would be useful, for example being able to hide them from gmoccapy's options.
solved!
ver. 0.9.9.9.14
- The usage of "EMBED_TAB_LOCATION = box_coolant_and_spindle"
will not hide the velocity widgets any more, plasma handles
that one now over tool_info_panel
Norbert
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
12 years 8 months ago #44097
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
ver. 0.9.9.9.15
- new hal pin gscreen.error as bit out, to show an error to the
hardware, so a light can lit or even stop the machine. It will
reseted with the pin gscreen.delete-message. This command will
delete the first error and reset the gscreen.error pin to False
after the last error has been cleared. Messages or user infos
will not affect this pin!
Documented in WIKI.
Norbert
- new hal pin gscreen.error as bit out, to show an error to the
hardware, so a light can lit or even stop the machine. It will
reseted with the pin gscreen.delete-message. This command will
delete the first error and reset the gscreen.error pin to False
after the last error has been cleared. Messages or user infos
will not affect this pin!
Documented in WIKI.
Norbert
- mr_deimos
- Offline
- New Member
-
Less
More
- Posts: 4
- Thank you received: 0
12 years 8 months ago #44141
by mr_deimos
Replied by mr_deimos on topic Gmoccapy - A new screen for linuxcnc
Hi Norbert.
I can confirm that the file list is now properly refreshed each time it's opened, screen dimensions seem to be working fine now (no matter on which monitor the mouse pointer is) and are no longer limited, feed override reset pin works fine with physical button, and coolant/spindle box can now be properly replaced. Thank you, that was fast
As for feed-override-counts i was already using the pin from gscreen instead one from hal. I just mentioned it because i wasn't sure if it was intended behavior or a bug.
Another question about feed override: i noticed that reducing feed override also reduces maximum machine speed. That's a usually good idea especially for test runs, but sometimes it can be troublesome: for example if i manually reduce maximum machine velocity and touch the feed override knob/slider the maximum velocity slider will be moved to automatically calculated value, which can actually be higher than the value i set. So maybe it would be a good idea to add a link/unlink toggle button for these sliders (or an option in settings menu)? That way everyone could use whatever works best for him.
As for gremlin view center, i tried poking around the source code but i'm not skilled enough with python (i am a programmer, but c++ is my language of choice). I tracked view center setting after opening a new file to line 1918 in axis.py. Maybe it'll help a bit.
Thanks again for all your great work.
Rafal
I can confirm that the file list is now properly refreshed each time it's opened, screen dimensions seem to be working fine now (no matter on which monitor the mouse pointer is) and are no longer limited, feed override reset pin works fine with physical button, and coolant/spindle box can now be properly replaced. Thank you, that was fast
As for feed-override-counts i was already using the pin from gscreen instead one from hal. I just mentioned it because i wasn't sure if it was intended behavior or a bug.
Another question about feed override: i noticed that reducing feed override also reduces maximum machine speed. That's a usually good idea especially for test runs, but sometimes it can be troublesome: for example if i manually reduce maximum machine velocity and touch the feed override knob/slider the maximum velocity slider will be moved to automatically calculated value, which can actually be higher than the value i set. So maybe it would be a good idea to add a link/unlink toggle button for these sliders (or an option in settings menu)? That way everyone could use whatever works best for him.
As for gremlin view center, i tried poking around the source code but i'm not skilled enough with python (i am a programmer, but c++ is my language of choice). I tracked view center setting after opening a new file to line 1918 in axis.py. Maybe it'll help a bit.
Thanks again for all your great work.
Rafal
- DaBit
- Offline
- Elite Member
-
Less
More
- Posts: 203
- Thank you received: 19
12 years 8 months ago - 12 years 8 months ago #44173
by DaBit
Replied by DaBit on topic Gmoccapy - A new screen for linuxcnc
I did a GIT pull yesterday as instructed in the gmoccapy wiki, and when using LXDE as the desktop environment I get the following when trying the sim.gmoccapy sample included with LinuxCNC:
And many, many more.
After a few of these messages I see the GUI appearing, but in the end LinuxCNC terminates without anything useful in dmesg/linuxcnc_debug.txt/linuxcnc_print.txt
When switching to Unity as the desktop environment (I installed LXDE as extra on a regular 12.04LTS install) it fires up without these errors. Seems to have something to do with a theme that is not available under LXDE.
Is it possible to use gmoccapy with LXDE? I hate Unity and like the lean-ness and speed of LXDE.
And many, many more.
After a few of these messages I see the GUI appearing, but in the end LinuxCNC terminates without anything useful in dmesg/linuxcnc_debug.txt/linuxcnc_print.txt
When switching to Unity as the desktop environment (I installed LXDE as extra on a regular 12.04LTS install) it fires up without these errors. Seems to have something to do with a theme that is not available under LXDE.
Is it possible to use gmoccapy with LXDE? I hate Unity and like the lean-ness and speed of LXDE.
Last edit: 12 years 8 months ago by DaBit.
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
12 years 8 months ago #44181
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
LXDE does not have gtk.theme, so the corresponding icon could not be found.
May be you have to install gtk ore gtk.theme or something else.
I have not tested with that Window manager, I am working mostly with 10.04, because I do not like UNITY easer.
Norbert
May be you have to install gtk ore gtk.theme or something else.
I have not tested with that Window manager, I am working mostly with 10.04, because I do not like UNITY easer.
Norbert
- Mario
- Offline
- New Member
-
Less
More
- Posts: 1
- Thank you received: 0
12 years 8 months ago #44183
by Mario
Replied by Mario on topic Gmoccapy - A new screen for linuxcnc
I do not like unity too. But what about XFCE? It is also lightweight and brings a classical desktop. I installed xubuntu-desktop on my Ubuntu 10.04 from the livecd and gmoccapy (buildbot) runs without errors.
Mario
Mario
Moderators: newbynobi, HansU
Time to create page: 2.285 seconds