i understand that this might be a tough thing to wish for that somebody developing Rhino should be no less a power user to understand all the concepts involved. i dont see myself as such a power user, at least not in every aspect since there are far more skilled people here in many regards. but i do love a good, fast and sufficient workflow and i am very sensitive to changes when the idea of a specific workflow is interrupted, lessened or completely broken. and i am sure not the only one here if you look around.
recently that was quite noticeable that many of such concepts were completely broken, with people sitting right at the top of McNeel not even knowing about, talking in specific about the Mac version and how short cuts were handled before and the still ongoing migration procedure induced by handful of loud voices (from what i understood a few teachers) not even working on mac but wanting the mac version to be like windows (because it seemed easier to teach to them) completely deleting advanced evolved concepts to furnish the mac version with endless regressions to the pain of many users here. i am very regular on the forum but i did not manage to perceive the few topics where these sudden changes were silently agreed on. at least nobody i know off other than these was asked in specific but the choice to submit to these voices seems now so utterly random that it hurts and angers.
i can not blame anybody alone since these might have been collective decisions and is also not what i want, but the changes to the mac version is to date other than people believe to be a blessing simplification of the good kind rather a parade example of an aberration, and all i hear since this happened is that you guys are working to make that better. but i am really worried that the concepts once put into place in mac are lost forever in favour of these few people having this great idea to unify mac towards windows completely instead of reviewing both versions accordingly and select which one of the integrations were actually in fact already evolved.
somebody from your staff concluding that these people which i am one off that are not pleased with the new version of Rhino suggesting that this might be a matter of taste which i obviously seem to have a different one on not matching the current Rhino version, gives me shivers and sadness hopelessness and already so many points that i sound like in need of a shrink. no i hope not, but, since you are new, you have the power to be part of a reevolvement, or let it be an evolvement once again but making it better shall be hopefully part of you and never stop collecting input from whoever gives, rethinking logistic concepts to the favour of these who love to work fast and sufficient with less mouse clicks more speed more time to drink beer and enjoy life.
Referring to the removal of unadorned keyboard shortcuts: This I really donât understand. Win and Mac users both benefit from having completely free use of nearly any keyboard combination possible, without having to press the ENTER key. This is a ACAD modality from 30 years ago. Iâve adapted but it remains frustrating and my enter key is nearly detroyed
This has been discussed innumerable times already. What you expect to happen if you program a hotkey for some command or macro with for example the letter âcâ. What happens to the command line accessibility of the 99 or so other commands that start with âcâ?
maybe somebody has a shortcut for all commands ever used? but what is that to others to decide, if that improves the workflow and has been already planted in the mac version i see nothing that would hold against implanting that again.
Last I checked there is only one âcâ in the alphabetâŚ
For single key hotkeys, you are then limited to max 36 command possibilities (including single numbers) to do everything you need to do. Any other command besides those you would need to use the other keyboard shortcuts, menus or toolbars to execute. Aliases and the command line will be completely disabled.
Me, I donât have a problem with that as an option as long as it can be completely turned off.
not all shortcuts would have to be one key only, but let the user decide that, i also used single key shortcuts before all the v8 disaster happened. keys like , . and others. if somebody decides they want to brick their c so be it, if thats the only shortcut they use for some specific situation where they just want to be fast have only the same tasks to do that could help quite a lot.
having sets which you save and change if needed again and install is already possible so why not. also if the shortcuts get cleaned up to pre v8 like similar to v7 that changing shortcuts also can be faster having a search function for all the commands.
Not trying to be disrespectful; I genuinely think this is closed-minded thinking. Letâs begin with, âimagine a world where we can make any keyboard shortcut possibleâ or âwhat if we could do this or that without compromising someoneâs well established workflowâ and begin a journey of problem solving here, rather than, no, we talked already and it is not possible!
What we are longing here has already been proven possible by McNeel themselves. Perhaps there is a âswitchâ for lack of a better word where one could switch to allow the old school way of keyboarding, effectively changing the underlying system. In the opposite mode, users are free to make their own keyboard commands as they desire. Everyone wins!
Strange. I used numerous non-cad 3d apps before Rhino, and found the command line a genius concept, which I donât want to miss. Old does not mean bad⌠The paradigm of a computer mouse and pointer is from the 60ies, and it still holds up.
Iâm well aware of these discussions as I have been a part of many of them. The instigator in some in fact. Technicalities aside, the spirit of the conversation is, âwell we already talked about thatâ is not making progress, nor is it allowing open discussion on possibilities.
Iâm lobbying for the flexibility of all users to be able to use what working methods suits them best. There is a contingent of users here who welcome a workflow using minimal keystrokes to invoke a command.
The discussion has already taken place many times. This thread is not going to add any more to it IMO. Up to McNeel to decide if/when they want to do something about itâŚ
rhetorically questioning the use of this option, when it in fact was already up and running and people using and really happy about it is like running after the bus when the next one is behind you, thats right, makes zero sense. i assume that it could be very likely that all the users in favour of this option are fully aware of the implications.
@CallumSykes if i did not blast you away with my shear frustration yet, i do have one more esc missing
the versions when opened should also close with esc when nothing is selected. this is maybe so so important but nevertheless would be nice not to break habit/flow for consistency.
And yet if we remain silent, nothing will happen. As a user, I donât want to be silenced. We are all here to provide input, feedback and advice to a community for the betterment of all. Not to encourage others to sit down and be quiet.
no i believe not, this is probably not a v8 specific issue, but it would be good if all functional windows could esc eventually, besides panels and tools of course.
talking about it, today i noticed that zebra does not esc when the window was not activated. it makes sense that not allowing esc could be beneficial since selection process should stay escapable, but since this is a command maybe it makes sense to keep consistent here either? maybe it should in fact become a panel? the same with emap. just thinking out loud.
important but nevertheless would be nice not to break habit/flow for consistency.