Single Window Modeling

The problem with the bottom edge detection is fixed in the 2014-05-20 WIP release. Exotic suggestions like trying to detect whether the Dock is visible or not are just not possible.

Yea, I sorta had that feeling post post. For the Top edge, would ignoring the menus qualify as exotic?

1 Like

The screen edges code has been tweaked in the 2014-05-20 WIP release and works better. Detecting a bottom edge touch is now reliable.

Iā€™m not sure what you mean here. Are you asking that top screen edge touches get ignored on the left half of the top edge where the application menu is? If thatā€™s your question, thatā€™s not possible either. The actual display of the menu is up to the Apple frameworks, and I am unable to determine how wide it is. Also the right side of the top edge gets filled up with controls of different sorts, and I donā€™t know what is there, either.

Using the top edge is probably only practical for the secondary screen. Itā€™s included for the primary screen mostly for consistency.

As an alternative, you might consider getting a mouse with lots of buttons. Logitech has some good candidates.

Correct. Sorry for not including an illustration. A method to determine the space illustrated in yellow above would make Top edge practical on the primary screen. Not being a programmer, however, I take your word for it. Sounds exotic. Makes useful sense for a secondary screen, and consistency is logical.

Indeed! Uncanny timing. Just yesterday my trusty approx. decade old top of the line (at the time) Logitech died. Ran out and bought a Logitech Performance Mouse MX as replacement. Per Logitechā€™s web site it has 9 buttons. My question is - how many can I make usable in Mac Rhino?

So, without Logitech Control Center installed, beyond left/right/middle(wheel down) clicks, Rhino automatically responds to the indicated Performance MX button numbers shown below.
.

Trying to get Rhino to recognize the remaining buttons, which are wheel left, wheel right, and ā€œtilt.ā€ (Logitech calls ā€œmouse tiltā€ a buttonā€¦and that equals 10 buttons total per my math???) I installed Logitech Control Center. With LLC installed I could not get Rhino to respond to anything beyond left/right/middle in the default config. I created a Rhinoceros application config in LCC and played around with several settings for the buttons without successā€¦Rhino recognized nothing beyond left/right/middle until I uninstalled LCC.

It is quite possible, however, that I did not try hard enough, missed something, etcā€¦ I wanted to ask first before continuing to bang my head.

Thank you!

RE: Build 2014-06-30 Fixes - The top screen edge macro now ignores top screen edge touches directly above the application menu. These touches only invoke the macro when
you touch the top screen edge to the right of the Help menu item. This
makes the top screen macro much more usable.

YES! YES! YES! Thank you for that.

Personally, while I love using the the right screen edge tough to trigger _ToggleRightSidebar; still, could more control over the right sidebar be an enhancement to some, if possible. Perhaps the following is in the worksā€¦? In future is it going to be possible to define which of the icons is displayed - turn some off/on?

To optimize screen real estate further while the sidebar is open, would it be possible to enable further reduction of the width of the sidebar even if such were to create a crop condition (allow the crop) such as is illustrated below.

At present, as far I I can tell, width is constrained by the 8 icons, etc.

Yes, something like that will be implemented later.

I donā€™t think this is a good idea. The general scheme is to allow UI features to be completely visible or completely hidden, with several options for temporarily show a panel. Quibbling over a few pixels by hiding part of a panel is going to cause problems.

Compare your screen shot above with another screen shot you posted - the first screen shot in this thread. They are almost identical, but in the other thread you were wondering where the color well for Display Color had gone. In the other thread the right half of the panel had been inadvertently been hidden by a wide layer name and you needed to drag the panel wider to see the color well. I think partially hiding a panel will lead to many support problems like this.

Currently the minimum width of the right sidebar is fixed to a specific number of pixels that will prevent the contents of a sidebar panel from being hidden. It is not bound to the number of available panels in the sidebar.

Yes, trivial perhaps. I see your point. The ability to do so, via sliding a separate window somewhat off screen, was something I had gotten used to in the past, that I can certainly get unused to. Thanks for the thoughtful answer. I surrender on this.

The product is working really well already. Appreciate all the hard work. Looking forward to you guys driving it into existence (release). I should keep that in mind when tempted to quibble.