[Bf-funboard] thoughts for game engine improvements

Campbell Barton cbarton at metavr.com
Wed Dec 20 11:27:16 CET 2006


Quit.blend is not that good for a few reasons other then the ones alredy 
suggested.
* dosnt seem to work with editmode changes (I just tested and a new 
quit.blend dosnt include changes made in editmode)
* If you load directly from /tmp/quit.blend and save to the new DIR its 
possible to loose objects linked from relatively linked libs such as.. 
//lib/mylib.blend - objects referencing this will be lost.

* other relative linked files will also not load though its not that bad 
since they will appier when the blend is put back in the right place 
unlike libs.

Sometimes it takes a noticeable amount of time to save quit.blend - not 
much can be done about that..

Id prefer a quit menu that defaulted to no and not allow closing 
directly from the window decorations.

Doug Ollivier wrote:
> Yep this is one of the most important improvements blender could 
> get.... and anyone who says but it has "quit.blend" should consider 
> the following, and also consider many people are either not as 
> patient, experienced or intelligent as you.
>
> 1) Temp directory on windows doesn't work by default. and blender does 
> not "warn" that the temp directory will fail. (and nobody whos new to 
> blender knows where the settings can be found)
>
> 2) Quit.blend is highly likely to be overwritten by someone who 
> doesn't know it exists.
>
> 3) Blender has no "auto recovery" feature at all, so the user is even 
> less likely to realise its there.
>
> However interestingly enough, blenders file versioning system is 
> better than any software i have ever used (blend1 - blend32, all 
> automatically done is fantastic)
>
> possible solutions to the problem/frustration include,
> a) Adding a save on quit dialogue. b) Offering quit.blend1 through 
> quit.blend5 by default (to avoid accidentally wiping over)
> c) showing a warning on open, that the tmp path is not working. (so 
> its not found out "after the fact"
>
> All solutions would have a beneficial effect on blender
>
> This stuff is all included in my Blendergo "random things" document 
> which i will be posting shortly, it includes many common frustrations, 
> as have been pointed out by real users. and tries to offer multiple 
> solutions for each.  It would be sad to have all this stuff ignored.  
> Is there some kind of "ergonomics" bug reporting system.  currently we 
> have standards for code, but none for usability.
>
> Doug Ollivier (Alltaken)
>
> Nathan Letwory wrote:
>> Carsten Wartmann wrote:
>>> Roger Pack schrieb:
>>>
>>>> 2) It would be nice if Blender "asked" on exit, if you want to save 
>>>> the .blend file.
>>>
>>> It saves a quit.blend ;-)
>>
>> This is true only if /tmp exists. On a Windows machine it often fails 
>> to write to tmp, since it is non-existant. Also, the default /tmp 
>> needs to be accessible (normally is, but I have seen cases where it 
>> is not accessible for all users...)
>>
>> /Nathan
>>
>> _______________________________________________
>> Bf-funboard mailing list
>> Bf-funboard at projects.blender.org
>> http://projects.blender.org/mailman/listinfo/bf-funboard
>
> _______________________________________________
> Bf-funboard mailing list
> Bf-funboard at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-funboard
>


-- 
Campbell J Barton

133 Hope Street
Geelong West, Victoria 3218 Australia

URL:    http://www.metavr.com
e-mail: cbarton at metavr.com
phone: AU (03) 5229 0241



More information about the Bf-funboard mailing list