V8 Shortcuts again? alt r suddenly not working?

are we playing battle ship? just make as many shortcuts unusable as possible to be sure that one loses interest in working with Rhino? it is supposed to be as reliable as possible, it is an unbearable non stop pain that makes Rhino as impossible as possible instead.

after updating to the recent Rhino it decided to kick out/delete one of my Shortcuts, i used alt s,w,r,x for object display modes, all others still work just not alt r, when i try to set it again it suddenly claims that it is a shortcut used by the operating system. i never ever had such a short cut functioning in mac os as far as i can think.

i really am tired running after each short cut and reconfiguring it because somebody had a great day!? why is this so bothersome since V8? i am really sorry if that sounds harsh but who is responsible for making such a mess with it? is it me?

2 Likes

just some extra info, the same is happening on WIP9,

BUT

testing in V7 it still works, so please dont blame the OS for it. can somebody please finally fix Rhinos short cuts.

That would be me :slight_smile:

This one is a tricky one. Shortcuts turn out to be annoyingly complex and I’d love to do a better job of this specific problem.

On mac Option + E, U and I are reserved by the OS for doing accents. You can see this is you try the shortcut in the viewport, it won’t make that maccy bonk in Rhino, but other unused shortcuts will, so of course, I notify people it’s in use by the OS.

That sounds simple, except it turns out to only be the case for en-us locales. If you change to Norwegian, then those aren’t reserved, but Option + R is. And Option + N for Japanese (IIRC).

I didn’t make checks locale dependent because a user can change locales and I can see it getting complex.

Apologies for interrupting your shortcuts @encephalon, and apologies for missing this issue.

1 Like

i dont have any “bonks” i like my keys besides the mechanically engineered quality sounds silent since it would keep bonking all over the place with the speed and inaccuracy i keep frantically hitting them with :wink:

i have an austrian keyboard, alt e does € for instance, though Rhino is set to English as a language that should not change my keyboard layout, but talking about it i have noticed that it seems to assume that i have an English keyboard when having it set to English as language, if i try to set new shortcuts i can not get some shortcuts done since i would have to find the english mapping for it, so there seems to be something off already if one can say so.

the burning question is, since it worked before and just suddenly has stopped, is there a way to have these functions back at some point? i would just prefer them working instead of being reminded what they could be used for otherwise…

:joy:

Does this ticket capture this? Or do I misunderstand? If so, it’s something I want to solve, but it’s quite complex.
https://mcneel.myjetbrains.com/youtrack/issue/RH-83731

I’m not 100% satisfied with the current solution, I like the idea of doing better, but I don’t have a better idea. I would like to allow every key possible, I also don’t want users to be able to create shortcuts that don’t work.

can you clarify what in your book “don’t work” means? those shortcuts that worked before dont work anymore that is for sure and it is concerning enough that Rhino is constantly being gutted to the last bone and i am not having any fun writing that, i dont want to blame you but since you have changed something that made shortcuts unusable and not configurable anymore i would really like to understand what the issue is.

shortcuts that worked in rhino before should just work again, i can not think of any operating system shortcuts one would need while working in rhino and if the user should be allowed to set that themselves and even if its changing cmd c and cmd v to do something else. also accents, special letters or however you call all these when produced with the keyboard should just work the same as any other letter either. maybe i am misunderstanding all that, some further explanation then would be neat indeed.

1 Like

Don’t work would mean, it does not fire, cannot fire. Assuming you’re on an English Keyboard, if you used Option + E as a shortcut, (which was previously possible to set) the shortcut would never be called because it doesn’t reach Rhino (as I understand it)

Is it just this? Or are other items being removed you need? I’d like to think Rhino is growing in features.

It’s 100% a change I made, I stand by it.

Some shortcuts, as far as I know, I cannot override, e.g CMD + Space, CMD + Tab, if you tried to enter those, the OS Shortcut will happen before it hits the Keyboard shortcut dialog.

As I said I’d like to allow every key possible, without it being possible to create shortcuts that won’t work. If Option + R is created on a English layout, and a user switches to a Norwegian layout, shortcuts they created mysteriously wouldn’t work anymore because the OS absorbs the shortcut in that locale when it didn’t before. I don’t believe I can stop that.

As to why the Dialog accepts (for example) Option+E fine, and Rhino doesn’t? I’m assuming the Option+E is piped to the command line as a character as it is ´

there were so many things removed and radically changed in v8, that people complained high and low about these not only because of the windows version but mac in specific got a real hit, rolling up all that once more is going the other direction, lets stay focused on shortcuts please.

i am not fully convinced that this is true, if the user wishes so why not let him do so, if the system really catches fire i can always change it in the os system settings. not a reason to exclude these options.

cmd space for instance is always an option that i can turn off in the system.

maybe cmd tab is trickier but maybe even that would be possible, but if that is the only one really not working full stop then i certainly could live without that.

as for alt r etc which stopped working suddenly after you have changed it not so much.

1 Like

Fair

I don’t exclude them explicitly, they just aren’t received, if you change them in the OS, they may work, I wasn’t aware you could change that.

Yes, this could be a valid shortcut, under certain circumstances, i.e if your keyboard is setup in certain languages. The options I see are;

A). Prevent adding shortcuts based on current locale
Pros : A few more more shortcuts
Cons : Users may find shortcuts don’t work when changing keyboard layouts

B). Prevent adding shortcuts that are unusable across all locales (current implementation)
Pros: Created shortcuts always work
Cons: A few less shortcuts

i never change the keyboard layout, i have one physical keyboard and i am quite alright with the german mapping even though i write a lot of english. it would also be confusing to have a different mapping suddenly, so i am not quite getting that point.

i would not prevent anything i am really not quite sure what you mean here
maybe there is a confusion that involve thinking i would like to write somewhere rather than hitting shortcuts? since writing in rhino if not in some text based command invokes commands that is the right place to leave all the bells and whistles alive.

since you have changed the circumstances for shortcuts that flawlessly worked before, can i expect these to be working soon again? i hope that does not come across too confrontative, but this topic just keeps growing and it does not get us anywhere…at least it does not seem so to me.

By circumstances I mean that as long as your keyboard layout is english, or a few others, Option+R is fine, but it is not fine on other layouts, for other users, e.g Norwegian. They’re set by Mac OS, those are circumstances out of my control

I’m trying to explain why I won’t be re-enabling option+R, but I’m don’t feel like I’m doing a very good job. I’m sorry to have removed your shortcut, but I don’t want users to be able to create shortcuts that mysteriously don’t work when switching layouts.

The above options are the only two I can see, and until I can find a good 3rd option, option B, the current implementation will remain.

why would somebody switch layouts, the different mapping would be distracting and unusable? and in which way does alt r pose a thread to anything not working in mac os? i have never used alt r for anything else, it is used for copyright in the german language ® but that only is purposeful when i want to write that, and even writing it or using ® as a shortcut should work so what exactly is the issue?

i think there is still some confusion going on, the system i currently use allows rhino 8 prior to the recent updates to use alt r on my keyboard, and it allows v7 to use these shortcuts, nothing that the operating system prevents or dictates. prohibiting these does not make sense, this or i am completely oblivious to the obvious reasons.

so to be sure i switched the layout to Norwegian, in fact i am just typing in this layout, and alt r does nothing here, does not even bear any special letter so what is really happening? please just bring these short cuts back. if somebody runs into issues why ever because of frequently changing layouts dues to whatever reasons unrelated to rhino and this indeed has some weird reason that is somehow strangely enough impossible to explain then dont let everybody suffer on that.

@CallumSykes i also checked in others apps, ALT R is usable in any other app i tried, Rhino is the only one that does no allow it suddenly.

i feel that your decision is not a good one since the people that would switch between norwegian and german (or whatever language) and need that switch in rhino are very few if at all it just does not make sense. can you please revisit that again

We are discussing the dead key shortcuts (option + R etc) internally and if/when there’s changes or updates I’ll mention them here.

1 Like

holding thumbs and crossing fingers…
i also have some more issue/requests in a new topic maybe you check it out in the meantime.

I always like to deliver good news, so I am too

1 Like