Hi, Simon. I am a new user. I just installed version 2.2.1.0. The program correctly switches desktops and is able to move windows to other desktops. But it fails to move new Word documents back to the current desktop. I does not move new Chrome pages back to the current desktop either.
The user manual says to adjust the value of MoveOnNewWindowDetectTimeoutMs. That value is not in the settings file. I manually added an entry for it and saved the file, but when I later saved the settings from the program, it blew away that setting. My guess is that you have removed that setting and that the user manual is out of date.
Do you have any suggestions how to get the automatic switching of new Word documents back to the current desktop to work on my PC? That was the reason I installed this software.
Thanks.
Ken
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right I did remove that setting for some reason. It was a while
back and I don't remember why exactly. I did increase it from 500ms
default to a fixed 1200ms but also changed slightly how it does this.
What version of office / word do you have? One thing to check is that
the executable name is WINWORD.EXE in upper case. If not change that
setting in the file.
For chrome it doesn't move it to the current desktop but if you have a
chrome window it opens in that window (new tab) as opposed to the last
window used on whatever desktop that was on.
Simon
On Sun, Apr 30, 2017, at 12:49 AM, Ken Williams wrote:
Hi, Simon. I am a new user. I just installed version 2.2.1.0. The
program correctly switches desktops and is able to move windows to
other desktops. But it fails to move new Word documents back to the
current desktop. I does not move new Chrome pages back to the current
desktop either.> The user manual says to adjust the value of
MoveOnNewWindowDetectTimeoutMs. That value is not in the settings
file. I manually added an entry for it and saved the file, but when I
later saved the settings from the program, it blew away that setting.
My guess is that you have removed that setting and that the user
manual is out of date.> Do you have any suggestions how to get the automatic switching of new
Word documents back to the current desktop to work on my PC? That was
the reason I installed this software.> Thanks.
That was helpful. I am using Office 2013. My winword is called winword.exe (lower case), so I changed that in the settings file. Now VirtualDesktopGrid works about a third of the time on Word files. I have an older PC and 1200 ms is barely long enough for it to open a small Word document. It is entirely too short if I try to open a large Word document. If you would put the MoveOnNewWindowDetectTimeoutMs setting back in, I believe I could adjust it to make it quite useful for me. As it is right now I cannot really use it for Word.
For Excel (which strangely enough is called EXCEL.EXE -- uppercase), I found that Excel's behavior without VirtualDesktopGrid running was already correct. It opens a spreadsheet on my current window. With VirtualDesktopGrid running, it gets messed up and opens it up on the wrong desktop! But that was easy to fix. I simply deleted EXCEL.EXE from the settings file.
Your explanation of how it behaves with Chrome was just what I needed to know. That works correctly for me. I suggest that you add that explanation to the help file, because I would have never figured it out on my own.
Ken
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I'll add the timeout setting back in and I'll change executable name
matching so that case doesn't matter. Should be within the next week.
Simon
Thanks, Simon.
That was helpful. I am using Office 2013. My winword is called winword.exe
(lower case), so I changed that in the settings file. Now
VirtualDesktopGrid works about a third of the time on Word files. I have an
older PC and 1200 ms is barely long enough for it to open a small Word
document. It is entirely too short if I try to open a large Word document.
If you would put the MoveOnNewWindowDetectTimeoutMs setting back in, I
believe I could adjust it to make it quite useful for me. As it is right
now I cannot really use it for Word.
For Excel (which strangely enough is called EXCEL.EXE -- uppercase), I
found that Excel's behavior without VirtualDesktopGrid running was already
correct. It opens a spreadsheet on my current window. With
VirtualDesktopGrid running, it gets messed up and opens it up on the wrong
desktop! But that was easy to fix. I simply deleted EXCEL.EXE from the
settings file.
Your explanation of how it behaves with Chrome was just what I needed to
know. That works correctly for me. I suggest that you add that explanation
to the help file, because I would have never figured it out on my own.
Ken
Cannot get automatic window move to work
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/virtual-desktop-grid-switcher/discussion/general/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Regarding Excel, I also have Office 2013 (Professional Plus) and it doesn't work without VDGS if you have a spreadsheet open on another desktop.
I do have 2007 on another machine and in that case VDGS moves the wrong document to the new desktop and then somehow that window becomes sticky./ visible on all desktopns (but not the way this is done in VDGS) :-(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, Simon. I am a new user. I just installed version 2.2.1.0. The program correctly switches desktops and is able to move windows to other desktops. But it fails to move new Word documents back to the current desktop. I does not move new Chrome pages back to the current desktop either.
The user manual says to adjust the value of MoveOnNewWindowDetectTimeoutMs. That value is not in the settings file. I manually added an entry for it and saved the file, but when I later saved the settings from the program, it blew away that setting. My guess is that you have removed that setting and that the user manual is out of date.
Do you have any suggestions how to get the automatic switching of new Word documents back to the current desktop to work on my PC? That was the reason I installed this software.
Thanks.
Ken
Hi Ken,
You are right I did remove that setting for some reason. It was a while
back and I don't remember why exactly. I did increase it from 500ms
default to a fixed 1200ms but also changed slightly how it does this.
What version of office / word do you have? One thing to check is that
the executable name is WINWORD.EXE in upper case. If not change that
setting in the file.
For chrome it doesn't move it to the current desktop but if you have a
chrome window it opens in that window (new tab) as opposed to the last
window used on whatever desktop that was on.
Simon
On Sun, Apr 30, 2017, at 12:49 AM, Ken Williams wrote:
Links:
Thanks, Simon.
That was helpful. I am using Office 2013. My winword is called winword.exe (lower case), so I changed that in the settings file. Now VirtualDesktopGrid works about a third of the time on Word files. I have an older PC and 1200 ms is barely long enough for it to open a small Word document. It is entirely too short if I try to open a large Word document. If you would put the MoveOnNewWindowDetectTimeoutMs setting back in, I believe I could adjust it to make it quite useful for me. As it is right now I cannot really use it for Word.
For Excel (which strangely enough is called EXCEL.EXE -- uppercase), I found that Excel's behavior without VirtualDesktopGrid running was already correct. It opens a spreadsheet on my current window. With VirtualDesktopGrid running, it gets messed up and opens it up on the wrong desktop! But that was easy to fix. I simply deleted EXCEL.EXE from the settings file.
Your explanation of how it behaves with Chrome was just what I needed to know. That works correctly for me. I suggest that you add that explanation to the help file, because I would have never figured it out on my own.
Ken
Great feedback, thanks Ken.
Yes, I'll add the timeout setting back in and I'll change executable name
matching so that case doesn't matter. Should be within the next week.
Simon
Thanks, Simon.
That was helpful. I am using Office 2013. My winword is called winword.exe
(lower case), so I changed that in the settings file. Now
VirtualDesktopGrid works about a third of the time on Word files. I have an
older PC and 1200 ms is barely long enough for it to open a small Word
document. It is entirely too short if I try to open a large Word document.
If you would put the MoveOnNewWindowDetectTimeoutMs setting back in, I
believe I could adjust it to make it quite useful for me. As it is right
now I cannot really use it for Word.
For Excel (which strangely enough is called EXCEL.EXE -- uppercase), I
found that Excel's behavior without VirtualDesktopGrid running was already
correct. It opens a spreadsheet on my current window. With
VirtualDesktopGrid running, it gets messed up and opens it up on the wrong
desktop! But that was easy to fix. I simply deleted EXCEL.EXE from the
settings file.
Your explanation of how it behaves with Chrome was just what I needed to
know. That works correctly for me. I suggest that you add that explanation
to the help file, because I would have never figured it out on my own.
Ken
Cannot get automatic window move to work
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/virtual-desktop-grid-switcher/discussion/general/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
New version is up and documentation updated as you suggested :-)
Regarding Excel, I also have Office 2013 (Professional Plus) and it doesn't work without VDGS if you have a spreadsheet open on another desktop.
I do have 2007 on another machine and in that case VDGS moves the wrong document to the new desktop and then somehow that window becomes sticky./ visible on all desktopns (but not the way this is done in VDGS) :-(
Thanks very much, Simon!
I have tried out the new version. So far it does everything I want!
Ken
Hey, thanks for the review Ken :-)