Thanks, I did figure out I can use -H and add hal files to the gladevcp
commands, and that works.
On 04/01/2015 04:34 PM, Chris Morley wrote:
>
> Perfect. I will look into that when I'm off work. I think you are using 2.7?
> Chris M
>
> ----- Reply message -----
> From: "Moses McKnight" <mo...@texband.net>
> To: <emc-developers@lists.sourceforge.net>
> Subject: [Emc-developers] Gscreen runs postgui.hal before embedded tabs are
> ready
> Date: Wed, Apr 1, 2015 1:58 PM
>
>
> I added -d to the gladevcp and gscreen commands, and below is the output.
>
> As you can see at the end the postgui file is getting run and then the two
> embedded tabs are created.
>
>
> LINUXCNC - 2.7.0~pre5
> Machine configuration directory is
> '/mnt/data1/Projects/linuxcnc/linuxcnc-dev/configs/candcnc/cccplasma'
> Machine configuration file is 'cccgscreen.ini'
> Starting LinuxCNC...
> Found file:/mnt/data1/Projects/linuxcnc/linuxcnc-dev/lib/hallib/core_sim.hal
> Note: Using POSIX non-realtime
> Found
> file:/mnt/data1/Projects/linuxcnc/linuxcnc-dev/lib/hallib/axis_manualtoolchange.hal
> Found
> file:/mnt/data1/Projects/linuxcnc/linuxcnc-dev/lib/hallib/simulated_home.hal
> Found file:./ccc_main.hal
> **** GSCREEN INFO: audio available!
> **** GSCREEN INFO ini:
> /mnt/data1/Projects/linuxcnc/linuxcnc-dev/configs/candcnc/cccplasma/cccgscreen.ini
> **** GSCREEN INFO: Skin name = cccgscreen
>
> **** GSCREEN INFO: Using CUSTOM glade file from
> /mnt/data1/Projects/linuxcnc/linuxcnc-dev/configs/candcnc/cccplasma/cccgscreen.glade
> ****
>
> **** GSCREEN INFO: No Screen 2 glade file present
> **** GSCREEN INFO: handler file path:
> ['/mnt/data1/Projects/linuxcnc/linuxcnc-dev/configs/candcnc/cccplasma/cccgscreen_handler.py']
> adding import dir
> /mnt/data1/Projects/linuxcnc/linuxcnc-dev/configs/candcnc/cccplasma
> module 'cccgscreen_handler' imported OK
> module 'cccgscreen_handler' : 'get_handlers' function found
> Registering handlers in module cccgscreen_handler object
> <cccgscreen_handler.HandlerClass instance at 0x7f7d967247e8>
> Register callback 'check_mode' in cccgscreen_handler
> Register callback 'connect_signals' in cccgscreen_handler
> Register callback 'initialize_pins' in cccgscreen_handler
> Register callback 'initialize_widgets' in cccgscreen_handler
> Register callback 'jog_x' in cccgscreen_handler
> Register callback 'jog_y' in cccgscreen_handler
> Register callback 'jog_z' in cccgscreen_handler
> Register callback 'on_gremlin_line_clicked' in cccgscreen_handler
> Register callback 'on_gremlin_radiobutton_toggled' in cccgscreen_handler
> Register callback 'on_gremlin_view_toggled' in cccgscreen_handler
> Register callback 'on_hal_status_all_homed' in cccgscreen_handler
> Register callback 'on_jog_speed_changed' in cccgscreen_handler
> Register callback 'on_keycall_ESTOP' in cccgscreen_handler
> Register callback 'on_keycall_INCREMENTS' in cccgscreen_handler
> Register callback 'on_keycall_POWER' in cccgscreen_handler
> Register callback 'on_offset_origin_entry_return' in cccgscreen_handler
> Register callback 'on_scale_fo_value_changed' in cccgscreen_handler
> Register callback 'on_scale_jog_value_changed' in cccgscreen_handler
> Register callback 'on_scale_mv_value_changed' in cccgscreen_handler
> Register callback 'on_toolbutton_run_toggled' in cccgscreen_handler
> Register callback 'on_touch_off_clicked' in cccgscreen_handler
> Register callback 'periodic' in cccgscreen_handler
> /mnt/data1/Projects/linuxcnc/linuxcnc-dev/bin/gscreen:539: RuntimeWarning:
> missing handler 'on_gremlin_line_changed'
> self.xml.connect_signals(handlers)
> **** GSCREEN INFO: Preference file path: None
> .0001 in
> .001 in
> .01 in
> .1 in
> continuous
> toggle dro units 0 0
> switch to imperial
> timeout 100
> **** GSCREEN INFO: postgui filename: cccgscreen_postgui.hal
> tool change False False 0
> adding import dir .
> module 'thc_box' imported OK
> module 'thc_box': no 'get_handlers' function - registering only functions as
> callbacks
> Registering handlers in module thc_box object <module 'thc_box' from
> './thc_box.pyc'>
> adding import dir .
> module 'thc_settings' imported OK
> module 'thc_settings' : 'get_handlers' function found
> Registering handlers in module thc_settings object <thc_settings.HandlerClass
> instance at 0x7f949c69dc68>
> <class 'Xlib.protocol.request.QueryExtension'>
> activating GTK bug workaround for gtkrc files
> **** GLADE VCP INFO: Switching thc_box to 'Ccc_Mint-X' theme
> <class 'Xlib.protocol.request.QueryExtension'>
> activating GTK bug workaround for gtkrc files
> **** GLADE VCP INFO: Switching thc_settings to 'Ccc_Mint-X' theme
>
>
> On 04/01/2015 03:06 PM, Moses McKnight wrote:
>> Well, I have the following in the ini file:
>>
>> EMBED_TAB_NAME = THC
>> EMBED_TAB_LOCATION = thc_box
>> EMBED_TAB_COMMAND = gladevcp -x {XID} -t Ccc_Mint-X -u thc_box.py
>> thc_box.glade
>>
>> EMBED_TAB_NAME = THC Settings
>> EMBED_TAB_LOCATION = thc_settings
>> EMBED_TAB_COMMAND = gladevcp -x {XID} -t Ccc_Mint-X -u thc_settings.py
>> thc_settings.glade
>>
>> There is no code in the .py files yet, and I tried without the -u *.py as
>> well.
>> As I mentioned, my skin is a modification of Gaxis, and I have changed almost
>> nothing in the _handler.py for it.
>>
>> Moses
>>
>> On 04/01/2015 01:54 PM, Chris Morley wrote:
>>>
>>> What command are you using to load the tab? If the tab pins load after
>>> gscreen this would happen. Seeing code would help.
>>> Chris M
>>>
>>> ----- Reply message -----
>>> From: "Moses McKnight" <mo...@texband.net>
>>> To: <emc-developers@lists.sourceforge.net>
>>> Subject: [Emc-developers] Gscreen runs postgui.hal before embedded tabs are
>>> ready
>>> Date: Wed, Apr 1, 2015 9:22 AM
>>>
>>>
>>> Hi,
>>>
>>> I'm building a custom skin for Gscreen based on the Gaxis skin. I have 2
>>> embedded gladevcp tabs/panels, and HAL widgets on them. In the postgui.hal
>>> file
>>> I connect pins from one of these embedded tabs to pins from my custom
>>> component.
>>>
>>> In Axis, or just plain Gscreen with no custom skin, this seems to work fine.
>>> But using my custom Gaxis skin, Linuxcnc exits before it gets started
>>> complaining that the HAL pins in the embedded tab do not exist.
>>>
>>> If I comment out the lines in the postgui.hal connecting those pins, I can
>>> start
>>> the screen and can see the pins in halshow.
>>>
>>> So, it seems that I'm doing something wrong or there is a bug that runs the
>>> postgui.hal before the embedded tabs have created their pins.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Moses
>>>
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website,
>>> sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for
>>> all
>>> things parallel software development, from weekly thought leadership blogs
>>> to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website,
>>> sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub for
>>> all
>>> things parallel software development, from weekly thought leadership blogs
>>> to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> Emc-developers mailing list
>>> Emc-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for
>> all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
