The title says it all. I use Jams Scheduler on a daily basis. The Shortcut menu, which is a default feature of the program and gives me access to job history and monitoring, is simply not on the front page when I open the program. I have tried altering font size and scaling options on Windows 10. The jams scheduler guide doesn't offer any help since every direction they have starts with "go to the shortcut bar". Please see the highlighted portion of the screenshot to see the portion that is missing. Has anyone run into this problem before?
JAMS has an option to make the Shortcuts panel float in a separate window by right-clicking on the Shortcuts panel title bar and selecting Float, or by dragging the shortcuts title bar out of the JAMS window. My guess is that your Shortcuts window is floating off screen.
You can restore your JAMS client back to defaults by deleting the version subfolder underneath your user's AppData Local folder for JAMS. By default, this folder is under C:\Users{username}\AppData\Local\HelpSystems\JAMS. Delete the 7.1.478.0 folder and the next time you open JAMS it will treat you as a new user with default views and a restored Shortcuts bar. This means you'll need to re-enter your server name, so if you don't remember it, make sure before you delete the folder you hit the gears icon and select "Servers..." to see your server name.
Related
I'm working on a Windows Setup Project in Visual Studio. In the "File System" editor, below the "User's Programs Menu" node, I have a folder for my application that contains several shortcuts. One shortcut serves to launch the application; a different one restores the application's factory settings (so it also calls the application, but with an argument).
After running the installer, the folder - and shortcuts it contains - are created correctly in the Start Menu. Additionally, without any action on my behalf, the installer creates an additional shortcut at the "top level" of the Start Menu (i.e. it's visible when one opens the Start Menu by clicking the Start button).
This additional shortcut used to be the one for launching the application. That was fine. But since I added the "Factory reset" shortcut, this is the one that appears at the "top level" of the Start Menu. This is pointless, and will just confuse users. Is there any way to change this?
EDIT (clarification): Since I added the "Factory reset" shortcut, only this shortcut appears at the top level of the Start Menu (which I don't want), and the shortcut to launch the application no longer appears (but I want it to). Note that all shortcuts in the Start Menu's subfolder are correct. What I'm referring to here is the single shortcut that appears automatically at the top level of the Start Menu (immediately visible when the Start button is clicked).
You'll have to explicitly mark your "factory reset" shortcut with the System.AppUserModel.ExcludeFromShowInNewInstall property. Raymond Chen shows how to do this in this blog post.
Note that this question was asked before.
In Xcode 4 (4.2), is there a way to keep the Project Navigator view open and Debug Navigator view open as well. Must a user have one or the other, but not both? And the other navigators?
Apple seems to have decided that if you want to see the debug view, you don't want to see the files in your project. WTH? Am I getting this wrong? Did Apple Xcode UI guys even talk to developers before designing the UI for Xcode 4?
Sigh...
You can indeed have more navigators open at once, if you are prepared to have multiple windows open. I know it's not exactly what you're asking for, but for multiple display setups it's very handy. Xcode provides "behaviors" to help automate this process if you only want certain things showing at certain times.
For example, a common pattern that developers follow is to setup a behavior for "Run starts" that opens up a new window setup for debugging. Start by creating a new tab in your main Xcode window by pressing command-T, and double-click on the tab's title to rename is "Debug", or whatever you like. Then drag that window out (or leave it as a tab if you like), and customise the view as required - for example, for a deb window you might have the Debug area showing at the bottom (or even covering the whole editor view), and remove the toolbar at the top by right clicking and selecting "Hide Toolbar".
Next, go to "Xcode > Behaviors > Edit Behaviors..." and choose "Run starts" in the left panel. Check the box for "Show tab" and enter the name of your newly created tab. You can also ask that tab to automatically show the Debug Navigator, and show the debugger with variables and/or console view. If you like, you can then choose "Run completes" and show the original "tab" (window), which I've setup to be called "Coding", and show the required navigator (in my case, Project Navigator).
On successfully running, Xcode will now open up your new window (or bring it to the front if it's already open) with all the settings you left it with. On stopping, your main editor will be brought back to the front.
There are loads of useful behaviors, so I would really recommend looking through them and taking the time to setup Xcode to suit your style as best as possible. All software dictates to the user how to go about doing things, and the developers can never please everybody when they decide to change the UI. The best anybody can hope to achieve is to customise the interface as best as they can to fit their style of working. If it's still an issue for you, you can either adapt to it, or, if possible, move to something else.
I'm not a fan of every new interface feature in Xcode, but I've "made it mine" with some customisations and I can still be very productive. That being said there are a lot of things that I do really like about it, and for that I can forgive it for some of the less friendly features - after all, you can't please every user.
As you might know katmouse enables scrolling over non active windows. Which would be especially great in vs 2010 because now you can take source code windows to other monitors. But of course it does not work. Is there a trick to make WPF receive the right message?
Try WizMouse, remember to set it to run with administrator privileges to make it work for admin level windows.
Yes, well, mostly.
Open the KatMouse dialog by right clicking and choosing settings. Go to the Classes tab, and drag the icon on the bottom of the dialog to an open vs2010 window. That'll add the new class to KatMouse. Now double click that new entry to bring up the settings for that class, and turn off the "Window has wheel scrolling support" checked box.
Unfortunately it seems like the class name changes for every source window, so I think you have tell KatMouse about every source window every time you launch vs. :(
How can I set the position for the output prompt in Visual Studio 2008 when debugging is started?
I have two screens and I want the prompt to always appear on my second screen so that I still can see the code on the primary screen, I have tried some tricks but I haven't got it right.
I'm not sure what you mean by "outputprompt". If you are creating a command line application and are talking about the command window, then
position the window where you want it (you can pause you app if it closes too fast)
click on its system menu, then click on properties
on the third tab of the appearing properties dialog, enter the values you like (be sure to uncheck automatic window positioning)
close the dialog by clicking OK
in the dialog that appears, pick the option that changes the link, instead of just changing the current window (I'm not sure either a German or English translation of the options is helpful for you)
HTH.
I have an application that gets installed with a Wise installer (EDIT: Wise creates a Setup.exe file, not an MSI). Upon installation, an icon is set for a certain file type:
HKEY_CLASSES_ROOT\.auz\DefaultIcon = C:\Path\To\App\some_icon.ico,0
Right after the installation, however, Explorer chooses to display this icon using the generic "white sheet + application icon" icon, which is different (and not provided by me).
Upon first launch, the application itself registers icons and other file associations, so that the last run version "owns" those documents. At that point, Explorer changes the icon for this file type and displays the correct one, but when I look at the registry, the value for DefaultIcon is exactly the same.
This is what I've tried so far
Removing all entries from the registry, and writing them myself.
After the installation, "touching" the value of DefaultIcon, and then launching a small little program that only calls SHChangeNotify(SHCNE_ASSOCCHANGED) (my program does this after updating the file associations in the registry).
After the installation, killing and restarting Explorer.
After the installation, using TweakUI to "repair" the icons on the desktop.
None of these work. The only way to get the correct icon is to let the program itself install it. I can't find any change in the registry. I'm pulling my hair off.
What I would like to avoid
Testing with another installer software
Changing the installation script too much (I don't have Wise itself, as the installer gets built on another machine on demand).
Embed the icons in the executable.
Any suggestions on how to get Explorer to display the correct icon after installation?
A couple of things come to mind:
why do you have the ',0' after the icon in the registry? That would limit the shown icon to one single icon. Better would be to have an icon file which contains several icons (same icon UI but different sizes/color depths) - Explorer has different icon views! Try removing the ',0' if your icon file only has one icon in it.
it may be that the registry is written last in the installer, after the explorer got notified of updates?
make sure the registry entry is written after the icon file is stored on disk
you should use the Wise installers own configuration to register the file type. Not sure, but I think explorer won't take any changes until the whole installation of an msi is finished, so calling SHChangeNotify() manually won't help. The msi has its own table for this, which Wise will add if you use the right configuration.
For Wise, do the following (instead of creating the registry keys on your own):
Under the Feature Details page group, select the File Associations page.
From the Current Feature drop-down list, select Core.
Click Add at the right of the window and select New.
The File Association Details dialog appears.
Click the Extension Details tab.
Browse to the QuickFacts directory, select the file QckFacts.exe, and click OK.
In Extension, enter: qft
Leave the defaults for the rest of the fields and click OK.
The extension .QFT is added to the installation. When an end user double-clicks a
file with this extension on the destination computer, the QuickFacts application
launches.
Save the installation
[Edit]
You may also missing required registry entries (the icon might not be enough for the shell to show it):
HKEY_CLASSES_ROOT\.auz\(default) = auzfile
HKEY_CLASSES_ROOT\.auz\shell\open\command = C:\Path\To\App.exe
Here's the solution.
Each file type (let's say ".auz" in this case) was registered with:
A DefaultIcon key with the path to the icon resource, and
A value for the HKEY_CLASSES_ROOT\.auz\(default) value giving a description of the file type, e.g. "Foobar Document".
In addition to this, there was an entry for the "Foobar Document" document type, or more specifically, a key for how to open such documents from the shell:
HKEY_CLASSES_ROOT\Foobar Document\Shell\command\open\(default) = C:\Path\To\App.exe "%1"
Apparently, this key supersedes the value written for the specific file extension. Because the icons are external to the .exe file, Windows Explorer then used the first icon of the application to create an icon for all files of type "Foobar Document" (that "white sheet + application icon" icon I mentioned).
Now, what I had wrong was that the application itself does change the value of
HKEY_CLASSES_ROOT\.auz\(default)
to a slightly different value when starting, say "Foobar 1.2 Document" (the problem with not being DRY). Thus, the link to "Foobar Document" was lost, and the .auz files got their icons after the first launch.
So I fixed this all by simply removing the HKEY_CLASSES_ROOT\Foobar Document key altogether, and voilà!