Joshua Leung da3802f559 Info Header: Non-blocking Info Messages ... Reports (i.e. 'info' or 'errors') are now shown in the info header in place of the scene statistics if the last executed operator had some, with this info disappearing again once another operator is run (to show scene statistics again). For example, this means that info such as the the number of verts merged, or whether a Keying Set successfully inserted keyframes, etc. is now shown again somewhere, and that this is done in a non-blocking manner. The current implementation is still a bit crude (i.e. lacking fancy polish), but is at least barebones functional. The todos... * When more than 1 report message is generated by the last operator, there is currently a display of the number of reports. In future, it would be nice to be able to add a button beside this or make the label clickable with appropriate text indicating this (commented out atm) to show popup menu of all the reports... * There could probably be some kind of coloured backdrop behind the text. Currently using standard box, but that has padding problems, and lacks visual interest. * Timer based fade out/disappear?		2010-03-02 11:48:40 +00:00
..
addons	replace operator options bl_undo and bl_register with bl_options	2010-03-01 00:03:51 +00:00
io	NetRender: Use threading mixin for master server. See if it solves latency issues that some people are having (always keep the stdout log from the master/client/slaves if you are reporting an issue).	2010-02-27 22:07:38 +00:00
modules	bugfix [#21405] Error on loading of thumbnails from network renderer [27204]	2010-03-01 12:44:28 +00:00
op	parts of the Python API are unstable, big discalmer in API docs main page, API Docs title and interactive console banner.	2010-03-01 10:34:54 +00:00
presets	scene.render_data -> scene.render	2010-02-23 12:48:35 +00:00
templates	make BGL and BLF modile names lowercase	2010-02-28 14:57:26 +00:00
ui	Info Header: Non-blocking Info Messages	2010-03-02 11:48:40 +00:00