Hello,
I've been using Dexpot for a while now, lately I encountered a problem which I cannot fathom the reason for. I have 10 virtual desktops, desktop 8 is for my programming apps. Whenever I open MonoDevelop, or Visual Studio (2010 or 2012) they instantly get switched to desktop 5 (my gaming workspace). Yet when I switch to that workspace, whenever I click a menu item, the app gets shifted back to desktop 8 again!
I'm baffled as I have assigned MonoDevelop and Visual Studio to desktop 8 and also have a rule in place to move them there if devenv or mono or contained in the exe filename.
Why are these apps being moved to the wrong desktop? I've checked my assignments and rules, they're all fine. Would appreciate any insight into what may be the cause of this, I'm rather stumped!
Issues with apps switching to incorrect desktops
Re: Issues with apps switching to incorrect desktops

Disable all rules for testing. If the problem still occurs, enable the Dexpot log file, restart Dexpot, reproduce the problem and send me the log.
Re: Issues with apps switching to incorrect desktops
That seems to have done the trick, the rules I had were:
Gaming (Desktop 5):
Programming & Development (Desktop 8):
Any ideas what may have caused the issue? The rules seem fine to me.
Gaming (Desktop 5):
Code: Select all
Executable contains desura
or Executable contains eve
or Executable contains steam
or Executable contains worldoftanks
or Executable contains ts3client
Code: Select all
Move to desktop 5Programming & Development (Desktop 8):
Code: Select all
Executable contains mono
or Executable contains devenv
Code: Select all
Move to desktop 8Any ideas what may have caused the issue? The rules seem fine to me.
Re: Issues with apps switching to incorrect desktops
The problem is that devenv contains eve. 
Change the rule conditions to the form "executable is devenv.exe" to avoid the issue. Also, in general it shouldn't be necessary to create rules like this when you're already using "Assign applications".
Change the rule conditions to the form "executable is devenv.exe" to avoid the issue. Also, in general it shouldn't be necessary to create rules like this when you're already using "Assign applications".
Who is online
Users browsing this forum: No registered users and 24 guests