LinuxCNC Features - a kind of NGCGUI

FernV wrote:

Hi,

As you can see, there are more headers and sub-headers and I hope it makes it more usable. However, I do not know how difficult it is with a touch screen to expand/collapse rows. Please tell me about your experience and what you think about it.
Fern

FernV wrote:

Hi,
Add dialog does not exist anymore and IconView is integrated in the window and shows when Add button is clicked. A single click is required. Also please note the size of icons and height of rows to make it easier with a touch screen. Please comment.
Fern

FernV wrote:

Hi,
A Virtual Keyboard appears when editing data type int and float. Not available in widget box. Simply set 'use_numeric_vkb = True' in the beginning of features.py. Again I would like your comment and if I should do more
Fern

def to_gcode(self, *arg) :
        def recursive(itr) :
            gcode_def = ""
            gcode = ""
            f = self.treestore.get(itr, 0)[0]
            if f.__class__ == Feature :
                gcode_def += f.get_definitions()
                gcode += f.process(f.attr["before"])
                gcode += f.process(f.attr["call"])
		try: 				
		 comm = f.process(f.attr["command"])
		 if comm != "":
		    rc = subprocess.check_output(os.path.abspath('.').strip() + comm.strip(), shell=True)
		    if "(bash_return_string)" in gcode :
		      gcode = string.replace(gcode, "(bash_return_string)", rc)
		except Exception:
		 pass

fixer wrote:

FernV wrote:

As you can see, there are more headers and sub-headers and I hope it makes it more usable. However, I do not know how difficult it is with a touch screen to expand/collapse rows. Please tell me about your experience and what you think about it.
Fern

I think, with split side by side view, there is plenty of space to have all parameters shown. Also requires less clicking. You have those sub headers declared in ini files, right? Leave it there, I am sure it will come handy, but with those basic subroutines with small set of params I would not use them.

fixer wrote:

When do you think you will publish it?

fixer wrote:

I still have some ideas to do in engraving feature (text on arc), but wont be able to finish it before next weekend. if ypu want to include it in your version, of course.
I did something with that if statement, it works better, but can still be done even better. Do take a look at it:

def to_gcode(self, *arg) :
        def recursive(itr) :
            gcode_def = ""
            gcode = ""
            f = self.treestore.get(itr, 0)[0]
            if f.__class__ == Feature :
                gcode_def += f.get_definitions()
                gcode += f.process(f.attr["before"])
                gcode += f.process(f.attr["call"])
		try: 				
		 comm = f.process(f.attr["command"])
		 if comm != "":
		    rc = subprocess.check_output(os.path.abspath('.').strip() + comm.strip(), shell=True)
		    if "(bash_return_string)" in gcode :
		      gcode = string.replace(gcode, "(bash_return_string)", rc)
		except Exception:
		 pass