[Bf-committers] Menu bar riffing behaviour (open subsequent menus on hover)

2014-06-09 Thread Matthew Reid
Hi all I'd like to contribute my first piece of functionality for blender. I've changed the menu bar behaviour to open the first menu on click, and subsequent menus on hover. This is also known as menu riffing, and matches the default menu behaviour of Windows and OSX applications. Here's a

Re: [Bf-committers] Menu bar riffing behaviour (open subsequent menus on hover)

2014-06-09 Thread Paweł Łyczkowski
This has my support. I don't see how this could be intrusive in any way though, so no need to make it configurable. Regards PLyczkowski Matthew Reid mailto:matthewrei...@gmail.com 10 czerwca 2014 01:13 Hi all I'd like to contribute my first piece of functionality for blender. I've

Re: [Bf-committers] Menu bar riffing behaviour (open subsequent menus on hover)

2014-06-09 Thread Campbell Barton
Seems useful, agree no need to make it an option. This is what submenu's do already. Can you upload a patch to: https://developer.blender.org/differential On Tue, Jun 10, 2014 at 9:28 AM, Paweł Łyczkowski pawellyczkow...@gmail.com wrote: This has my support. I don't see how this could be

[Bf-committers] Python API for updated data and other questions

2014-06-09 Thread Angus Hollands
Hi all, I'd like to keep this short, because it's early in the morning, and I need to sleep, but there are a couple of questions I have regarding the Python API. We currently have is_updated as a means for testing if data has been changed since we last rendered it. I am working/ discussing with

Re: [Bf-committers] BGE developer meeting

2014-06-09 Thread brita
The meeting went through and quite some people showed up to weight in their opinions. Thank you all, it is good too see the interest on the project. Here is the summary of the meeting, the wiki will be updated accordingly: We reviewed the planning presented on the roadmap

[Bf-committers] More wiki tweaks...

2014-06-09 Thread Dan McGrath
Hi, Yet again the wiki went down today, this time with a 500 which appeared to be a result of a the single backend of fast-cgi dying (a test we tried a few days ago in case of thread issues). This time I tried to increase the backend count back to something a little higher with a quicker turn