On Wed, Apr 9, 2008 at 7:08 PM, Mike Driscoll wrote"
> You can turn it off by right-clicking the
> "Start" button, going to Properties, and choosing the "Taskbar" tab. Uncheck
> the "Group similar taskbar buttons" checkbox and it will no longer group
> them together.
Yes, but my point was: how do you stop disable this functionality
using Python? There might be some way using ctypes of win32all which
allows you to do that, but I don't know how to do it. And anyway, that
should be a user choice, not a programmer one.
That is EXACTLY right. There is, in fact, a simple registry hack that will enable/disable the grouping feature, but it's not up to you or your application to decide whether or not I want grouping on my taskbar. That's my personal preference. Don't change my desktop colors, don't change my screen size, don't change my default fonts, and don't change my desktop preferences.
> I don't know why py2exe would stop the grouping effect. To
> me, it should work unless your frames are created using subprocess. But I
> think you'd need at least 4 frames before the grouping would take place.
What I meant is that, once you compile your app into an executable, it
will not group together your app with the wxPython demo, for example,
as Paul mentioned in his e-mail. That's because your compiled app is
no more a "pure" python GUI but a standalone exe process.
Well, that's not really the reason. The reason is that the "grouping" decision is made based on the name of the executable for the process. For the typical .pyw script, the executable is "pythonw.exe", and anything started by that executable will be grouped. When you use py2exe, the executable is your combined exe name, so it will no longer be grouped with "pythonw.exe".
···
On Wed, 9 Apr 2008 22:36:07 +0100, "Andrea Gavana" <andrea.gavana@gmail.com> wrote:
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.