Shift<Key>3 bindkey not working

This is one of the reasons for the new bindkey editor in IC615. When you add a new bindkey (or edit an existing one), rather than having to figure out the (sometimes) cryptic names for the key, you simply press the key or key combination on the keyboard, and it will enter the encoding for you.

So that way you shouldn't need to scream.

Regards,

Andrew.

Hi there,

Many years after that post I still have this issue. Originally - back in 2012 - I thought that was the issue with the German keyboard layout I was using as on SHIFT+3 was asigned a different symbol and thus my key programming was not overwriting the embeded bindkey. I was deleting the default value and then I had a functional SHIFT+3 bindkey.

Since a few months ago, this is not working. There is no other bindkey assigned - yet SHIFT+3 does not work.

Can you please guide me through that?

Many thanks,

BR,

D.

Have you tried using the Options->Bindkey editor, picking the application that  you are trying to enter a bind key for, and then using the green "+" button to add a bind key. Then in the place where it says "type new bind key" (or double click on the bind key cell on an existing row) press shift+3 on your keyboard (try a few other key combinations too to make sure it's working if this doesn't work). It should show you the bindkey incantation for your keyboard.

For example, for me it says "<Key>sterling" (yes, shift-3 is £ on my keyboard as I'm in the UK with a UK keyboard).

Andrew.

Hi Andrew, thanks for the fast reply.

I did this and the result was the bind key I loaded through my script.

That is why I am puzzled: The SHIFT+3 shows correctly programmed and no overlap, yet, it refuses to funcrion at all!

Any thoughts on that?

Many thanks!

BR,

D.

I don't understand what you mean by:

Dimitris Kar said:

I did this and the result was the bind key I loaded through my script

If you just mean that "Shift<Key>3" shows up on the form, that's not surprising. It shows up any bind key that you've defined - that doesn't mean that the key combination will be understood though when you actually press shift+3 on the keyboard. 

So for example, I had done this:

hiSetBindKey("Layout" "Shift<Key>3" "doSomethingOrOther()")

and on the bindkey form it shows:

What I was asking  you to do was this:

i.e. first press the green plus button, then where it says "type new bindkey" (if you move off the form, you may need to double click where it says "type new bindkey") press the actual key combination you want (e.g. shift and 3, or ctrl and h or whatever - just press the actual key combination on the keyboard). This will then show the recognised key incantation in the form, as shown here:

I hope that's clear. If that doesn't solve your problem, perhaps you can better explain by what you meant by "the result was the bindkey that I loaded through my script"?

Regards,

Andrew

Hi Andrew,

I was thinking Greek and typing English - sorry for that. It is exactly as you describe it.

Let me be more detailed:

When I press SHIFT+3 in the search field i get  " £ " . The Bindkey list returns empty below.

Yet, my originally programmed SHIFT<Key>3 vAddmetal3() shows in the list when I search for it.

Now, I replaced the SHIFT<Key>3 description in the field, with the <Key>sterling and ...SHIFT<Key>3 is functional!

I will do the same in my script.

Thanks Andrew! That solved a 7 year mystery!!!

Much oblidged!

BR,

D.

Hi Andrew,

Why we can't set few combination as bindkeys. I have tried using AltShift<Key>r and AltShift<Key>v in the option->Bindkey editor. But it is not taking the value. I am just wondering what may be the reason for the same?

The forum guidelines do ask you not to post on the end of an old (in this case 9 years old) thread.

By default, you can't define bindkeys using Alt, because the Alt key is used for menu accelerators (the underlined character in menus). So in the CIW if you do Alt-T-V-W it will bring up a ViVA waveform window.

You can disable that by adding:

ui enableMenuShortcuts boolean nil

to your ~/.cdsenv (note it cannot be done in .cdsinit - it must be .cdsenv as it has to be done early enough in the initialisation). Then you can define bindkeys using Alt as part of the key sequence, but the menu accelerators can't be used.

Andrew

The forum guidelines do ask you not to post on the end of an old (in this case 9 years old) thread.

By default, you can't define bindkeys using Alt, because the Alt key is used for menu accelerators (the underlined character in menus). So in the CIW if you do Alt-T-V-W it will bring up a ViVA waveform window.

You can disable that by adding:

ui enableMenuShortcuts boolean nil

to your ~/.cdsenv (note it cannot be done in .cdsinit - it must be .cdsenv as it has to be done early enough in the initialisation). Then you can define bindkeys using Alt as part of the key sequence, but the menu accelerators can't be used.

Andrew