How to Close Skype
-
@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.
-
@JaredBusch said:
@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.
Something running on the taskbar is not considered to be closed.
This, to me, is a failing of Windows as an OS. I've felt this way about several interface things in Windows. In iOS, the close functionality is handled by the OS and cannot be overridden. If you force a close, it closes. They don't let the application developers take common interface elements to this level and make them do other things. I realize that Windows is keeping things more open, but I think that they make a mistake of taking it too far and allowing application designers too much freedom. They could just as easily have that close button, that could have been outside of the application and just connected to it, be the "format hard drive" button and say that that was what close meant to them.
-
@art_of_shred said:
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.
What I've found, given that I find Skype so annoying that I only use it when necessary, is that when someone mentions Skype, all I think about is that it is this annoying "nagware" that doesn't close when you tell it to or even get out of your face but nags you to use it by sticking to the taskbar. I think of Skype as only barely one step removed from the Ask Toolbar.
-
@art_of_shred said:
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.
I agree that it would be nice, but that would require a change int he default windows behavior.
On a side note, An application also has a setting at the project level that developers can choose to exit an application after all forms are closed. By setting this, a dev does not have to write code into the X button and the application will still close once all the windows forms are closed. I do not like to trust in that functionality though and I always specifically code my windows forms to exit the application on form close as appropriate to the app.
-
@JaredBusch said:
@art_of_shred said:
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.
I agree that it would be nice, but that would require a change int he default windows behavior.
On a side note, An application also has a setting at the project level that developers can choose to exit an application after all forms are closed. By setting this, a dev does not have to write code into the X button and the application will still close once all the windows forms are closed. I do not like to trust in that functionality though and I always specifically code my windows forms to exit the application on form close as appropriate to the app.
Thanks for that information. I never knew that (why would I?), and I guess it makes all the difference.
-
@JaredBusch said:
@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.
Understood, but close window to me means not in the task bar (but can be in the notification bar). And - that is the way Skype USED to work.
-
@Dashrender said:
@JaredBusch said:
@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.
Understood, but close window to me means not in the task bar (but can be in the notification bar). And - that is the way Skype USED to work.
Yes. Am I mistaken, or did that change when MS took over Skype?
-
@art_of_shred It's been a while, I'm not sure that I can identify the pre-MS Skype from the new Skype behaviour anymore.
-
I don't recall when it changed.
I'm further an anti-fan of Skype when they change the underlying technology to go through their own servers for surveillance purposes.
Skype used to be point to point (encryption setup by the endpoint, eavesdrop proof... today, it's no different than a landline).
-
@Dashrender said:
I'm further an anti-fan of Skype when they change the underlying technology to go through their own servers for surveillance purposes.
This also undermines the quality and reliability that it was known for originally. Now it is just a new interface for Lync.
-
@scottalanmiller said:
@art_of_shred It's been a while, I'm not sure that I can identify the pre-MS Skype from the new Skype behaviour anymore.
I don't use it enough to really know. It just seemed that the change was in the months-long gap I didn't use it; and the switch-over was in that same gap.
-
@art_of_shred Microsoft took over in May, 2011.
