Creating a GUI

ok to run it stand alone:
I assume your using a run-in-place
add you python file into <run-in-place-folder> /bin
make sure it's executable.
and the glade file in <run-in-place-folder /share/linuxcnc

then add some code to your python file so it can find the glade file:
some thing like this (from my gaxis example) :

import sys,os

BASE = os.path.abspath(os.path.join(os.path.dirname(sys.argv[0]), ".."))
datadir = os.path.join(BASE, "share", "linuxcnc")
xmlname = os.path.join(datadir,"gaxis.glade")

change these lines to this:

builder.add_from_file(xmlname)

panel = gladevcp.makepins.GladePanel( halcomp, xmlname, builder, None)

note they use the variable xmlname rather then using the actual xml file name now.

the in your INI file change DISPLAY=axis to
DISPLAY=gaxis.py

That should do it

I also should mention that after you call makepins and after you make any extra HAL pins you want you should call
halcomp.ready() to let HAL know the pins are ready

the DRO will pan - try the unintuitive button 2 press both buttons at the same time then it should pan.
I think the shift key and button 1 will also make it pan.

You can turn the DRO off. I can't remember if you can make it smaller like in AXIS.
The capability is probably there but not brought out to glade controls.

Are you building this in the gscreen branch? gscreen has more options for gremlin and screen controls.

I looked at the source double clicking button 3 (which should be the right hand button) will clear the plot of previous moves.
There are methods in gremlin you can call directly to manipulate the screen controls for instance to use a touch screen - which doesn't work well with the standard controls.

For instance If you prefer to have a separate button to pan then connect a button signal to a method that:
calls gremlin.set_mouse_position(0,0)
and calls gremlin.pan(0,5)

this would pan 5 units in the positive Y axis

builder shouldn.t need to be global or self.builder unless you need it outside of the _ini_ call
It won't hurt to have it self.builder (that what is in gscreen but I am pretty sure it's unnecessary)