I hope the good AHK team is working on a way to work efficiently with Windows 10's virtual desktops. Detect how many are open. Close them with a single command. Open. Maybe switch through them, all without using the hotkeys. Also, finding windows in other desktops if you want. Hopefully to specify whether or not you want to look among other desktops. Something like "SetDesktopSearchMode"?
Also, could you somehow have a way to open a program in a new desktop? I don't know if that is possible, or if Microsoft will come up with something like that eventually.
All this would be pretty much possible without being built in, but just an idea for reliability, etc. Maybe it'll be a big project that'll take till windows 12!!!
-Derek
Windows 10 virtual desktops
Windows 10 virtual desktops
try it and see
...
...
-
- Posts: 7
- Joined: 25 May 2016, 17:13
Re: Windows 10 virtual desktops
+1 !derz00 wrote:I hope the good AHK team is working on a way to work efficiently with Windows 10's virtual desktops. Detect how many are open.
Please if someone has a solution for this, it would help a lot and permit programming anything
Re: Windows 10 virtual desktops
What team? There's no team of developers, just myself and sometimes other independent contributors.
I don't use Windows 10's virtual desktops, so it doesn't interest me.
Here's a starting point (requires an understanding of COM interfaces): IVirtualDesktopManager interface. Also search the forum for "IVirtualDesktopManager" as some code has already been written.
I don't use Windows 10's virtual desktops, so it doesn't interest me.
Here's a starting point (requires an understanding of COM interfaces): IVirtualDesktopManager interface. Also search the forum for "IVirtualDesktopManager" as some code has already been written.
Re: Windows 10 virtual desktops
so lexikos is working alone...
I'm wondering why noone co-operate with you why you don't make a big development team?
how hard is working alone to release updates ?
I'm curious I mean what the hell only you ?
you said (I don't use Windows 10's virtual desktops, so it doesn't interest me.)
Bcause you don't use virtual desktops means that no one use them too?
you really need a team.
you own a language which is realeased to the public and I think that you are pretty negative to users.
and you are right you are alone is hard to make changes fast requires a lot of work.I don't know though how much work requires as I'm not expert and I also don't have knowledge about that
I'm wondering why noone co-operate with you why you don't make a big development team?
how hard is working alone to release updates ?
I'm curious I mean what the hell only you ?
you said (I don't use Windows 10's virtual desktops, so it doesn't interest me.)
Bcause you don't use virtual desktops means that no one use them too?
you really need a team.
you own a language which is realeased to the public and I think that you are pretty negative to users.
and you are right you are alone is hard to make changes fast requires a lot of work.I don't know though how much work requires as I'm not expert and I also don't have knowledge about that
Re: Windows 10 virtual desktops
Development isn't that easy, it takes time!
Even when you have a whole team :/
Usually, when it can be done say using COM or Dllcall, there's no "necessity" to add it into AutoHotkey.
I wouldn't lexikos is negative, just very critical. He wants things to be there for a good reason (usually that cant be done too well with libraries) and high but respectable standards.
Don't worry, if you really need this. You can always post in the help forums, someone might even write a library
However, I must say that it's an interesting idea!
Even when you have a whole team :/
Usually, when it can be done say using COM or Dllcall, there's no "necessity" to add it into AutoHotkey.
I wouldn't lexikos is negative, just very critical. He wants things to be there for a good reason (usually that cant be done too well with libraries) and high but respectable standards.
Don't worry, if you really need this. You can always post in the help forums, someone might even write a library
However, I must say that it's an interesting idea!
Windows 10 x64 Professional, Intel i5-8500, NVIDIA GTX 1060 6GB, 2x16GB Kingston FURY Beast - DDR4 3200 MHz | [About Me] | [About the AHK Foundation] | [Courses on AutoHotkey]
[ASPDM - StdLib Distribution] | [Qonsole - Quake-like console emulator] | [LibCon - Autohotkey Console Library]
Re: Windows 10 virtual desktops
The interface to manipulate virtual desktops like the Task View does, IVirtualDesktopManagerInternal, is, as its name implies, undocumented (credits to NickoTin and Grabacr07 for actually reversing it), not meant for public use and subject to change at any time. Hardly makes a top candidate for inclusion. Plus, AutoHotkey gives you the flexibility to do the work yourself.
With the exception of searching desktops for applications and starting apps on another desktop (the only ways to do that are a little messy: switch to the new desktop first and then start the application, or hook into the process so that you can call the MoveWindowToDesktop method [or whatever it's called]), everything listed in derz00's post can be done easily (with the caveat your scripts may break come the next Windows 10 upgrade, 'cause undocumented interface).
Like joedf says, just post in the help forums saying what you actually want. If I, or one of the many other people on this forum that are good at using COM (I've had many of my misconceptions cleared up by posting in AFH), can help, you'll get an answer.
I've already posted code on here that uses the undocumented interface to switch desktops and add a new one, and I have AutoHotkey code out there that uses IVirtualNotificationService to update a tray icon with the current virtual desktop number when it's changed (which I repurposed for somebody wanting to change Wi-Fi networks when the current virtual desktop was changed). (I won't write a library, personally, as I wouldn't be interested in maintaining one for a feature I don't use, and knowing how inept I can be, I'd probably have to break its API 20 times to get something simple that actually serves others' needs.)
With the exception of searching desktops for applications and starting apps on another desktop (the only ways to do that are a little messy: switch to the new desktop first and then start the application, or hook into the process so that you can call the MoveWindowToDesktop method [or whatever it's called]), everything listed in derz00's post can be done easily (with the caveat your scripts may break come the next Windows 10 upgrade, 'cause undocumented interface).
Like joedf says, just post in the help forums saying what you actually want. If I, or one of the many other people on this forum that are good at using COM (I've had many of my misconceptions cleared up by posting in AFH), can help, you'll get an answer.
I've already posted code on here that uses the undocumented interface to switch desktops and add a new one, and I have AutoHotkey code out there that uses IVirtualNotificationService to update a tray icon with the current virtual desktop number when it's changed (which I repurposed for somebody wanting to change Wi-Fi networks when the current virtual desktop was changed). (I won't write a library, personally, as I wouldn't be interested in maintaining one for a feature I don't use, and knowing how inept I can be, I'd probably have to break its API 20 times to get something simple that actually serves others' needs.)
Who is online
Users browsing this forum: No registered users and 36 guests