[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gEDA-dev: questions about lesstif menus




>        case 101:		/* named subnode */
> 
> Where the SomethingElse is what is a named subnode?  I didn't see
> any of that in pcb-menu.res since the only named subnodes I saw were
> "top level" ones like MainMenu.

001	{val val}
010	val
101	name = {val val}
110	name = val

I don't think we use 101 in practice, once we're inside the menu
layout.

> I see where "sensitive" is used and also "checked".  I wasn't able
> to see that "radio" had been used in pcb-menu.res.

I think that's dead code too.  I was going to use radio for radio
groups, but the flags worked more reliably.

> Around line 1352, I don't quite understand what note_widget_flag
> does.  Also, I didn't see active= used in pcb-menu.res, what is that
> supposed to do in this part of menu.c?

It keeps track of which widgets need to have their "checked" status
changed due to changes in the PCB status (like, loading a new board).

active= is supposed to be used for menu options that get greyed out
when they shouldn't be used, like trying to print an empty board.  I
just don't happen to like greyed-out menu buttons, because there's no
way to find out *why* they're greyed out.

> Is line 1394 reached?

Yeah, you can just put in a bare word and you get a useless button.
It comes in handy when you're building a new menu layout from scratch.

> What do you thing about using "tt=" for tooltips?  I'm not sure if
> we actually use any tooltips right now, but it is pretty clear where
> you'd stick this value if you found it in a menu resource file.

Can we call it "tip" or "tooltip"?


_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev