![]() ![]() The changes I made to the code now made NextSTART execute the shortcut itself instead of the target application.Īnd why is this a problem? Because of the automatic file system re-direction in 64 bit systems for 32 bit applications (PITA!!). Particularly the 'All Programs' sub-menu of the Windows Start Menu: all you have there are shortcuts to applications. So now we would run the shortcut itself instead of trying to resolve it automatically.īut I forgot one very important thing: NextSTART. ![]() This makes sense because shortcuts can be deleted at any time.Ī dock item specifically pointing to a shortcut could thus only mean that the user had deliberately made that item point to a shortcut. ![]() This should work fine since shortcuts are immediately resolved when you drag & drop items into the dock (i.e if you drop a shortcut into the dock, the dock item itself will point to the target application, NOT the shorcut). To solve this issue, I changed the code so that, if a user explicitly targeted a shortcut in the Item Properties dialog, the shortcut itself would run instead of the target application. This happened because the routine that executes programs automatically resolved shortcuts - so it would actually run CMD.EXE instead of the shortcut itself, thus by-passing the user's customization options. The shortcut did run, but not with the customization options he had selected (if you remember, in the shortcut itself to a CMD window you can specify things such as font size, etc.) ![]() Some time ago during v16.2's development, a user contacted me because he wanted to run a customized shortcut to the command prompt. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |