> Note that while playing around with this method just now, I found two > separate bugs, one of them a nuisance (changes the cycle after > parameterizing the point, without warping the cursor to that point), > and the other fatal (seems to be in version 3.7 only). There is also > a handful of annoying "features" related to the ability to modify the > library master object (and therefore all instances) at the same time > you're trying to change the parameterized point of a single instance > (for example, you parameterize the X-position only of a point; then > if you move that point in both X and Y, the change in X applies only > to that instance, but the change in Y applies to every instance). As > I mentioned before, I need to implement a "lock-out" flag that one can > set to prevent editing anything other than the parameterized parts of > an element. This seems easier said than done, though.
That should be easy to do once I'm done with revamping the parameter system. As soon as you get a new release done, I'll merge your changes with my codebase. >> Is it OK to call pwriteback(areawin->topinstance) willy-nilly? Perhaps >> simply putting it at the end of each and every event handler is a >> temporary workaround? > > I can't think of any reason this shouldn't work, but then again, that's > what I always say just before I break my program. I'd call it "brute > force" rather than "willy-nilly". OK, I'll give it a try. So far I've put in the assert and got rid of all drawing code that was in action outside of the repaint event. There will be other simplifications that may also follow from that. As for the color-via-paremeters, I presume that we would need a way of specifying global default parameters? Such that the default color can be propagated down the tree. Thanks, Kuba _______________________________________________ Xcircuit-dev mailing list [email protected] http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
