Wellof course the next question is why?
Why are we forced to accept (a: enter repeating the last command, and (b: having enter hard coded to sundry buttons/keys other than the natural one handed down thru the mists of time from the great querty keyboard gods on high?
Why?
Not sure why I only have this problem on this computer but yes, why all of a sudden is RMB repeating the last command? It is supposed to just pan? That is one of the big reasons I like rhino!! Hate middle mouse pan on autocad.
I've modified my interface to use the right mouse button for the "enter" command. As a former AutoCAD user, I'm not finding one further enhancement that is very useful. In AutoCAD, it's called "right click customization" and it allows right click to do more than one thing. If a command is ongoing, then right click (in my case) would mean "enter". If no objects are selected, then right click means "repeat last command". This is something I use constantly. In Bricscad, if no objects are selected then right click brings up a dialog box where "repeat" is an option listed along with a number of other commands. This adds an extra step which, in the long run, slows things down. Since the drawing process often means performing similar actions in sequence then the ability to simply "repeat" w/o going through a dialog box is a faster way of working. Maybe there is a way to accomplish the same thing in Bricscad but I don't know what it is. Would appreciate any suggestions. Otherwise, I guess this could be taken as a feature request.
Just RMB to "repeat last command" is a bit tricky.
I once had settings (Quad deactivated or something) where it worked well,
but normally it is easier to use SPACEBAR instead.
As with Quad active, RMB by default will open Quad beside your cursor
and you need to relocate your cursor over the Icon of that "last used command"
before you release RMB to "accept" the command,
which is one tedious step more.
But maybe I am doing something wrong here.
You can set each of those variables just by typing the variable name. Or you can set them and also see a description of how each one works, by opening the Settings dialog and searching for "shortcut."
To choose what's on each of the right-click context menus, open Tools > Settings, the Menu tab, and scroll down to the section called Context Menus.
The DEFAULT context menu pops up when nothing is selected and no command is active.
The EDIT context menu pops up when something is selected but no command is active.
The COMMAND context menu pops up when a command is active.
The EDIT and COMMAND context menus have some built-in menu items that aren't listed in the Customize window. Those vary depending on what's selected or what stage of which command is active.
I am building a photoshop like color picker in my perspective application, and I have done some fancy math to determine where in a color gradient the user clicks, and calculate the color code accordingly. I even added a cursor Icon, to make it more clear where they have clicked.
The properties you mention here on the event object do not seem to have any way of determining their position within the view itself. I.e. the pageX and clientX can only give you the X position over the entire page, and not within the specific view of the item being clicked on. Do you know of a way to do that?
You need to use onMouseDown to set the page object properties.
In the event mouseDown is true, then onMouseMove needs to update the deltaX and deltaY appropriately, where they describe the difference between the original click position and the distance dragged.
Place a Change Script on mouseDown which resets ALL of the other properties to their default values is mouseDown is false.
onMouseUp AND onMouseLeave need to set mouseDown to false.
Bind instance.position.top to delta.y.
Place a change script on instance.position (the object), which sets the position of the instance by using the index property.
So I think I have most of this working, however the onInstanceClicked script does not run until AFTER the onMouseUp event, and so the index does not get set in time to reference it in the instance.position change script.
Ah, yah, what that component really needs is onInstanceMouseDown for an Event, along with an accompanying onInstanceMouseUp. It looks like for now there is not a way to get the mouseDown or click location within the View.
So, I managed to accomplish this with a mouseOver event on the embedded view, that changes an output parameter called mouseOver and then I call a messageHandler to check for any instances where mouseOver = True. That allows me to get my index value before I start moving, and it works great when moving from 0,0!
However, whenever I click the item again, the delta goes to 0, 0 and the instance moves to 0,0 with it (because of the script on the instances.position custom property), any idea what could be causing this?
Ah, there needs to be a sort of go-between variable which registers the initial original.instanceLeft and original.instanceTop. These values should not change during the drag, but they should be used to define the new position. So custom.instance.position.left should be expression bound to
I think we have a winner! It is not perfect, I think because of having to use the messagehandlers and timing, and with an onInstanceMouseDown and onInstanceMouseUp would really smooth that out. That would also eliminate the need to have the messageHandlers and output parameter too, making it a much smoother design.
Issue still exist after updating to Sonoma 14.2. I can't even describe how frustrating this bug is. Not a single word from Apple about this is a shame. 3 months after release and still not fixed. What's the point of reporting bugs, if they don't care at all.
I got the same issue after updating I got Macbook pro m1 pro 2021. this is very annoying. I have to restart again and again. There are time that it ok but 80% of the time its not. I got no antivirus installed. as you can see on the GIF, i cant even select anything on my nav menu.
I have reported an issue I am encountering with my Logitech MX Master 3S mouse when connected to my Mac running on an M1 Pro chip. The problem is that the menu highlights, which are visible when using the trackpad, disappear when I connect the mouse. This issue persists across all applications on the macOS.
I would greatly appreciate any assistance or guidance you could provide to resolve this issue. If there are any further troubleshooting steps you would recommend or if this is a known issue with a potential upcoming fix, please let me know.
I have been experiencing a persistent issue with my Mac recently, and it has been causing me a lot of frustration. The problem seems to be occurring frequently, and I initially thought it was specific to my machine. However, after stumbling upon a post related to the same issue, I realized that it is a widespread problem that many people are experiencing.
I tried running my Mac in safe mode to troubleshoot the issue, but unfortunately, it did not resolve the problem. I am still actively searching for a solution or any updates that may help me resolve the issue permanently.
The latest update didn't solve the problem. So what they are updating, and why do they not look into it? Let me be clear. I do not use any external mouse. It's just the internal trackpad. There was no problem with Ventura .. It's all about BUGGY Sonoma. This bug is very annoying, as a developer why the heck I have to deal with switching pages just to make trackpad work in the middle of my intensive work? Dropdowns need hover and the hover of our precious Mac keeps disappearing!
Don't buy it if you haven't yet. And if you bought it, do not update it as Apple developers don't care about the bugs. Maybe they think it's a very little bug(clearly it's not) so, it can be postponed to a later date!
I'm also having issues with my mouse after a few days of updating to Sonoma. I tested different mice and the problem is definitely the Mac. The mouse is recognized, but the left click is not working properly. I click on the menus, and they open, but then I cannot select any option. The weirdest thing is that when I restart the computer I'm able to use the mouse properly (when the system is still restarting)one time and then it is broken again. I need to use the tab or arrows on the keyboard to select things. I'm not sure how it could be related, but the problem started when I plugged the computer into a different screen than I usually do.
I just want to add here. An Apple support contacted me earlier about this issue. Well, they don't really know what's happening they just contacted me to go over the issues and they took some logs on my mac. They say that a good number of mac has the same issue but they don't have any idea what causing it. But tonight I discovered something about the wireless-connected device that might be causing it.
Issues appeared when I connected my mouse via Bluetooth or dongle and when I turned it off the issue disappeared. I think it is because of the software (logi Option+) but I tried connecting my other Bluetooth mouse (Generic one with no software needed just connected via Bluetooth) and I got the same issue so it's not on the software.
OMG, I'm having a very hard time with my iMac. It's driving me crazy and I'm thinking it was a biggest mistake of my life purchasing this computer with all the problems it has. I've had this problem with the mouse before but after updating to Sonoma it gets worse. I can't do anything. my space doesn't work in some apps and also I can't open any files using space bottom anymore. the mouse has glitch a lot. for example when I'm using Pages and start typing pages starts moving and I can't type. and there is a weird blue boarder I can see in my screen all the time.
I have a game that I am working on in a C# console application, purely as practice before going on to better methods. As opposed to using something such as a Windows Forms App, which has button functionality built in, I am endeavoring to grab the cursor position (which I know how to do) and compare it to a number of area's inside a console application as defined by perhaps pixel location, but I also do not know if there is some sort of built in unit of space other than pixels (this last bit is the part I am unable to figure).
3a8082e126