Re: Windows 10 Properties Shortcut
Latrisha Adan
So for me it is not persistent, just happens occasionally. From time to time Ctrl+Alt+ keyboard shortcuts stop working on a Hungarian keyboard layout (Windows). I need to switch to an English layout where they do work - as suggested by Yuval.
Not sure whether this is the same problem, but today I restarted Figma and now Ctrl+Alt+C goes to Comment mode instead of copying properties. Only workaround I know of is to use the menu, Edit > Copy properties. Quite annoying. My version is 98.14 (Windows app).
I am having the same issue today.
Changing the keyboard layout workaround works but it definitely not optimal.
It used to work well with ENG-INTL keyboard before. Switching the keyboards layout all the time is painfull.
Same here. I discovered that Loom was causing the problem by closing tray applications one by one until the Ctrl + Alt +C shortcut worked. Then I checked Loom preferences and found the shortcut conflict.
I've assigned shortcut keys to numerous application shortcuts (right click the shortcut > Properties > Shortcut tab > Shortcut key). I've been using these shortcut keys for years with no problems, but this morning they stopped working normally.
The actual cause is Nvidia's overlay, which as of 2019 is called "In-Game Overlay" in the settings page within GeForce Experience, and is controlled by the "NVIDIA Share" process. The overlay itself also listens for hotkeys; presumably that interaction is the source of the problem.
As a workaround, disabling the "In-Game Overlay" setting within GeForce Experience will prevent the indicated problem - that shortcut keys no longer work when you are on the desktop, i.e. all programs are minimized. Enabling the overlay feature will prevent shortcut keys from working in that situation.
Unlike the asker, I found that the shortcut keys will work so long as any program* is unminimized - it does not even need to be focused. Nvidia's overlay has special behavior regarding the desktop itself, but this bug is not dependent on the related setting (Privacy Control -> Desktop Capture) within the nVidia Overlay.
*This includes, for example, even the properties pane of a shortcut. However, it does NOT include UWP apps such as the modern Windows Calculator or the modern Personalization dialog. It also does not include the Nvidia Overlay itself, nor utilities like RainMeter.
This morning, the October 2018 Windows Update finally became available for me to install (Windows 10, version 1809). As soon as I installed it, my third monitor stopped being recognized. At that point, shortcut keys were still working in the problematic way described in the question.
In troubleshooting the monitor problem, I deinstalled my nVidia driver and reinstalled the latest version. Once I finally got all of my monitors working again, shortcut keys were working consistently.
Every Windows object possesses properties that control its behavior or use. Shortcuts are no exception. You can view the properties for a shortcut by right-clicking on the shortcut icon and choosing Properties from the context menu. The Properties dialog box appears. The Shortcut tab of the Properties dialog box is displayed by default. (See Figure 1.)
The first field in the dialog box is the Target field. The information contained here was derived when you first created the shortcut. This is the path and name of the file to which the shortcut points. If you change the information in the field, then you change the nature of the shortcut by changing to what it points. Changing the target also changes the icon that is used for the shortcut, but it does not change the name of the shortcut itself.
The next four fields in the dialog box allow you to control how the target is executed. First, in the Start In field, you can specify what directory to use when starting the program or opening the file. This path does not have meaning for shortcuts to documents, but it can mean quite a bit in shortcuts to programs. By changing the value in this field, you can control what data are immediately available to a program when it is started. For instance, you may create three shortcuts to your accounting program, one each for the years 2016, 2017, and 2018. The only difference between the three may be the value set in the Start In field. In the first shortcut, the field should be set to the path that contains the 2016 accounting data. In the second, the path to the 2017 data is used, and the third contains the path of the 2018 data.
The next field, Shortcut Key, allows you to specify a keyboard combination that runs the shortcut. This combination can also be used to switch to the program window if you have already opened the shortcut. By default, the Shortcut key field is set to None, meaning that no key combination is specified. If you choose to change the value of this field, enter the characters CTRL, ALT, or CTRL+ALT, followed by the key to be used in combination with these. As an example, if you wanted to use the key combination of Ctrl+R, then you would enter CTRL+R in the Shortcut Key field.
When choosing a shortcut key for a shortcut (sounds redundant, doesn't it?), don't use a key combination that is already used by a different Windows program. Doing so makes the shortcut key in the Windows program unavailable.
The next field in the dialog box, Run, allows you to specify how the program that is being indirectly run by the shortcut should begin. You can make three choices here: Normal window, Minimized, and Maximized. You can pick the one that reflects how you want the program to be started.
The final field in the dialog box, Comment, allows you to make a note to yourself that explains something about your shortcut. This can be very helpful for jogging your memory a couple of months down the road when you've completely forgotten why you ever created this shortcut in the first place.
Most of the time you'll only want to modify the properties made available in the Shortcut tab. You can, if you desire, explore the other tabs in the dialog box. Each of them provides a number of pieces of information and controls that affect how the shortcut is used by Windows.
With more than 50 non-fiction books and numerous magazine articles to his credit, Allen Wyatt is an internationally recognized author. He is president of Sharon Parq Associates, a computer and publishing services company. Learn more about Allen...
The MsiShortcutProperty table enables Window Installer to set properties for shortcuts that are also Windows Shell objects. Beginning with Windows Vista and Windows Server 2008 the Windows Shell provides an IPropertyStore Interface for shell objects such as shortcuts. A Windows Installer 5.0 package running on Windows Server 2008 R2 or Windows 7 can set these properties when the shortcut is installed.
A string value that provides information for the PROPERTYKEY structure. The information in this field must refer to the canonical name of a property registered with the Windows property system. For more information about the Windows property system, see the Property System Overview.
Windows Installer can set shortcut properties only when the shortcut is installed or reinstalled. A patch that does not reinstall a shortcut that has already been installed does not update the shortcut's properties. A patch can update the properties by including a Shortcut table in the patch package and reinstalling the shortcut.
In Windows File Explorer, Alt + double-click on a file or folder pops up that item's Properties page. It is equivalent to right-clicking and selecting Properties. This is a useful, time-saving keyboard shortcut/gesture.
The shortcut should work for lvclass and lvlib items, VIs, and CTLs (and possibly other item types too). For lvclass and lvlib items the Properties window would appear. For VIs and CTLs the VI Properties window would appear (equivalent to Ctrl + I).
And while at this topic, it would also be nice to add context menu keyboard shortcuts. Sorry I don't recall their proper name, but I would love to use right click, R to open the properties. The same goes for the rest of the menu items that have a common use in other environments, like Windows, MS Office etc.
I am working with several other people in a share Dropbox folder, which contains several subfolders. Now I wanted to create a shortcut from one subfolder to another subfolder within this Dropbox (everybody has access to every folder) to save space - is this possible without .ink-files appearing in the shortcut?
Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
What do you think about the Community? Fill out our survey here!
First create the shortcut as you would normally do. Then in file properties, change the target to replace the "C:\...\Dropbox\ ..." to %USERPROFILE%\\Dropbox\... where the ellipsis is the rest of the file location. You can also change the "Start in" to C:"^%UserProfile^%\\Dropbox\".
When the system synchronizes, the other users will get the updated location, which automatically replaces the %USERPROFILE% variable with the appropriate location for them. Note, this only works within the app, as the sync'd files are locally stored. Effectively, the link customizes itself for the given user. This also works for file links.
First create the shortcut as you would normally do. Then in file properties, change the target to replace the "C:\...\Dropbox\ ..." to %USERPROFILE%\\Dropbox\... where the ellipsis is the rest of the file location.
d3342ee215