window-specific tasks, delay in window fadeout, etc.

Post your suggestions, wanted features,... for ShellEnhancer here.

Moderators: Marc G, Johan G

window-specific tasks, delay in window fadeout, etc.

Postby mortee » Mon Jul 12, 2004 8:51 am

Hi!

I just found your utility referred from betanews.com, I installed it, and really like what I've seen sofar.

I'd have a few comments though. First, it'd be nice if one could create window-specific tasks. That is, activate/enable the given task only if the specified app or window is in the foreground. It'd be the simplest to have a popup menu on the task dialog, with the available automanaged windows (along with an item to define a new one...)

Also, it'd be nice if there would be a slight delay between the mouse going over the window-border-buttons and the window becoming transparent (if it's enabled at all). I find it very useful to have a fast and intuitive way to make a window temporarily transparent, but it's really disturbing if it immediately goes transparent, even if I just want to close it. Also, I don't know if it's possible, but the button in question should be kept opaque, while the rest of the window made transparent (it's quite inconvenient that the very button you're going to click almost entirely disappears...)

Also related to transparency (and I also don't know if it's possible), the enhanced task switcher should not be uniformly transparent - only the background, and the contents (icons, labels, preview) should be opaque.

I like the possibility to block the screensaver from a task, but enabling this from a screen corner should somehow be streamlined a bit. Currently, if I link a screen corner to blocking the screen saver, then it *starts* blocking, but when I move the mouse away, it should also end it. I realize it's not trivial to solve, since the task is a one-time action, and has no notion of the mouse entering and leaving the screen corner. Maybe, a few of such simple actions should be pre-defined for linking to the screen corners (without being separately defined as a task), and this predefined thing should behave as I wrote.

The window rollup function is really nice, as well as the option to roll them down on mouse over. However, if both are enabled, then as soon as the user rolls up a window, it rolls down again in a second (because you have to go over the title bar to roll it up anyway). So I suggest to disable auto-rolldown until the mouse left the titlebar for the first time after rolling up the window.

Keep up the good work! I'm sure I'll have a few more suggestions as I play around with the app.
User avatar
mortee
 
Posts: 28
Joined: Mon Jul 12, 2004 8:31 am

Re: window-specific tasks, delay in window fadeout, etc.

Postby Marc G » Mon Jul 12, 2004 9:51 am

mortee wrote:Hi!

I just found your utility referred from betanews.com, I installed it, and really like what I've seen sofar.
:D

mortee wrote:I'd have a few comments though. First, it'd be nice if one could create window-specific tasks. That is, activate/enable the given task only if the specified app or window is in the foreground. It'd be the simplest to have a popup menu on the task dialog, with the available automanaged windows (along with an item to define a new one...)
Nice idea, i'll add it to the todo list.

mortee wrote:Also, it'd be nice if there would be a slight delay between the mouse going over the window-border-buttons and the window becoming transparent (if it's enabled at all). I find it very useful to have a fast and intuitive way to make a window temporarily transparent, but it's really disturbing if it immediately goes transparent, even if I just want to close it. Also, I don't know if it's possible, but the button in question should be kept opaque, while the rest of the window made transparent (it's quite inconvenient that the very button you're going to click almost entirely disappears...)
I'll add a user-defineable delay for the window-buttons-transparency.
I'm not sure if it is possible to keep the window-button opaque because ShellEnhancer doesn't 'own' the window, but i'll take a look at it.

mortee wrote:Also related to transparency (and I also don't know if it's possible), the enhanced task switcher should not be uniformly transparent - only the background, and the contents (icons, labels, preview) should be opaque.
This might be possible (i'm not sure). I'll give it a try.

mortee wrote:I like the possibility to block the screensaver from a task, but enabling this from a screen corner should somehow be streamlined a bit. Currently, if I link a screen corner to blocking the screen saver, then it *starts* blocking, but when I move the mouse away, it should also end it. I realize it's not trivial to solve, since the task is a one-time action, and has no notion of the mouse entering and leaving the screen corner. Maybe, a few of such simple actions should be pre-defined for linking to the screen corners (without being separately defined as a task), and this predefined thing should behave as I wrote.
This is done by design. The way it currently works is: you put the mouse in the correct corner and ShellEnhancer starts blocking. When you put the mouse a second time in the corner, blocking stops. It allows you to quickly start blocking the screensaver and still do some work like starting a process (for example: a backup). Afterwards, just put the mouse back in the corner and blocking stops.
Don't you think this is more usefull than a block when mouse enters and stop blocking when mouse leaves?
I'll think about adding some predefined corner tasks.

mortee wrote:The window rollup function is really nice, as well as the option to roll them down on mouse over. However, if both are enabled, then as soon as the user rolls up a window, it rolls down again in a second (because you have to go over the title bar to roll it up anyway). So I suggest to disable auto-rolldown until the mouse left the titlebar for the first time after rolling up the window.
Nice suggestion, i'll add it to the todo list.

mortee wrote:Keep up the good work! I'm sure I'll have a few more suggestions as I play around with the app.
All suggestions are welcome ;)
Marc Gregoire,
NuonSoft
[ Microsoft MVP VC++ since 2007 ]
User avatar
Marc G
NuonSoft Staff
 
Posts: 818
Joined: Thu Nov 07, 2002 8:19 pm
Location: Belgium

Re: window-specific tasks, delay in window fadeout, etc.

Postby mortee » Mon Jul 12, 2004 10:10 am

Marc G wrote:This is done by design. The way it currently works is: you put the mouse in the correct corner and ShellEnhancer starts blocking. When you put the mouse a second time in the corner, blocking stops. It allows you to quickly start blocking the screensaver and still do some work like starting a process (for example: a backup). Afterwards, just put the mouse back in the corner and blocking stops.
Don't you think this is more usefull than a block when mouse enters and stop blocking when mouse leaves?

It does turn screensaver-blocking off when I move the mouse in the corner next time? I didn't notice that. If it's so, then it's all good (:
User avatar
mortee
 
Posts: 28
Joined: Mon Jul 12, 2004 8:31 am

Postby Marc G » Mon Jul 12, 2004 10:13 am

Yes it works that way because the "Block screensaving" command is a toggle-command.
Marc Gregoire,
NuonSoft
[ Microsoft MVP VC++ since 2007 ]
User avatar
Marc G
NuonSoft Staff
 
Posts: 818
Joined: Thu Nov 07, 2002 8:19 pm
Location: Belgium

Postby mortee » Mon Jul 12, 2004 2:48 pm

Actually, as I thought about this screensaver blocking thing, I concluded that I still preferred it the other way. After all, screensaver only activates when the user doesn't do anything, so blocking it is only meaningful if the user is idle. Thus, if you want to start a backup or anything, you can do it, the screensaver won't be triggered anyway. And when you want to leave the machine with the screensaver blocked, you just drag and leave the mouse in the hot corner. So, having it in trigger mode (at least when activated by a hot screen corner) doesn't make any sense. And the other way around, which automatically stops blocking when you move the mouse away, is just much simpler.

(That said, I have a little utility which provides this kind of screensaver blocking; and since I'd keep it anyway, because it does other useful things too, it's not really important to me to have this done in ShellEnhancer... :)
User avatar
mortee
 
Posts: 28
Joined: Mon Jul 12, 2004 8:31 am

Postby Marc G » Mon Jul 12, 2004 3:01 pm

yes, you are right, it is more intuitive to unblock when leaving the corner.
I'll might add this to a future release.
Marc Gregoire,
NuonSoft
[ Microsoft MVP VC++ since 2007 ]
User avatar
Marc G
NuonSoft Staff
 
Posts: 818
Joined: Thu Nov 07, 2002 8:19 pm
Location: Belgium

Re: window-specific tasks, delay in window fadeout, etc.

Postby Guest » Mon Jul 12, 2004 4:01 pm

mortee wrote:Hi! I just found your utility referred from betanews.com, I installed it, and really like what I've seen sofar. I'd have a few comments though. First, it'd be nice if one could create window-specific tasks. That is, activate/enable the given task only if the specified app or window is in the foreground. It'd be the simplest to have a popup menu on the task dialog, with the available automanaged windows (along with an item to define a new one...) Also, it'd be nice if there would be a slight delay between the mouse going over the window-border-buttons and the window becoming transparent (if it's enabled at all). I find it very useful to have a fast and intuitive way to make a window temporarily transparent, but it's really disturbing if it immediately goes transparent, even if I just want to close it. Also, I don't know if it's possible, but the button in question should be kept opaque, while the rest of the window made transparent (it's quite inconvenient that the very button you're going to click almost entirely disappears...) Also related to transparency (and I also don't know if it's possible), the enhanced task switcher should not be uniformly transparent - only the background, and the contents (icons, labels, preview) should be opaque. I like the possibility to block the screensaver from a task, but enabling this from a screen corner should somehow be streamlined a bit. Currently, if I link a screen corner to blocking the screen saver, then it *starts* blocking, but when I move the mouse away, it should also end it. I realize it's not trivial to solve, since the task is a one-time action, and has no notion of the mouse entering and leaving the screen corner. Maybe, a few of such simple actions should be pre-defined for linking to the screen corners (without being separately defined as a task), and this predefined thing should behave as I wrote. The window rollup function is really nice, as well as the option to roll them down on mouse over. However, if both are enabled, then as soon as the user rolls up a window, it rolls down again in a second (because you have to go over the title bar to roll it up anyway). So I suggest to disable auto-rolldown until the mouse left the titlebar for the first time after rolling up the window. Keep up the good work! I'm sure I'll have a few more suggestions as I play around with the app.
Guest
 

Re: window-specific tasks, delay in window fadeout, etc.

Postby Guest » Mon Jul 12, 2004 4:01 pm

Marc G wrote:
mortee wrote:Hi! I just found your utility referred from betanews.com, I installed it, and really like what I've seen sofar.
:D
mortee wrote:I'd have a few comments though. First, it'd be nice if one could create window-specific tasks. That is, activate/enable the given task only if the specified app or window is in the foreground. It'd be the simplest to have a popup menu on the task dialog, with the available automanaged windows (along with an item to define a new one...)
Nice idea, i'll add it to the todo list.
mortee wrote:Also, it'd be nice if there would be a slight delay between the mouse going over the window-border-buttons and the window becoming transparent (if it's enabled at all). I find it very useful to have a fast and intuitive way to make a window temporarily transparent, but it's really disturbing if it immediately goes transparent, even if I just want to close it. Also, I don't know if it's possible, but the button in question should be kept opaque, while the rest of the window made transparent (it's quite inconvenient that the very button you're going to click almost entirely disappears...)
I'll add a user-defineable delay for the window-buttons-transparency. I'm not sure if it is possible to keep the window-button opaque because ShellEnhancer doesn't 'own' the window, but i'll take a look at it.
mortee wrote:Also related to transparency (and I also don't know if it's possible), the enhanced task switcher should not be uniformly transparent - only the background, and the contents (icons, labels, preview) should be opaque.
This might be possible (i'm not sure). I'll give it a try.
mortee wrote:I like the possibility to block the screensaver from a task, but enabling this from a screen corner should somehow be streamlined a bit. Currently, if I link a screen corner to blocking the screen saver, then it *starts* blocking, but when I move the mouse away, it should also end it. I realize it's not trivial to solve, since the task is a one-time action, and has no notion of the mouse entering and leaving the screen corner. Maybe, a few of such simple actions should be pre-defined for linking to the screen corners (without being separately defined as a task), and this predefined thing should behave as I wrote.
This is done by design. The way it currently works is: you put the mouse in the correct corner and ShellEnhancer starts blocking. When you put the mouse a second time in the corner, blocking stops. It allows you to quickly start blocking the screensaver and still do some work like starting a process (for example: a backup). Afterwards, just put the mouse back in the corner and blocking stops. Don't you think this is more usefull than a block when mouse enters and stop blocking when mouse leaves? I'll think about adding some predefined corner tasks.
mortee wrote:The window rollup function is really nice, as well as the option to roll them down on mouse over. However, if both are enabled, then as soon as the user rolls up a window, it rolls down again in a second (because you have to go over the title bar to roll it up anyway). So I suggest to disable auto-rolldown until the mouse left the titlebar for the first time after rolling up the window.
Nice suggestion, i'll add it to the todo list.
mortee wrote:Keep up the good work! I'm sure I'll have a few more suggestions as I play around with the app.
All suggestions are welcome ;)
Guest
 

Re: window-specific tasks, delay in window fadeout, etc.

Postby Guest » Mon Jul 12, 2004 4:02 pm

mortee wrote:
Marc G wrote:This is done by design. The way it currently works is: you put the mouse in the correct corner and ShellEnhancer starts blocking. When you put the mouse a second time in the corner, blocking stops. It allows you to quickly start blocking the screensaver and still do some work like starting a process (for example: a backup). Afterwards, just put the mouse back in the corner and blocking stops. Don't you think this is more usefull than a block when mouse enters and stop blocking when mouse leaves?
It does turn screensaver-blocking off when I move the mouse in the corner next time? I didn't notice that. If it's so, then it's all good (:
Guest
 

Postby Guest » Mon Jul 12, 2004 4:03 pm

Marc G wrote:Yes it works that way because the "Block screensaving" command is a toggle-command.
Guest
 

Postby Guest » Mon Jul 12, 2004 4:03 pm

mortee wrote:Actually, as I thought about this screensaver blocking thing, I concluded that I still preferred it the other way. After all, screensaver only activates when the user doesn't do anything, so blocking it is only meaningful if the user is idle. Thus, if you want to start a backup or anything, you can do it, the screensaver won't be triggered anyway. And when you want to leave the machine with the screensaver blocked, you just drag and leave the mouse in the hot corner. So, having it in trigger mode (at least when activated by a hot screen corner) doesn't make any sense. And the other way around, which automatically stops blocking when you move the mouse away, is just much simpler. (That said, I have a little utility which provides this kind of screensaver blocking; and since I'd keep it anyway, because it does other useful things too, it's not really important to me to have this done in ShellEnhancer... :)
Guest
 

Postby Guest » Mon Jul 12, 2004 4:04 pm

Marc G wrote:yes, you are right, it is more intuitive to unblock when leaving the corner. I'll might add this to a future release.
Guest
 

Postby Marc G » Mon Jul 12, 2004 4:17 pm

:?
If you want to post a reply, click on the "Post Reply" button at the bottom of the page.
Marc Gregoire,
NuonSoft
[ Microsoft MVP VC++ since 2007 ]
User avatar
Marc G
NuonSoft Staff
 
Posts: 818
Joined: Thu Nov 07, 2002 8:19 pm
Location: Belgium


Return to SE - Wishlist

Who is online

Users browsing this forum: No registered users and 2 guests

cron