I had a similar issue yesterday. The width was correct, but the container ignored the height. Deleting the container and recreating was the only thing that corrected the problem.
Also @pascal, my team syncs toolbars. Our Rhinos are pointed to a read-only share with the toolbars.RUI. I make changes, and they automatically appear in all the clients.
Now, we need to sync the containers that hold the toolbars. 1) There isn’t a way to put all of those containers into a single file. 2) Each individual file has to be manually imported on each client.
I’m currently evaluating version 8 and am finding the pop up menu very frustrating. I’ve created a container for my imported menus (my pop up has 3 tabs). Rhino sometimes displays it at my preferred ratio (13 icons wide), but mostly defaults to a narrower version (7 icons wide).
More frustrating is that I am constantly dragging tabs off the menu so I have to go through the rigmarole of adding them back. This seems to happen with the tiniest movement of the mouse, and is very annoying. I must do it five times a day! So far I haven’t managed to find a way of locking them so this can’t happen.
Same here, I’m finding it frustrating and my muscle memory has been with a 3(w)x6(h) pop up for years so it sounds petty, but its preventing me from switching full-time to R8 becuase it is slowing things down and I can’t afford the time to be slower in my work.
@pascal is there anyway that a solution to this can be looked at? Could we escalate it or somehow?
Thanks, Jon.
If any of you are experiencing issues where PopUpToolbar stops working all of a sudden, I think we nailed down the cause in this thread, So far, if I use a max width command window, PopUpToolbar continues working:
@pascal I just installed Rhino 8.7 and I’m having the same trouble as others. The popup menu no longer remembers my preferred aspect ratio. The MMB popup is always 4x8 regardless of how the container is set up.
It’s infuriating. The whole Rhino 8 UI is like this, as if no one who published the software had tested it in the real world. It needs to be solved to permit users to actually work instead of wasting our time trying and failing to repair the UI or spending significant amounts of time creating or defending detailed bug reports on the forums. Half those reports get lost, neglected, or punted for years, which sucks in ways I hesitate to put into words in public.
The Rhino UI used to help speed up my work. Now it just gets in the way. I keep trying to use 8 but within about 20 minutes I end up saying **** it and going back to 7 where, despite its many problems, most of the UI was trustworthy and there were fewer non-UI bugs to negotiate.
I’d be happy to screenshare for a few minutes with anyone on staff who would like to save hours of Discourse time just seeing what it’s like for me to try, and eventually fail, to work in 8. It would save me so much time and be far clearer to you guys what we’re dealing with out here. How much of my time has 8 squandered? I don’t even want to try to put a number on it.
To be clear, I’ve said it before, I’ll say it again: I love Rhino, I need it for my work, and I have faith that McNeel cares even more about it.
I’ve installed SR9.24 this morning and it is unfortunately still doing this for me too.
Pop up on the right, what it should be on the left:
@pascal I’m sorry to keep tagging you on this, but is this being looked at do you know? Muscle memory is hard to change when I’ve had the same popup toolbar for at least the whole time I was using R6, and R7.
Mine has been pretty stable for awhile now even when new releases are installed. But…
If I save my custom .rui, (which my custom popup is in) close Rhino and re-open, the popup gets resized. I imagine if the popup was in default and not in my .rui, it would probably do this more regularly. The bug has not yet been addressed, for me it’s one of the two or three remaining annoyances with the toolbar system.
I couldn’t get my imported RUI popup toolbar nor its container to match its floating layout. I then modified the V8’s Default Popup toolbar using only V8’s Default buttons (SVG). It seems to be working, although I haven’t been modifying it.
Has anyone else noticed whether the popup keeps its layout when using only SVG buttons and/or is part of the Default toolbar set?
Mine are all in a custom RUI with SVG buttons. There’s a test command to dump all of Rhino’s SVGs into a folder. I used those directly or took them into Affinity to make quick modifications like putting text over the save icon.
I also tried to match their use of black and white so it handled dark mode.
Is there work in the pipeline to sort out this glitch in a service release? For something so apparently trivial in terms of the way the user interface is presented, it (the random and erroneous resizing of the popup toolbars) makes for a big slowdown in the speed at which I can work. Mine should be 7 wide by 6 high, but is resizing itself to 7-and-a-bit wide x 5-and-a-bit high. The row of missing buttons at the bottom is a real pain. The double chevrons at the bottom right is a disaster in terms of functionality.
My Pop up menu is still randomly changing size. More often than not it seems to appear in a narrow configuration so I’m just getting used to it.
One thing I have noticed since switching to dark mode is that some icons haven’t changed to their dark mode colouring. I notice that the the line tools in the main menu are white on dark, but the same one in the Pop Up menu is black on dark. Is there a trick to getting it to update?
Hi - Yes, I’m using a Container for the popup. I have several toolbars on it, so thats the most sensible way to acheive what I’m after.
It’s a bit of a shame that this topic has been marked as ‘solved’ since September 2023, as clearly there are still some people having problems. Pascal’s announcement that the popup supports Containers does mitigate matters substantially, though. It’s only the fact that Rhino forgets the size and proportion of the popup that remains a problem?
@MattE I put the “solved” marker on this thread when @pascal had a solution for my specific question. There weren’t nearly as many people commenting on this at the time. It’s obvious from this thread that problems persist, so I have removed my “solved” marker.
