Hello all,
first thing : is it the right mailing list for tiny suggestions like this
one ? Please read on and tell me so I don't get it wrong. It is a usability
idea.
I often use proportional edit when modeling, however I sometimes use
connected and sometimes not, and I don't systematically
Someone should test if SDL stuff is still working. Maybe that variable
needs re-adding but only just before SDL initialization, and to be removed
after.
Also, as a workaround for previous versions you can do:
import os
del os.environ['SDL_VIDEODRIVER']
Or something like that.
--
DiThi
On 13-07-05 03:54 PM, Alberto Torres wrote:
Also, as a workaround for previous versions you can do:
import os
del os.environ['SDL_VIDEODRIVER']
Or something like that.
When I use this with 2.68 RC1, I get this error:
del self._data[key]
KeyError: b'SDL_VIDEODRIVER'
However the patch
The upcoming pie menu's should make the 3 way switch pretty easy. The
piemenus addon in contrib already has functionality for proportional
editing on the 'o' key.
The best place for suggestions like this is probably the bf-funboard
(Functionality Board) mailing list.
-Sean
On Fri, Jul 5, 2013
Here is a semi-dev related followup...
I figured it should be possible to cause a keypress to bring up the
context-menu to select a specific proportional editing mode. I tried to
replace the shift-o keybinding
to wm.context_cycle_enum(tool_settings.proportional_edit_falloff) to a
direct reference
On Sat, Jul 6, 2013 at 9:10 AM, David Jeske dav...@gmail.com wrote:
Here is a semi-dev related followup...
I figured it should be possible to cause a keypress to bring up the
context-menu to select a specific proportional editing mode. I tried to
replace the shift-o keybinding
to
import bpy
km = bpy.context.window_manager.keyconfigs.default.keymaps[3D View]
kmi = km.keymap_items.new(wm.context_cycle_enum, 'O', 'PRESS',
oskey=True)
kmi.properties.data_path = tool_settings.proportional_edit_falloff
When I do this, I get the same behavior as the current. It cycles
On Sat, Jul 6, 2013 at 12:44 PM, David Jeske dav...@gmail.com wrote:
import bpy
km = bpy.context.window_manager.keyconfigs.default.keymaps[3D View]
kmi = km.keymap_items.new(wm.context_cycle_enum, 'O', 'PRESS',
oskey=True)
kmi.properties.data_path = tool_settings.proportional_edit_falloff
Any particular reason there isn't an argument for adding custom tooltip
text when adding operators via Python with ?
UILayout.operator(operator, text=, text_ctxt=, translate=True,
icon='NONE', emboss=True)
I want to add tooltips to lines that look like this:
On Sat, Jul 6, 2013 at 1:49 PM, David Jeske dav...@gmail.com wrote:
Any particular reason there isn't an argument for adding custom tooltip
text when adding operators via Python with ?
Yep, storing data such as tool descriptions in the UI isn't good
practice, then the API docs miss them
After hashing it out with a few artists/users who LOVE the current spline
handle behavior, I think I have a patch which will make single spline
handle-set more predictable/understandable, while retaining 110% of current
functionality. (not a joke, I added functionality by fixing bugs)
This patch alters the window-editor-type-selection menu to a new 4-column
layout, based on the multi-column Modifier selection design.
The new design:
- keeps the primary editors very close to the menu-button in both
orientations
- makes it SUBSTANTIALLY easier to find and remember the locations
12 matches
Mail list logo
