I've been working in Altium since version 10 and my usual workflow in schematic capture has been:
Freely drag components around with mouse left-click-hold (attached nets don't stick to component's pins)
While holding the mouse, pressing the spacebar would rotate the component
I've recently installed a clean version 17 (i.e. not an upgrade of existing installation) on Win10 x64 and now to do the same actions in schematic capture I have to hold down "CTRL" key, which is very annoying:
To freely drag components (so that the nets remain detached from the pins) I have to use CTRL+left-mouse.
To rotate while dragging, I have to press "CTRL"+Space.
I quickly got fed up with this, unable to find an option to modify this behavior, I uninstalled version 17 and installed 16, which has been known to work as expected in the past. Immediately after the installation version 16 behaved as expected (no need to use "CTRL" key).
But now, without any further computer/software modification the installed version 16 behaves as the version 17 did (i.e. "CTRL" key is required for the above operations). No options inside Altium have been modified to provoke a different program behavior.
Can anyone else confirm this behavior? Is there an option in Altium that I'm overlooking that would give me a choice of behavior in this regard?
I'm generally suspecting a Win10/.NET direction, but am not sure how to troubleshoot this.
Thanks!
For those looking to solve this as I did:
In Altium Preferences -> Schematic -> Graphical Editing uncheck "Always Drag". This should allow to move and rotate components freely without "ctrl" modifier key.
Related
I have been watching tutorials on youtube (i'm new to unity), I was trying to add a rigid body to my player, which I've never done. In the video they clicked add component in the inspector then physics then rigid body. but i don't see physics and when I search for it nothing appears. the only options i get are:
Effects
Layout
Mesh
Miscellaneous
Rendering
New Script
Underneath Box Collider i get a warning saying the the "module that implements this component type has been force excluded in player settings" could this be the problem? If so how would i fix it?
Thanks.
Try go to the PackageManager, switch to Built-In Packages and see if the package Physics is installed. Sounds like it has been actively be removed (uninstalled) or you somehow broke the Packages/manifest.json file.
If you can't even get the PackageManager try to reset the packages as described here via the top menu bar → Help → Reset Packages to defaults
or just directly replace your Packages/manifest.json with a one from a fresh empty project
Also note
Our first TECH stream release of the year is available as of today. Unity 2020.1 includes a wide range of features and improvements that make Unity workflows even more intuitive and make you more productive, while Unity 2019 LTS remains the recommended version for projects in production.
The PackageManager got an overhaul and a lot of users had issues like yours. See e.g. this thrread.
You should stick to the LTS versions, currently 2019.4 LTS (except for experimenting with the very newest features).
So if you type in the search bar of Add Component "Rigid" nothing pops up? If not I believe it should.
The problem could be in your libraries. Try deleting the library in your project (with Unity closed). Maybe if you have not made much progress in this project you could try opening a new unity project and seeing if it works.
I have just purchased the Steelseries apex gaming keyboard and rival mouse. Unfortunately, each of these products has different software for macros and keyboard lighting, both of which are mediocre at most.
Instead of having 2 processes running in the background and having to use 2 crappy programs to write my macros, I have decided to use AutoHotkey for my macros, some of which I plan on making quite complex. The mouse was no problem in AutoHotkeys, with the two side buttons using XButton1 and XButton2, however no matter what I do, I can't detect my keyboard macro keys (M1 to M12 and MX1 to MX10).
Using a keyboard hook doesn't detect any keys, and looking online I can't find how to reference these keys either. I'm not even sure windows sees them, as when I try to input them into the shortcut key field in a normal shortcut they do nothing. So my questions are:
What is the name for the macro keys on my keyboard in AutoHotkey?
Is there any way to work around this problem without having to use the Steelseries Engine?
If I can't access them normally, is there a way to reassign them without external software?
(Optional) Is there any way to adjust the lighting on the keyboard and mouse without the Steelseries software as well?
Btw I'm using Windows 8 and here are the links to the mouse and keyboard. Thank you in advance.
You can get the name for special keys that are not listed in AutoHotkey documentation by following steps here.
Some notes and explanations:
You can use that script for step 1:
#InstallKeybdHook
Sleep, 99999999999999999999
When you run it, check if keyboard hook is active by:
press here:
then here:
and if active, you should see something like here:
In the step 6 the hex value column is here:
If that is not working for you, try Alternate solutions in the link that I provided before.
using Microsoft Visual Studio Professional 2013 Version 12.0.30324.0 REL Microsoft .NET Framework Version 4.5.50938
I just upgraded a project from VS2010 to VS2013. On certain forms I can no longer use the mouse to move or resize controls. In some cases when attempting this VS2013 locks up
It's not just the controls either. I can't use the mouse to resize a "sizable" form. I also can't drop new controls on the form. I can however use shift arrow keys to resize the form and key in the size I want under properties. No I'm not debugging. Yes I have my snap to grid settings the way I want them. No I don't have controls "locked". This is clearly a phenomenon with VS2013. Occasionally, by futsing around with it the form seems to fix itself and the mouse actions function as normal. But as soon as I exit VS2013 and restart it, the ability to use the mouse on a form in design mode is hosed again. The issue seems worse on forms with many controls but can occur on any form.
As an experiment I created a new plain Jane form in VS2013 and dropped a couple buttons on it. I was able to resize the form with the mouse and do whatever I needed. However, when I exited VS and restarted it, The form exhibited the same behavior as my converted forms, in that I could no longer resize it or move my controls around.
I believe the issue is with the IDE and I'm forced to roll back to VS2010 so I can actually continue development.
I do also have VS2010 installed on the same PC which is suppose to be fine and dandy so I'm wondering it there is in fact some sort of conflict occurring.
If someone has some new insight on this I would love for you to share.
Thanks and happy coding,
Chris
When I try to delete a netbeans project, I get this dialog
I try to use left arrow key to switch focus from the No to the Yes button but it isn't switching. (This will work perfectly for any other windows application on my system)
Is this a normal behaviour for netbeans IDE or is something wrong with mine?
Just tried it with the latest development build, and I can confirm that the arrow keys do not move the focus.
My guess is that it is a Java/Swing/AWT thing, not necessarily a Netbeans thing. Unfortunately I do not have another Java application I can get to at this very moment, so the previous sentence is conjecture on my part.
On the other hand, TAB/SHIFT-TAB cycles through each of the UI items. A little bit farther around the mountain, but not quite as far as reaching for the mouse.
Dear RubyMine Overflowers,
I downloaded the latest version of RubyMine (3.2.1) on a Mac running SL 10.6.8 and latest apple provided Java.
I am experiencing some problematic behavior regarding the mouse right-click.
I can bring up contextual menus only by double right-clicking. if I single right-click, the menu comes up very instantly and disappears.
After some experimentation, I have concluded that if I right-click and manage to keep the mouse pointer at the exact pixel as before r-clicking, contextual menu disappears. If the pixel before right-click is different than the one after r-click the Contextual menu stays. (Imagine the chaos when this applies to the Project window: i get constant warnings of moving files).
Anybody experiencing such funny stuff in RubyMine? or otherwise, any way to change mouse pointer sensitivity?
Many thanks...
Petros
There is similar issue, but it's known to affect only Linux users with Eclipse keymap:
Intellij right click context menu problems in Ubuntu.
I can't reproduce it on Mac, but the question above is worth checking, maybe the suggested workaround will work for you.