Yes, under the hood it creates nodes with hscripts-expressions and vex snippets. Also it can delete history and many other features not included to video.

Some feature list:

0. RMB - hotbox-like widget with modeling tools

1. in ‘select’ state (mode):
1.1 LMB - laser selection
1.2 MMB - box\lasso selection
1.4 MMB (fast click) - elect loop - doesn`t need of ‘A’ hotkey
…

in ‘edit’ mode:
1.5 Alt - multi-snapping
1.6 RMB - fast grabbing pivot (hello xsi-users). Key release will fix pivot back. with alt it multi-snapping to anything
…

2. Wheel:
2.1 Up - select polygons
2.2 Down - select poly-islands. Fast wheel roling (Down+Up) will select island under the mouse
2.3 Ctrl+Up - select verites
2.4 Ctrl+Down - select edges
2.5 Shift+Up - Move
2.6 Shift+Down - Rotate\Scale
2.7 Ctrl+Alt+Up - Redo
2.8 Ctrl+Alt+Down - Undo
2.9 Ctrl+Shift+Up - Shrink seletion
2.10 Ctrl+Shift+Down - Grow seletion

—

All this works (in most cases) with simple but advanced selection behaviour. For example (like in Silo) it doesn`t need component selected, but maybe pre-hilighted (under mouse) when nothing was selected.

All hotkeys, mouse behaviour, ui-style and hotbox items are very custimizable in simple python code pieces.

Doesn`t showed snapping and align features in this video. Coming soon…

—

PS No standard hotkeys was used when recording video, only mouse+modifiers

Some PySide fast modeling very-customizable tool system.
Preview of very simple (but not very last) features.
http://youtu.be/IsSWh4Bw6LM [youtu.be]

Or maybe hscript? :cry:

Is it possible to get\set current manipulator ('edit' state for example) position\orientation from python\hscript\hdk

Is it possible to setup multisnapping (for example set snap to midpoints) from python or HDK?

It think the best is LC_ALL=en_US.UTF-8
in houdini.env

o shit, i`m stupid idiot.
Thanx edward you saved me

It is very interesting that i asked questions (without answers) like this not once , and I never noticed highlight flag

Good question. This is old problem

I use this trick in my interactive tools.

For example, after my tool finish i want to highlight components to use it in next tool if need.

It is very good if main node of my tool is created by soptoolutils.genericTool. In this case components automatically selected (highlighted)

But, if node created manually (with hou.Node.createNode()) it can`t highlight components, except ‘group’ node

So, my temporary solution is creating ‘group’ node after main node and highlight components with hou.SceneViewer.enterCurrentNodeState() Works well, but IMO this is not good

Yes it is good addition. But I still need press ENTER to accept selection
I didn't notice this behaviour yesterday.

So it is not so good for automatization tricks in my scripts

No !!!
H14 has NEW initial geometry arguments in hou.SceneViewer.selectGeometry method

:twisted: :twisted: :twisted:

I find H14 solution !!!

def select_geometry( mask='0', geometry_type=hou.geometryType.Primitives ):
viewer = toolutils.sceneViewer()
if viewer is not None:
viewer.selectGeometry(use_existing_selection=False, initial_selection_type=geometry_type, initial_selection=mask)

Can reproduce this BUG if eventFilter class described in Shelf Tool Script section.
Works normally if i described class in external python script, for example, in file

I have bad news. In my case, linux x64 and any of H14 builds, i can`t get my custom eventFilter to work allways.

Bug submitted…


EDIT:

I saw that this BUG reproduces when i want to catch QtCore.QEvent.KeyRelease, but not with QtCore.QEvent.KeyPress

EDIT1:
I continue to consider this problem. The problem is with key events only.
It doesn`t works allways. But, for example, with QtCore.QEvent.MouseButtonPress it works well. And it doesn't matter if i installed filter to specific widget or to QApplication instance…

Also at now i can install eventFilter to viewport widget in my tools.
But it would be good if we can catch Enter\Leave and HoverEnter\Leave events, because its good way to identify that we left out viewport widget.

Good fixes! I dont know how long we have to wait its form AutoD*** )))

I consider that we still need ability to find main widget from python.

I remind that at now i get it from top level widgets and test it by windowIconText() function. If it contains something then it is MainWidget
Not so elegant but it works

Anyway you give us good Qt implementation and in some cases it more robust than in Maya !!!

Thanx !!!

Thanx!

QApplication instance should be safe in both PySide and C++ code

QtGui.QApplication.instance().styleSheet() retrurn empty string

QT_Utils::applyWidgetStyleSheets(QWidget*)

Can`t find this method

What the best way to get styleSheet text?
At now i get it from one of QApplication top level widgets…

Thanx. I mean single RED component under mouse, that highlighten without starting selection.
I dont need BLUE components during mouse drag