On Sun, Feb 19, 2012 at 7:00 AM, wrote:
> Date: Sat, 18 Feb 2012 15:34:25 -0500
> From: Dan Katz
> Yes of course. I think it's a bit easier with names because you can
> introspect
> on them in the python REPL using 'dir' and 'help' and such, but looking up the
> text of the shape module isn't
Since you understand your need and desire for documentation better than
anyone, perhaps you are the best one to add the explanation?
M
On Sat, Feb 18, 2012 at 3:34 PM, Dan Katz wrote:
>
> On Feb 17, 2012, at 3:43 PM, Hans Breuer wrote:
>
> > But I don't see why you could not use named constants
On Feb 17, 2012, at 3:43 PM, Hans Breuer wrote:
> But I don't see why you could not use named constants for the connection
> point index instead.
> The connection points are parsed in the order in the shape (see
> objects/custom/shape_info.c) and put into the connection point array in that
> o
At 17.02.2012 19:24, Ron Wilson wrote:
[...]
The check-in comment removing named CPs claimed lack of use in
the core objects and some memory savings as the rationale for deleting
them. My use case, though, involves custom objects rather than core
objects, and I'm not sure that the memory savings
At 16.02.2012 16:07, Dan Katz wrote:
Hi -
I'm doing a bunch of work on yet another Python diagram->code
generator plugin, and several times now I've found myself wishing that
connection points (and handles, to a lesser extent) had names that
were assignable in the Custom Shape Module shape files
On Fri, Feb 17, 2012 at 7:00 AM, wrote:
> Date: Thu, 16 Feb 2012 10:07:02 -0500
> From: Dan Katz
>
> A bit of context: I'm writing a Python plug-in for Dia which
> translates a data-flow diagram to code in a home-grown legacy
> job-control language. The plugin is exposed as an export filter (lik
