[Bf-committers] Temporary "global" storage

Jorge Rodriguez jorge at lunarworkshop.com
Fri Jun 22 01:07:23 CEST 2012


You'

On Thu, Jun 21, 2012 at 3:57 PM, Dan Eicher <dan at trollwerks.org> wrote:

> On Thu, Jun 21, 2012 at 3:00 PM, Jorge Rodriguez
> <jorge at lunarworkshop.com> wrote:
> > This would be perfect but I can't find a place to use it that's not part
> of
> > an operator. There's no single operator responsible for handling these
> > functions. I'm not able to find any way to attach a SKIP_SAVE property
> to,
> > for example, wmWindowManager or wmWindow. I'd rather avoid resorting to a
> > static variable in a function. Maybe there's some way to do it with rna
> > that I'm not seeing?
>
> If these variables aren't of interest to people in general it's
> overkill to wrap them in rna and (automagically) expose them in the
> py-api. Why would anyone care when the last time a tooltip was closed
> or what the last highlighted button was when writing a script?
>
> Dan
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
Jorge "Vino" Rodriguez
jorge at lunarworkshop.com
[ Tweet <http://twitter.com/vinobs> | Like <http://www.facebook.com/bsvino>|
Plus <http://www.google.com/profiles/bs.vino> ]
919.757.3066


More information about the Bf-committers mailing list