[Bf-committers] Trusted blend files and scripted drivers bug and annoyance

Jace Priester jacepriester at threespaceimaging.com
Sun Aug 11 14:20:45 CEST 2013


Thank you!


On Sun, Aug 11, 2013 at 1:30 AM, Campbell Barton <ideasman42 at gmail.com>wrote:

> On Sun, Aug 11, 2013 at 5:08 PM, Jace Priester
> <jacepriester at threespaceimaging.com> wrote:
> > The specific issue I'm bringing up is the fact that the driver panel
> shows
> > that the expression evaluates to zero. In fact it does not, because
> > evaluation was skipped. If blender is going to ignore all of the very
> > necessary scripts in the blend files, there should at least be sufficient
> > notice instead of substituting a fake (zero) value without warning.
>
> Addressed this r59061,
> Now there is a warning message in the driver panel when scripted
> expressions are selected.
>
> >
> > On Sat, Aug 10, 2013 at 3:24 PM, Campbell Barton <ideasman42 at gmail.com
> >wrote:
> >
> >> On Sun, Aug 11, 2013 at 3:35 AM, Ton Roosendaal <ton at blender.org>
> wrote:
> >> > Hi,
> >> >
> >> > I understand the pain... apparently this header notice is not
> >> communicating, even when people already expressed disagreement and knew
> the
> >> feature was coming.
> >> >
> >> > However, you can set this all in user preferences to have things work
> >> forever as you want. It'swell documented in release logs:
> >> >
> >>
> http://wiki.blender.org/index.php/Doc:2.6/Manual/Extensions/Python/Security
> >> >
> >> > One idea we missed to investigate was to make the default (for
> previous
> >> saved startups) to mimic the old behaviour, so existing users wouldn't
> >> notice the change. The new trusted source feature then would only get
> >> activated on new installs or new userprefs after upgrading Blender.
> >>
> >> We didn't miss this, thats how it works currently and I suspect why we
> >> didn't get much feedback initially when the change was made.
> >>
> >> But as users do new installs without using their old userprefs, or
> >> reset factory-defaults, they run into this problem.
> >>
> >> > -Ton-
> >> >
> >> > --------------------------------------------------------
> >> > Ton Roosendaal  -  ton at blender.org   -   www.blender.org
> >> > Chairman Blender Foundation - Producer Blender Institute
> >> > Entrepotdok 57A  -  1018AD Amsterdam  -  The Netherlands
> >> >
> >> >
> >> >
> >> > On 9 Aug, 2013, at 22:30, Jace Priester wrote:
> >> >
> >> >> I expressed a lot of disagreement with the "Trusted" feature when
> there
> >> was
> >> >> talk about implementing it, and I'm here to voice a complaint again
> now
> >> >> that it has become a problem.
> >> >>
> >> >> I have created an animation using a scripted expression driver and
> that
> >> >> driver's value evaluates to zero. I did not notice the "Continue
> >> Untrusted"
> >> >> button appear at the top right. I've spent hours trying to figure out
> >> why
> >> >> scripted drivers don't work, only to save and reload and then be
> >> prompted
> >> >> to "Reload Trusted". This has been a gigantic waste of my time and is
> >> >> precisely the reason I did not want this "trusted" junk in the first
> >> place.
> >> >>
> >> >> I am aware of the command line options to disable it, but I never
> >> expected
> >> >> to have to do that. I understand the "Reload Trusted" prompt when
> >> opening a
> >> >> file. However, when I create a brand new driver and enter the
> expression
> >> >> myself it should work immediately. In any case, it damn sure should
> not
> >> >> show a value of zero without a notice right next to it that it
> skipped
> >> >> evaluation entirely. As-is, this is very misleading and indicates
> that
> >> the
> >> >> expression did in fact resolve to a value of zero.
> >> >> --
> >> >>
> >> >>
> >> >>
> >>
> --------------------------------------------------------------------------
> >> >> Jace Priester
> >> >> Threespace Imaging
> >> >> jacepriester at threespaceimaging.com
> >> >> 559-284-0904
> >> >>
> >>
> --------------------------------------------------------------------------
> >> >> _______________________________________________
> >> >> Bf-committers mailing list
> >> >> Bf-committers at blender.org
> >> >> http://lists.blender.org/mailman/listinfo/bf-committers
> >> >
> >> > _______________________________________________
> >> > Bf-committers mailing list
> >> > Bf-committers at blender.org
> >> > http://lists.blender.org/mailman/listinfo/bf-committers
> >>
> >>
> >>
> >> --
> >> - Campbell
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> http://lists.blender.org/mailman/listinfo/bf-committers
> >>
> >
> >
> >
> > --
> >
> >
> >
> --------------------------------------------------------------------------
> > Jace Priester
> > Threespace Imaging
> > jacepriester at threespaceimaging.com
> > 559-284-0904
> >
> --------------------------------------------------------------------------
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
>
>
>
> --
> - Campbell
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 


--------------------------------------------------------------------------
Jace Priester
Threespace Imaging
jacepriester at threespaceimaging.com
559-284-0904
--------------------------------------------------------------------------


More information about the Bf-committers mailing list