Are there any standards out there for how applications that have a system tray icon should behave?
I recently wrote an application that sits in the system tray most of it's life. I handed it to a friend, and her first instinct was to double click the icon to get at the main window (which worked). But this got me thinking. In .NET atleast, there are all sorts of different events and ways of attaching things to your system tray icon (click [left/right], double click [left/right], context menus, off the top of my head). Just thinking about it, I've come up with applications with a right click context menu (most), left click brings up the same context menu (Live Messenger), a (different) left click context menu (Daemon Tools), left click opens the main window (alot of the Windows notifications), left double click opens the main window (mIRC, lots of other applications). I've yet to discover an application that uses right double click, though I'm sure it's possible...
Are there any usability guidelines or standards as to how your application should behave under any of these particular situations?
You may want to read Those notification icons, with their clicks, double-clicks, right-clicks... what's up with that? from Raymond Chen's blog The Old New Thing.
He even includes a link to Guidelines for the Notification Area (more commonly known as the "system tray").
Unfortunately it's hard to have a standard when every one is different.
Double click to open and right click to have some sort of context menu are the ways I expect it to behave. Having an Exit command as the bottom icon on the context menu is good whenever it makes sense as well.
Related
How ungroup the "Open as..." context menu entry?
If I am using only 2 Profiles, I'm good
Screen of only 2 profiles
As you can see in the screenshot, I have to do two clicks for opening an url link within the other profile.
Screen of 3 or more profiles
But if I have a third profile, the context menu changes, it creates an expandable item, grouping the other profiles. That is very annoying, because I have to navigate first to the "Open as" line and then after a short delay or an additional click the profile-list appeares where I need to select appropriate profile.
Can we revert the behaviour to list all available profiles within the root context menu?
May we create a keyboard-shortcut for every profile, so pressing the asssigned button while clicking on any links, will open the url in that profile.
Or is there an extension for doing the job? I couldn find any useful information to solve this...
Thanks in advance for any helpful advices :)
(sorry for the spellingmistakes)
Offtopic:
(migrating from ff to chromium. Everyday web-based apps for end-consumers getting more focus, which means in my eyes, programmatically design gets more limited due to the main concept behind our standardized world wide web. And additionally user control gets worse everyday because that's the new key to generate money no longer just for complex & highly specialized products. e.g. timeinvestigation is enormous to through out all the bugs and bullshit extensions to get a reasonably useful tool for accessing the world wide web.)
Let me explain the situation.
I need to copy a lot of instances of a text inside a project of PhpStorm. So, I perform a 'Find in Path' action and a floating window appears with the matching results.
Now my problem is that after copying once from the floating window, if I click on another app window, then PhpStorm's main window/PhpStorm itself go to background, then if I want to copy text from the floating window again, I can not use any keyboard shortcut, I can not modify any line in the floating window because PhpStorm stays in background/inactive-mode even if I click on its floating window.
If I click anywhere in the PhpStorm except the main top-white bar of PhpStorm, then the floating window disappear, which causes me to perform the search again.
It is reducing my productivity a lot. Is there any way to make the PhpStorm active or bring it foreground when clicking its floated search window?
Please see the screenshot:
Is there any way to make the PhpStorm active or bring it foreground when clicking its floated search window?
You are approaching the problem from the a bit wrong angle. There is a better solution than fighting the focus/foreground state.
There is a button in the bottom right corner of "Find in Path" window ("Open in Find" it says on your screenshot) -- click it and it will open search results in traditional / standard Search Results tool window (with grouping by folders/files, preview area etc)... so no floating and no auto closing on clicking somewhere.
P.S. Lots of people forgetting that results shown in this new "Find in Path" dialog/popup is still just a preview (TOP 100 matches only). Super functional (you can edit and stuff) but still preview only. This mainly applies to those who remember the way how this dialog (back then it was dialog window) looked before redesign (now it's more of a popup).
Because of the way how it is all presented now (results occupy majority of the popup space) people somehow automatically forgetting about "traditional" way of searching (clicking actual "Find" button to get search working) and focusing only on what they see on a screen right now.
This new "Find in Path" dialog/popup adds a lot of convenience for sure (you typed search text and results are straight away before your eyes). At the same time quite often you may see/hear "it does not show me all results" frustrated comments (as it shows top 100 .. and a single file may have 100+ hits in some cases) and alike. JetBrains needs to improve UX a bit in this area for sure.
I want to debug code at the same time as I see what is being sent on the network tab without having to go back and forth between the Network tab and Sources tab. Is there a way to do this as of chrome Version 52.0.2743.82 or Version 54.0.2810.2 canary?
I know that it is possible to log http request in the console which can be visible with other tabs open but I want the actuall networks tab if possible..
Thank you in advance
This is now possible in Chrome 87. Right click Network in the menu and select "Move to bottom"
and it will do this
You can view 'Quick source' while viewing the Network panel (or the other main panels) at the same. This will allow you to view the source and add breakpoints.
However, it's not possible to step through code using the debugging in the split view. Chrome will automatically switch to the Sources tab if you use the shortcuts.
It's also not possible to have an extension running a separate instance of the debugger as the Chrome Debugging Protocol doesn't allow simultaneous clients to be connected.
I will open up a discussion with other Chromium contributors into the feasibility of sharing the debugging controls in the split view. I don't know whether it will or can be done easily. I suspect it's a fair amount of work.
If you would like to set up the split view, as it's useful anyway, go to overflow menu on the right side and select 'More Tools' and then select 'Show console'. This makes sure the panel loads below the main one.
On the left side of the panel that shows, click the overflow menu and select 'Quick source'.
You will now see a small Sources panel.
Since I was referred here from this question, I'll answer here.
In my scenario I need to be able to work on two different source files (under DevTools->Sources) simultaneously, for instance an html and a css file.
My workaround was to work on two separate tabs.
Right click one of them and click 'Open in new tab'.
When the new tab is open press F12 to open DevTools, and dock the two editors side by side (Focus on one and pressing ⊞+→ then leftwards on the other one).
Result:
I am building an extension for Chrome and Can't decide If I should use chrome.windows.create type popup , panel or detached panel. I could not find a comparative study of the three options . Any links or short description of positives and limitations of each will be helpful .
Thanks
You are having difficulty understanding it, because unless you specifically enabled an experimental feature, they are exactly the same, or rather the latter ones are ignored and a popup type is created.
Unfortunately, this means that this API is unavailable for general use until Google decides to mark it stable.
Quoting the docs:
The 'panel' and 'detached_panel' types create a popup unless the '--enable-panels' flag is set.
As for what panels are, here is the API proposal with detailed description.
Panels are windows that are visible to the user even while the user is interacting with other applications. The small windows are positioned at the bottom of the screen, with minimal manual window management by the user. This API will allow extension developers to create and use panels.
[...]
An extension opens small "pop up" windows, for example, separate chat sessions, calculator, media player, stock/sport/news ticker, task list, scratchpad, that the user wants to keep visible while using a different application or browsing a different web site. Scattered "pop up" windows are difficult for the user to keep track of, therefore panels are placed along the bottom of the screen and are "always on top".
The user would like easy control of chat windows: finding them, moving them out of the way, etc. Window management of separate chat "pop ups" is time consuming. All panels can be minimized/maximized together.
If you want a real-life example, the Hangouts extension is whitelisted to use this window type; that's how they make the chat panels:
Since chrome doesn't by default enable panels , this need to be set to display panel behavior instead of popup window . Note that popup windows can be re positioned and one can view console window , but none of it is available in panel .
I am developing an app. A page showing full image and when you tap on the image, image caption and sound options appear from two opposite sides i.e caption from left and sound options from right with translate animations.
I want to be clear about that when I press back button, I can navigate to back page or I have to make those options disappear first and then again press back key to go to previous page from microsoft certification point of view?
I believe this is the same since windows phone 7.
You should be allowed to capture the back event and add some code. I don't think that is seen as bad practice, you just aren't allow to stop it.
Saying that, I don't think you can easily do a double back. you might have to check.
Here is a fairly useful post on the subject:
WP7: navigate twice back
which leads to another post about navigating the stack:
http://blogs.windows.com/windows_phone/b/wpdev/archive/2010/12/13/solving-circular-navigation-in-windows-phone-silverlight-applications.aspx