<br><br><div><span class="gmail_quote">On 7/1/07, <b class="gmail_sendername">Levi Schooley</b> <<a href="mailto:levischooley@eaglecom.net">levischooley@eaglecom.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>3. Editmode bevel and offset tools - how do I procede with these<br>with the event refactor looming on the horizen? Does it need to be<br>a factor in my decision-making process? If so, to what extent?</blockquote><div>
<br>- snip -<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">1. "Permission" to create my own Transform()-like event loop for
<br>use with the editmode bevel tool. I may possibly need to do<br>something similar for the offset tool as well. To help justify<br>this action, I will point out that the edge-split/slide tool is<br>currently implemented using its own event loop.
<br></blockquote></div><br>Personally if you're thinking of the event refactor, I would avoid adding any new tight sub-loops. One of the targets of the events work is to remove these sorts of things from Blender, and have everything working via a central event loop.
<br><br>All these small loops scattered throughout Blender have got to go - they are duplicating effort and creating room for bugs since coders have to handle all input, redraws etc themselves, and they present several significant limitations - they are not very usable since they block all other input, which means that all interaction must take place with single undocumented key presses rather than being able to use all the different buttons and GUI controls that should be available at our disposal.
<br><br>cheers<br><br>Matt<br>