gEDA-dev: PCB patch for "SetChangedFlag" action, work on project manager

[Peter Clifton]

On Fri, 2006-08-25 at 07:48 -0400, DJ Delorie wrote:
> Can you have it take a parameter, to set it to true *or* false?  It's
> ok to default to true, but we should allow both settings somehow.

Had thought this might be necessary for CVS inclusion, I just wanted to
see I it was along the right lines.

I'm leaning away from the action name "ChangeChangedFlag", which would
be implied if we look at the parametrised alteration of other flags in
PCB.

Perhaps modeling on the "SetFlag" and "ClrFlag" actions, and implement
both "SetChangedFlag" and "ClrChangedFlag"?

For our purpose, we only need to set the flag, but I guess someone might
find a use for clearing it.


What is the convention for getting information _out_ of PCB? Please
excuse my laziness for not reading the code closer, but are there any
functions which return data to stdout? e.g. "GetChangedFlag"...? I see
stuff returned to the message window at various points.

Any thoughts on our proposed gschem2pcb usage whilst PCB is open? Any
ideas how to offer the user new components to paste in where they wish,
without trampling their paste buffer contents?

Many thanks,

Peter Clifton.