[Bf-committers] Blender 2.57 Release AHOY! (1)

[Dalai Felinto]

Hi Campbell,

here (on windows 64) the message shows as a warning popup actually
(before your commit/fix) http://www.pasteall.org/pic/show.php?id=10969

So imho it's really annoying/misleading (thinking in the mainstream
user that used to work in 2.49 and is finally migrating to 2.5).

--
Dalai

2011/4/12 Campbell Barton <ideasman42 at gmail.com>:
> Both my fault too!
> - Error report on engine load only shows in the info view, so no
> popups which complain to the user, infact the message should show in
> the info header but because its done on file load it doesn't, I marked
> it as a TODO in the code, so we have a nice case of a bug hiding a
> bug.
> IMHO its bad but not a showstopper (fixed in svn).
>
> - Not loading bookmarks & recent file list is stupid, currently this
> is only done on load.
>  This bug existed before the "Copy Previous Settings" operator was
> added it just that moving blenders configuration wasn't something
> users ended up doing much.
>  My main aim was go get the files copied to the right locations &
> correctly check if copying was needed on all OS's & configurations,
> (self contained, system wide install etc).
>
> Calling WM_read_history() on file new looks like it should work.
> The bookmarks are not so simple since its called from ED_file_init
> which initializes file sel icons & thumbnail dir, of coure splitting
> it off into a function isn't hard, but I rather not do this as a last
> minute fix.
>
> For a quick solution on this it could just have a popup that says
> "restart blender for new settings".
> The drawback with this is it leaves blender splash with the "Copy
> Settings" button still there, as if nothing happened, the splash wont
> redraw without the button because of how its setup (draw call only
> runs once), the copy settings operator has no way to exit the splash
> or force a re-initialization - unless we add some api calls or
> operators to do so...
>
> ...so maybe users can just put up with this one time annoyances?, we
> probably get a huge number of more important reports so since this is
> only a glitch and doesn't stop the button being useful I'm inclined to
> just go ahead with the release.
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>