Gmoccapy - A new screen for linuxcnc
10 Sep 2014 03:38 #50987
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@Anders,
I will take a look, i have been thinking about that feature allready, but missed to implement it. But you will be forced to do also some work, like Rick was:-)
What about if i ask you for the needed icon?
Or making a handbook with the wiki info, so we can include the Information in the 2.6 deb packets?
Or a new translation to have even more languages?
Or.....
I will not implement more features if i remain beeing a one man show:-)
@probamo
Please post screenshots of:
- start fullscreen
- start maximized
- start as Window with min possible size.
See the settings page for the different options.
I do beleave you have not realized the differences, as you mentioned the window decoration.
Norbert
I will take a look, i have been thinking about that feature allready, but missed to implement it. But you will be forced to do also some work, like Rick was:-)
What about if i ask you for the needed icon?
Or making a handbook with the wiki info, so we can include the Information in the 2.6 deb packets?
Or a new translation to have even more languages?
Or.....
I will not implement more features if i remain beeing a one man show:-)
@probamo
Please post screenshots of:
- start fullscreen
- start maximized
- start as Window with min possible size.
See the settings page for the different options.
I do beleave you have not realized the differences, as you mentioned the window decoration.
Norbert
Please Log in or Create an account to join the conversation.
10 Sep 2014 04:01 #50989
by cncbasher
Replied by cncbasher on topic Gmoccapy - A new screen for linuxcnc
probamo:
perhaps try opening the settings panel in gmoccapy and in main window , select start as window
and then change width & height values from 979 & 750 , then select start maximised
and see if changing these helps
perhaps try opening the settings panel in gmoccapy and in main window , select start as window
and then change width & height values from 979 & 750 , then select start maximised
and see if changing these helps
Please Log in or Create an account to join the conversation.
11 Sep 2014 01:42 #51044
by probamo
Replied by probamo on topic Gmoccapy - A new screen for linuxcnc
Norb,
cncbasher,
I tried all possibility. No need for hidden panels any more . I run well with full screen, the icons at the bottom are fully visible.
Thank you,
cncbasher,
I tried all possibility. No need for hidden panels any more . I run well with full screen, the icons at the bottom are fully visible.
Thank you,
Please Log in or Create an account to join the conversation.
- microsprintbuilder
- Offline
- Elite Member
Less
More
- Posts: 163
- Thank you received: 4
14 Sep 2014 21:33 - 14 Sep 2014 21:45 #51156
by microsprintbuilder
Replied by microsprintbuilder on topic Gmoccapy - A new screen for linuxcnc
I'm trying out this screen and like it. I have some mysteries numbers running threw the tool info area in the screen. can anyone tell me what I need to do where to look to get rid of them.
Last edit: 14 Sep 2014 21:45 by microsprintbuilder. Reason: photo didn't show
Please Log in or Create an account to join the conversation.
14 Sep 2014 21:39 #51157
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Hi
Look in the INI file under the [TRAJ] section you will find and entry MAX_LINEAR_VELOCITY = xxx. Change that entry to MAX_VELOCITY = xxx
Look in the INI file under the [TRAJ] section you will find and entry MAX_LINEAR_VELOCITY = xxx. Change that entry to MAX_VELOCITY = xxx
Regards
Marius
www.bluearccnc.com
The following user(s) said Thank You: microsprintbuilder
Please Log in or Create an account to join the conversation.
- microsprintbuilder
- Offline
- Elite Member
Less
More
- Posts: 163
- Thank you received: 4
14 Sep 2014 21:50 #51158
by microsprintbuilder
Replied by microsprintbuilder on topic Gmoccapy - A new screen for linuxcnc
That fixed it. Thanks!
Please Log in or Create an account to join the conversation.
14 Sep 2014 23:37 #51160
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
As the strange number matter did occure several times and is not caused by gmoccapy,
I made a new part in the WIKI page, named "Known problems"
See gmoccapy known problems
I would appreciate much, if you guys just add other probelms you noticed.
Norbert
I made a new part in the WIKI page, named "Known problems"
See gmoccapy known problems
I would appreciate much, if you guys just add other probelms you noticed.
Norbert
Please Log in or Create an account to join the conversation.
16 Sep 2014 04:25 #51206
by PKM
Replied by PKM on topic Gmoccapy - A new screen for linuxcnc
Norbert, I just run gmoccapy for the first time and I'm delighted! Thank you
I'm going to use for a lathe I'm retrofitting, with the touchscreen LCD.
Just a couple of hardware buttons and MPG, jog selector and feed/spindle knobs... probably all that on the remote pendant with 7i73. Makes the panel very simple.
But I found that the onscreen keyboard won't appear (hybrid iso, LCNC 2.6.3). What could be wrong?
I'm going to use for a lathe I'm retrofitting, with the touchscreen LCD.
Just a couple of hardware buttons and MPG, jog selector and feed/spindle knobs... probably all that on the remote pendant with 7i73. Makes the panel very simple.
But I found that the onscreen keyboard won't appear (hybrid iso, LCNC 2.6.3). What could be wrong?
Please Log in or Create an account to join the conversation.
16 Sep 2014 14:31 #51229
by cncbasher
Replied by cncbasher on topic Gmoccapy - A new screen for linuxcnc
install this keyboard
by typing from a terminal sudo apt-get install matchbox-keyboard
and make sure your install is up to date
by typing from a terminal sudo apt-get install matchbox-keyboard
and make sure your install is up to date
Please Log in or Create an account to join the conversation.
16 Sep 2014 23:21 #51239
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@PKM
unfortunately DEBIAN WHEESY does not have a pakage for the virtual keyboard onboard.
So I changed the code to work also with matchbox-keyboard wich can be installed using
sudo apt-get install matchbox-keyboard
If non of both is found, I disable the on screen keyboard and all related buttons.
By the way, I am using a hardware keyboard most of the time.
I do know matchbox-keyboard is ugly and has less options than onboard, but till we find someoen to build the onboard pakage for Wheesy, we will have to live with the solution.
If you want to change the layout of the matchbox-keyboard, you will have to make a hidden directory
.matchbox-keyboard
in your home directory and kopy one of the xml layout examples from usr/share/matchbox-keyboard and rename that one to keyboard.xml. Than you can edit it. This file will be loaded by default.
Here are the latest changes to gmoccapy, please take care you are using 1.2.2
ver. 1.2.2
- changed the way the window size and position is
handled, as before the default values did appear
several times in the code
- If no virtual keyboard could be initialized, we
disable now the corresponding part on the settings
page and the related button. Check will be done
for <onboard> and <matchbox-keyboard>
- starting gmoccapy did throw an error to the terminal
that a widget could not get default. Finally I found
the reason, the glade file did contain a property
"has_default" and that is not allowed by builder.
ver. 1.2.1
- due to the behavior of XFCE of the new hybrid.iso I
had to change the width settings of several button
to stretch them to fit some text and images
- The same reason forced to set new default startposition
of the main window and the notification messages.
ver. 1.2.0
- changed GetIniInfo to return also user message setups
- notification now supports pango markup in the messages
- added hal user messages similar to gsreeen to gmoccapy
see gmoccapy_messages.ini for usage information
- updated the translation files for German and Spanish
The WIKI is up to date, except matchbox-keyboard.
Norbert
unfortunately DEBIAN WHEESY does not have a pakage for the virtual keyboard onboard.
So I changed the code to work also with matchbox-keyboard wich can be installed using
sudo apt-get install matchbox-keyboard
If non of both is found, I disable the on screen keyboard and all related buttons.
By the way, I am using a hardware keyboard most of the time.
I do know matchbox-keyboard is ugly and has less options than onboard, but till we find someoen to build the onboard pakage for Wheesy, we will have to live with the solution.
If you want to change the layout of the matchbox-keyboard, you will have to make a hidden directory
.matchbox-keyboard
in your home directory and kopy one of the xml layout examples from usr/share/matchbox-keyboard and rename that one to keyboard.xml. Than you can edit it. This file will be loaded by default.
Here are the latest changes to gmoccapy, please take care you are using 1.2.2
ver. 1.2.2
- changed the way the window size and position is
handled, as before the default values did appear
several times in the code
- If no virtual keyboard could be initialized, we
disable now the corresponding part on the settings
page and the related button. Check will be done
for <onboard> and <matchbox-keyboard>
- starting gmoccapy did throw an error to the terminal
that a widget could not get default. Finally I found
the reason, the glade file did contain a property
"has_default" and that is not allowed by builder.
ver. 1.2.1
- due to the behavior of XFCE of the new hybrid.iso I
had to change the width settings of several button
to stretch them to fit some text and images
- The same reason forced to set new default startposition
of the main window and the notification messages.
ver. 1.2.0
- changed GetIniInfo to return also user message setups
- notification now supports pango markup in the messages
- added hal user messages similar to gsreeen to gmoccapy
see gmoccapy_messages.ini for usage information
- updated the translation files for German and Spanish
The WIKI is up to date, except matchbox-keyboard.
Norbert
Please Log in or Create an account to join the conversation.
Time to create page: 0.229 seconds