How to Close Skype
-
I will admit I rarely use Skype unless prompted to do so by a team member. However, I won't assume that anyone else out there uses it in any specific way. Making assumptions about a widely-used product based on the (mostly assumed) information you have about how the people you know and their use of it, is basically worthless. Like I have a clue what millions of people out there are using their Skype accounts for. You don't either. Get used to it.
-
@scottalanmiller said:
It is only ever a momentary "open it to connect with someone I've arranged to talk to" software.
Then instead of clicking X and expecting it to quit the application (which is not a default behavior of the Windows platform as discussed above) simply right click the notification area icon and choose exit.
I will agree that the option to minimize to taskbar on the X click should (at least the first time) ask you which behavior you want to set as the default.
-
@JaredBusch said:
The people you know and the people I know are different then because of the 15 people in my contact list they almost always have Skype on for ease of communication.
You would be most likely to be adding people who keep it on. I think that you will find tons and tons of people who require Skype to talk to that one or two people who use it and use nothing else. Using Skype is one of the super annoying third party systems where there are just enough people using it that everyone needs access to it but most people don't want it around - especially given how poor the interface is and how clunky everything is. It's extremely poor to use unless you are in it all of the time.
I've probably got thirty or more people in my contact list, only two or so are ever on any any given time. I'm not aware of many people who leave Skype open all of the time. That's extremely surprising to hear. I know of no one who doesn't have it, but you are the first I've heard of that uses it as a regular, full time tool.
-
@JaredBusch said:
I will agree that the option to minimize to taskbar on the X click should (at least the first time) ask you which behavior you want to set as the default.
And should never be a "minimize to taskbar" which already has a button in the same place. This is a degree of either overly sloppy or just outright mean interface design that you don't normally see in legitimate software.
-
@scottalanmiller said:
And should never be a "minimize to taskbar" which already has a button in the same place. This is a degree of either overly sloppy or just outright mean interface design that you don't normally see in legitimate software.
Many, many communication applications have this option. It is an option.
-
@JaredBusch said:
Many, many communication applications have this option. It is an option.
To keep it in the taskbar as a duplicate functionality of two buttons? What other software does this?
-
@scottalanmiller said:
@JaredBusch said:
Many, many communication applications have this option. It is an option.
To keep it in the taskbar as a duplicate functionality of two buttons? What other software does this?
Lync, for starters.
-
Lync does not do that, Lync's close button goes to the notification area, it doesn't just "not close."
-
-
I Just tested it with Lync. It minimized to my taskbar, not notification area. I have not messed with default settings.
-
@FiyaFly said:
I Just tested it with Lync. It minimized to my taskbar, not notification area. I have not messed with default settings.
Weird, I just tested here and it went to the notification area.
-
@scottalanmiller said:
Lync does not do that, Lync's close button goes to the notification area, it doesn't just "not close."
You are again incorrect.
-
Define "not close". If I hit the X and it's still running, that means not closed to me. That's what Lync does, that's what nearly every chat thing I've used does. It's pretty normal.
-
@scottalanmiller said:
Weird, I just tested here and it went to the notification area.
Then you changed the default setting at some point.
-
@art_of_shred said:
Define "not close". If I hit the X and it's still running, that means not closed to me. That's what Lync does, that's what nearly every chat thing I've used does. It's pretty normal.
By definition based on the links posted previously and by my personal experience writing windows form based applicaitons, it is a close window button. it is not a close applicaiton button unless the software developer also specifically adds code in the Me.FormClosed event handler. A lot of basic applications do this, so it is how people assume that it is an exit program button.
-
@JaredBusch said:
@art_of_shred said:
Define "not close". If I hit the X and it's still running, that means not closed to me. That's what Lync does, that's what nearly every chat thing I've used does. It's pretty normal.
By definition based on the links posted previously and by my personal experience writing windows form based applicaitons, it is a close window button. it is not a close applicaiton button unless the software developer also specifically adds code in the Me.FormClosed event handler. A lot of basic applications do this, so it is how people assume that it is an exit program button.
Are you then saying that a closed window with the icon still on the taskbar, not just the notification area is closed? definitely not what I consider closed.
-
@Dashrender said:
@JaredBusch said:
@art_of_shred said:
Define "not close". If I hit the X and it's still running, that means not closed to me. That's what Lync does, that's what nearly every chat thing I've used does. It's pretty normal.
By definition based on the links posted previously and by my personal experience writing windows form based applicaitons, it is a close window button. it is not a close applicaiton button unless the software developer also specifically adds code in the Me.FormClosed event handler. A lot of basic applications do this, so it is how people assume that it is an exit program button.
Are you then saying that a closed window with the icon still on the taskbar, not just the notification area is closed? definitely not what I consider closed.
No, I am not calling that closed. I am saying how is sitting in the task bar different than going to the notifications? Either way, it's still running in the background.
-
@art_of_shred said:
No, I am not calling that closed. I am saying how is sitting in the task bar different than going to the notifications? Either way, it's still running in the background.
Point taken. One, though, is in your face and one is not. Often people are looking to clean up their taskbars, that was the purpose of choosing the close button over the minimize button explicitly but then it does exactly what the minimize button is for. It's not that you need to close it all of the time, but if you have a button with the only viable reason for its existence being to at least get it out of the task bar (I'd prefer if it actually shut it down, I shouldn't need multiple steps for such a common task) I'd like to not be surprised by a change in the Windowing interface and have to take additional actions for an action I already clearly conveyed to the application.
-
@Dashrender said:
Are you then saying that a closed window with the icon still on the taskbar, not just the notification area is closed? definitely not what I consider closed.
It is closed because the X button is a close window button. Not a close application button. That is by design. Yes a developer can additionally add in a function to Application.Exit(), but that is not required nor default.
-
@scottalanmiller said:
@art_of_shred said:
No, I am not calling that closed. I am saying how is sitting in the task bar different than going to the notifications? Either way, it's still running in the background.
Point taken. One, though, is in your face and one is not. Often people are looking to clean up their taskbars, that was the purpose of choosing the close button over the minimize button explicitly but then it does exactly what the minimize button is for. It's not that you need to close it all of the time, but if you have a button with the only viable reason for its existence being to at least get it out of the task bar (I'd prefer if it actually shut it down, I shouldn't need multiple steps for such a common task) I'd like to not be surprised by a change in the Windowing interface and have to take additional actions for an action I already clearly conveyed to the application.
This is where I agree that it is somewhat annoying. If you're going to have a standard, keep to the standard. I like the X to close an application. But, this is the real world, where we don't always get what we want. And it's not always selectable in the options menu. Oh well.
