reason: mixbuffer size was not correctly initialized in .blend. Doing this
for struct UserData has some extra quirks, so better not do it with
checking for version (if version<2.27 etc) but always (if U.mix==0 etc).
I mail this to committers list as well.
- fixed error introduced by coding color for panel, instead of just
implementing the right default color. this caused colors not possible
below value '100'... tsk tsk
standard starts with 0.5 sec. Turn the threshold value up to effectively
disable it when you dislike it. But give it a try!
- added 'Home' after splitting window for buttonswindow
ENORMOUS job Matt has done with the menus! :)
- followed as much as possible order and options in pulldowns, but since
toolbox has more categories, it is split up sometimes.
- did some minor changes in pulldowns to make it more consistant
- not yet: armature & text options...
- not yet: toolbox in other window types
(warning; shift+a now is new... eek!)
Armature, Camera, Lattice
- this enables browsing data again. All in F9 menu (editing)
- fixed 'home' in buttonswindow, mixed up 1 and 0 again! :)
(it scaled in the wrong direction...)
- errors in names/hotkeys pulldowns fixed
- full window option in pulldown win caused ortho on/off event
- weight paint now shows vertex color Panel in editbuttons
- adding armature while vpaint mode, didnt end vpaint mode
- cleaned up some buttons design
- leftmouse press-hold for toolbox also moved 3d cursor
- nkey menu for buttonswindow (hex values) couldnt be restored yet, is
for next release
- replaced Nkey in IpoWindow with Panel, this now displays the buttons
that were formerly in 'anim buttons' as well; to view the boundbox
values of all visible curves, and adjust it.
- the new panel also has the 'set speed' option, fixed stuff in it and
added better errorwarning... still not a very well coded tool!
correctly for deciding whether its pressed or not
- added 'add new' buttons to material & texture menus
is done by std_lib buttons in headerbuttons.c, now only for this.
doing it for ipowindow, sound, etc. has some weird consequences, save
that for later
- verified usage of 'setting2' color for databuttons only
- problem was in limiting the abuse of frontbuffer drawing as happended
a lot in 2.28 and older. the less the better...
- bug was not registering a curarea->win_swap=FRONT_OK, to indicate there
was only drawn in frontbuffer
- cleaned up calls further, and made sure it doesnt draw 1 vertex too many!
also means it works better with selecting in solid drawmode now, check!
