VCB and Shortcut Keys

thomthom

I thought enableVCB? was supposed to force SketchUp to listen to the VCB when onReturn is fired, and not the keystroke when depressed.

Unfortunately it doesn't. There are some keys that is accepted, provided it's not the first key to be pressed. But they appear to be hard coded into SketchUp to fit the needs of the native tools.

TIG

The excepted characters that are OK after a number are:
",',m,mm,cm,s,x,/,*,[,],<,> etc
Can you use some of those in your custom inputs...

Chiefwoodworker

@tig said:

The excepted characters that are OK after a number are:
",',m,mm,cm,s,x,/,*,[,],<,> etc
Can you use some of those in your custom inputs...

Unfortunately I don't think s works either; it invokes the Scale tool. The larger problem is that enableVCB? appears to have no effect on the VCB. You can leave this method out altogether and the VCB works the same way, i.e. the default false is not the case. In fact, I have confirmed that SketchUp does not call enableVCB? on any keystroke, including Enter. However, it does call enableVCB? on left mouse button. Go figure!

thomthom

Without enableVCB? you cannot make VCB input...

And I've made use of s in VCB input - but it cannot be the first character to be typed.

Chiefwoodworker

@thomthom said:

Without enableVCB? you cannot make VCB input...

And I've made use of s in VCB input - but it cannot be the first character to be typed.

I am using SketchUp 2013 Pro Windows version. I can comment enableVCB? out and still enter data through the VCB. However, if I enter 5s it invokes the Scale tool. I haven't tried Make or version 8.

TIG

@chiefwoodworker said:

@thomthom said:

Without enableVCB? you cannot make VCB input...

And I've made use of s in VCB input - but it cannot be the first character to be typed.

I am using SketchUp 2013 Pro Windows version. I can comment enableVCB? out and still enter data through the VCB. However, if I enter 5s it invokes the Scale tool. I haven't tried Make or version 8.
In my 2d tools the user can type say 12s to change the segmentation of arcs/circles etc just like the native-tools, typing 12s+<enter> does NOT invoke the Scale tool in v8 OR v2013...
I have just retested it to make sure.
Perhaps there is something adrift in the way you are making your 'Tool' ?
Do you have it setup and made as a tool-command as required ?

thomthom

@chiefwoodworker said:

I am using SketchUp 2013 Pro Windows version. I can comment enableVCB? out and still enter data through the VCB.

I cannot reproduce this...


class MyTool; end;
Sketchup.active_model.select_tool( MyTool.new )

Any chance you've already loaded the code with enableVCB? ? Because then commenting out will not remove it if you reload the file.

Chiefwoodworker

@thomthom said:

I cannot reproduce this...


> class MyTool; end;
> Sketchup.active_model.select_tool( MyTool.new )
>

Any chance you've already loaded the code with enableVCB? ? Because then commenting out will not remove it if you reload the file.

Here is the sequence on my Windows PC.

Comment out the enableVCB? method.
Open SketchUp.
Open my model.
Select my tool.
Pick first point.
Type a number into the VCB with no characters.
Press Enter and the number is interpreted as a length by my conversion code.

I can repeat this sequence with only steps 6 and 7 changed.
6. Type a number followed by t, no space, and the Tape Measure tool come up.
7. Never get to step 7.

If I repeat the sequence using s in step 6. instead of t I get a system beep indicating the input can't be parsed (I don't have the code in there to parse an s).

Now I repeat these same three tests with the enableVCB? method coded to return true. Note I completely close SketchUp, make the code change and Re-Open SketchUp. I Don't use reload.

I get exactly the same results as with no enableVCB? method. Further, as I mentioned earlier, if I code the enableVCB? method as follows:

def enableVCB? UI.beep return true end

I never get a beep on any keystroke. But I do with left mouse button presses (and I believe left mouse button up as well). There is a bug here someplace but I am not sure how it should work. I know how I would like it to work, but that is probably not interesting to the SketchUp team.

p.s. I get the same behavior on SketchUp Pro 8.
p.p.s. I have a friend who wrote a tool script and never knew about enableVCB? method, hence never implemented it. His tool worked as long as what he typed into the VCB was numbers and no characters. If confirmed for me that he gets the same results I do when he uses a shortcut key. He then implemented the enableVCB? method to return true and also got the same results.

thomthom

I'm puzzled that you can get a tool to accept VCB input if enableVCB? is not implemented... did you try my bare bone example?
What Windows version do you have?

And I don't think that enableVCB? is meant to be called on each key stroke.

Chiefwoodworker

@thomthom said:

I'm puzzled that you can get a tool to accept VCB input if enableVCB? is not implemented... did you try my bare bone example?

I modified your example as follows:

class MyTool def onUserText(text, view) begin value = text.to_l #just to do something rescue # Error parsing the text UI.beep puts "Cannot convert #{text} to a Length" value = nil Sketchup::set_status_text "", SB_VCB_VALUE end return if !value UI.messagebox(text) end end; Sketchup.active_model.select_tool( MyTool.new )

I typed 36 into the VCB and hit Enter. Resulting output is shown in image at bottom.

@thomthom said:

What Windows version do you have?

Windows 8 64 bit.

@thomthom said:

And I don't think that enableVCB? is meant to be called on each key stroke.

Well, if it is supposed to allow and check for accepted characters besides numerals I would think it would have to. But it should at least be called on Enter and it isn't.

Chiefwoodworker

@tig said:

The excepted characters that are OK after a number are:
",',m,mm,cm,s,x,/,*,[,],<,> etc
Can you use some of those in your custom inputs...

TIG,

Where in the documentation did you find this list of accepted characters after a numeral? I haven't been able to locate it.

TIG

It doesn't exist...
Just made it up - from what I know works...

thomthom

That's interesting. Just making use of onUserText will enable the VCB - making enableVCB? redundant. (Though this might need testing on all versions - in case this is something that has changed.)
I don't see the point of enableVCB? if onUserText automatically enables it...

@chiefwoodworker said:

Well, if it is supposed to allow and check for accepted characters besides numerals I would think it would have to. But it should at least be called on Enter and it isn't.

It's only a simple property to enable or disable the VCB.
The docs only says:

The enableVCB? method is used to tell SketchUp whether to allow the user to enter text into the VCB (value control box, aka the "measurements" panel). If you do not implement this method, then the vcb is disabled by default.

So it doesn't affect what types of characters you can input - it just enables/disables the control as a whole.

But I agree that there should be a way to prevent keyboard shortcuts from triggering.

Chiefwoodworker

@tig said:

It doesn't exist...
Just made it up - from what I know works...

I like your style

Chiefwoodworker

@thomthom said:

It's only a simple property to enable or disable the VCB.
The docs only says:

The enableVCB? method is used to tell SketchUp whether to allow the user to enter text into the VCB (value control box, aka the "measurements" panel). If you do not implement this method, then the vcb is disabled by default.

So it doesn't affect what types of characters you can input - it just enables/disables the control as a whole.

I don't think it is the onUserText that is enabling the VCB. I think the default is true, not false. Try this script:

class MyTool def enableVCB? UI.beep end end; Sketchup.active_model.select_tool( MyTool.new )

Depress and release the left mouse button slowly. You will see that enableVCB? is called on both the down and up of the left mouse button. That's why I think it is intended to sample each key stroke, to see if a shortcut key was preceded by a number, in which case it would be interpreted as a parameter of the number and not a shortcut key. But it doesn't get called at all with a key stroke, including the Enter key, which I think is the bug. Why is it called with a mouse action? That's what's curious to me.

thomthom

I asked the SketchUp team, and they confirmed that onUserText enables the VCB - and enableVCB? is there to let you disable the VCB when you do not want user input. (For instance - if your tool uses the VCB to adjust values then you don't want the VCB to be enabled until you have performed an action.)

And enableVCB? is queried on certain event which one can assume the tool changes state - such as on mouse clicks.

thomthom

I looked further at the behaviour of the Tool class - using variations of this snippet to inspect the behaviour:

<span class="syntaxdefault"><br />class ToolTest6<br /><br />  </span><span class="syntaxkeyword">%</span><span class="syntaxdefault">w</span><span class="syntaxkeyword">{<br /></span><span class="syntaxdefault">    activate<br />    deactivate<br />    Xdraw<br />    enableVCB</span><span class="syntaxkeyword">?<br /></span><span class="syntaxdefault">    getExtents<br />    getInstructorContentDirectory<br />    getMenu<br />    onCancel<br />    onKeyDown<br />    onKeyUp<br />    onLButtonDoubleClick<br />    onLButtonDown<br />    onLButtonUp<br />    onMButtonDoubleClick<br />    onMButtonDown<br />    onMButtonUp<br />    onMouseEnter<br />    onMouseLeave<br />    XonMouseMove<br />    onRButtonDoubleClick<br />    onRButtonDown<br />    onRButtonUp<br />    onReturn<br />    XonSetCursor<br />    onUserText<br />    resume<br />    suspend<br />  </span><span class="syntaxkeyword">}.</span><span class="syntaxdefault">each </span><span class="syntaxkeyword">{</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">|</span><span class="syntaxdefault">event_name</span><span class="syntaxkeyword">|<br /></span><span class="syntaxdefault">    define_method</span><span class="syntaxkeyword">(</span><span class="syntaxdefault"> event_name </span><span class="syntaxkeyword">)</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">{</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">|*</span><span class="syntaxdefault">args</span><span class="syntaxkeyword">|<br /></span><span class="syntaxdefault">      puts event_name<br />      true<br />    </span><span class="syntaxkeyword">}<br /></span><span class="syntaxdefault">  </span><span class="syntaxkeyword">}<br /><br /></span><span class="syntaxdefault">  </span><span class="syntaxkeyword">%</span><span class="syntaxdefault">w</span><span class="syntaxkeyword">{<br /></span><span class="syntaxdefault">    onKeyDown<br />    onKeyUp<br />  </span><span class="syntaxkeyword">}.</span><span class="syntaxdefault">each </span><span class="syntaxkeyword">{</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">|</span><span class="syntaxdefault">event_name</span><span class="syntaxkeyword">|<br /></span><span class="syntaxdefault">    define_method</span><span class="syntaxkeyword">(</span><span class="syntaxdefault"> event_name </span><span class="syntaxkeyword">)</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">{</span><span class="syntaxdefault"> </span><span class="syntaxkeyword">|*</span><span class="syntaxdefault">args</span><span class="syntaxkeyword">|<br /></span><span class="syntaxdefault">      puts event_name<br />      false<br />    </span><span class="syntaxkeyword">}<br /></span><span class="syntaxdefault">  </span><span class="syntaxkeyword">}<br /><br /></span><span class="syntaxdefault">end </span><span class="syntaxcomment"># class<br /><br /></span><span class="syntaxdefault">Sketchup</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">active_model</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">select_tool</span><span class="syntaxkeyword">(</span><span class="syntaxdefault"> ToolTest6</span><span class="syntaxkeyword">.</span><span class="syntaxdefault">new </span><span class="syntaxkeyword">)<br /></span><span class="syntaxdefault"> </span>

Not the X in front of some names - I used that to quickly prevent some events from flooding the console.

Here's a quick summary of which event triggered which was followed by enableVCB?:

` activate
enableVCB?

onMouseEnter

onMouseLeave

onLButtonDown
enableVCB?

onLButtonUp
enableVCB?

onLButtonDoubleClick
enableVCB?

onMButtonDown

onMButtonUp

onRButtonDown
enableVCB?

onRButtonUp

onRButtonDoubleClick

onKeyDown

onKeyUp

onUserText

onReturn
enableVCB?`

The event's that responded with enableVCB? query:
activate onLButtonDown onLButtonUp onLButtonDoubleClick onRButtonDown onReturn

Other observations:
If onKeyDown or onKeyUp return true then no text is entered into the VCB. It appear to block it.

When the VCB is enabled: Space, S, M, K etc didn't trigger it's shortcuts - but only if I had typed a number first.

If the VCB is enabled, and you enter some input to the VCB then first onUserText will trigger the first time you hit Return - then on the second you hit Return onReturn will trigger.

If the VCB is disabled then onReturn will trigger every time you hit Return.

Chiefwoodworker

@thomthom said:

I asked the SketchUp team, and they confirmed that onUserText enables the VCB - and enableVCB? is there to let you disable the VCB when you do not want user input. (For instance - if your tool uses the VCB to adjust values then you don't want the VCB to be enabled until you have performed an action.)

And enableVCB? is queried on certain event which one can assume the tool changes state - such as on mouse clicks.

thomthom,

Thanks very much for the help on this and clearing things up. The documentation on this is really poor and misleading. I still wish we had a way to disable shortcut keys like the native tools have.

Thanks again.

Chiefwoodworker

@thomthom said:

I looked further at the behaviour of the Tool class - using variations of this snippet to inspect the behaviour:

thomthom,

Your help is well above and beyond anything I could ask for. Thanks again. I am loading the snippet to complete the "etc" and see if there are keys I can use.

driven

Hi Joe,
your script partially works on mac with to_f added @ line 4.
jumps out of tool if you hit a q t o p a f h l
a lot of Capitals work as well, e.g LBWH all work, as a block or on their own...


value = text.to_f.to_l #<<ADDED  TO FLOAT

john