From: senn on

"Karl E. Peterson" <karl(a)exmvps.org> skrev i meddelelsen
news:%234DtySA3KHA.4540(a)TK2MSFTNGP04.phx.gbl...
> Steve Rindsberg wrote:
>> In article <ufVSce22KHA.5820(a)TK2MSFTNGP06.phx.gbl>, Karl E. Peterson
>> wrote:
>>> Steve Rindsberg wrote:
>>>> [snippedy-doodah snippedy-yay]
>>>>
>>>>>> Hm. Use VMWare instead? ;-)
>>>>>
>>>>> Does it have the seamless operation?
>>>>
>>>> Unless you beat it pretty good, it's not even aware of the extended
>>>> desktop. The copy of Windows running inside it is restricted to the
>>>> VMware window (which can be full screen on one or another of the
>>>> monitors). For example, if you doubleclick the title bar of the
>>>> VMWare app, it expands to fill whichever monitor it's *mostly* on; it
>>>> doesn't try to fill both monitors (ie, the expanded desktop). If you
>>>> want it to do that, you'd make the app less than maximized then
>>>> manually drag and size it to the desired shape/size.
>>>
>>> Okay, that sounds a whole like running ordinary VirtualPC VMs. They've
>>> actually done something kind of crazy with what they now call "Windows
>>> Virtual PC" that can be added onto non-consumer versions of Windows 7.
>>> It makes it appear the software running in an XP VM is actually running
>>> on Windows 7. But it fails to pass along the separate monitor
>>> information. It's very cool, and at times very frustrating. Funny how
>>> that goes, huh?
>>
>> AKA Version 1 bug? ;-)
>
> I'd like to think, yeah. But given the difficulty I've had describing it,
> I wonder if it's risen to anyone's attention yet.
>
>> Been meaning to ask, though: got URL? Where do you download this pup?
>
> http://www.microsoft.com/windows/virtual-pc/
>
> Once you get an "XP Mode" VM running, anything you put in the "All Users"
> start menu will show up in your host Windows 7 start menu, under the
> VirtualPC group, and can be fired up as you would any other "native"
> application. If the VM isn't already running, that starts up (in the
> background, unseen) first. The "seamless" app just runs as would any
> other, except that it's XP themed rather than all Aero'd out. <g>
>
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
>
>

> that starts up
> (in the background, unseen)
You feel the minutes don't you? <g>.
/se

From: Robert Comer on
I very much understand what you mean, but I think WVPC would have to be
multiple monitor aware (and assignable to specific monitors) for you to get
what you want, and I'm afraid that's not the case. You can cheat by not
using full screen mode and just sizing the window correctly I would think...

I wonder if RAIL has this problem independent of WVPC...

--
Bob Comer


"Karl E. Peterson" <karl(a)exmvps.org> wrote in message
news:ue8AwXA3KHA.3844(a)TK2MSFTNGP05.phx.gbl...
> Robert Comer wrote:
>>> Okay, that's good to know. So we're left just waiting for MSFT to
>>> accurately pass the monitor metrics through to the guest VM, then. :-(
>>
>> I wouldn't know, I never use extended desktop like that, however I don't
>> think it's passing parameter that's the problem, it's probably the
>> drawing technology. In VPC2007 it was a directdraw problem, but I don't
>> know about WVPC.
>
> I could find out definitely enough, I guess, by just writing up a quick
> little monitor enumeration applet and running it in that mode. But I
> think, from the time I've spent working with the monitor API, that it's
> pretty clear what's happening. The seamless apps are simply being told
> there's one monitor, and its dimensions are given as that of the entire
> virtual monitor which is the accumulamulated area of all physical monitors
> combined.
>
> IOW, say you have two monitors, side by side. Both running at 1280x1024,
> with the 0,0 point at the upper-left of monitor 1, which is on the left.
> The coordinate space for the twp physical displays would be something
> like:
>
> 0,0 1279,0 1280,0 2559,0
>
> *1* *2*
>
> 0,1023 1279,1023 1280,1023 2559,1023
>
> (Hope you have a fixed-width font! <g>)
>
> But monitor "0" is the virtual display, that covers the whole thing. It's
> coordinates would be:
>
> 0,0 2559,0
>
> *0*
>
> 0,1023 2559,1023
>
> That's the one being given to the seamless apps, when they inquire about
> monitor dimensions. This also explains why their popup dialogs (msgbox's,
> etc) so often appear split between the two monitors. They're simply
> centering themselves on what they see as "the" monitor.
>
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
>
>
From: Robert Comer on
Just saw a workaround in the WVPC forum, make your main monitor the
rightmost monitor in the resolution settings and your seamless app will no
longer span both monitors.

--
Bob Comer

"Karl E. Peterson" <karl(a)exmvps.org> wrote in message
news:ue8AwXA3KHA.3844(a)TK2MSFTNGP05.phx.gbl...
> Robert Comer wrote:
>>> Okay, that's good to know. So we're left just waiting for MSFT to
>>> accurately pass the monitor metrics through to the guest VM, then. :-(
>>
>> I wouldn't know, I never use extended desktop like that, however I don't
>> think it's passing parameter that's the problem, it's probably the
>> drawing technology. In VPC2007 it was a directdraw problem, but I don't
>> know about WVPC.
>
> I could find out definitely enough, I guess, by just writing up a quick
> little monitor enumeration applet and running it in that mode. But I
> think, from the time I've spent working with the monitor API, that it's
> pretty clear what's happening. The seamless apps are simply being told
> there's one monitor, and its dimensions are given as that of the entire
> virtual monitor which is the accumulamulated area of all physical monitors
> combined.
>
> IOW, say you have two monitors, side by side. Both running at 1280x1024,
> with the 0,0 point at the upper-left of monitor 1, which is on the left.
> The coordinate space for the twp physical displays would be something
> like:
>
> 0,0 1279,0 1280,0 2559,0
>
> *1* *2*
>
> 0,1023 1279,1023 1280,1023 2559,1023
>
> (Hope you have a fixed-width font! <g>)
>
> But monitor "0" is the virtual display, that covers the whole thing. It's
> coordinates would be:
>
> 0,0 2559,0
>
> *0*
>
> 0,1023 2559,1023
>
> That's the one being given to the seamless apps, when they inquire about
> monitor dimensions. This also explains why their popup dialogs (msgbox's,
> etc) so often appear split between the two monitors. They're simply
> centering themselves on what they see as "the" monitor.
>
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
>
>
From: Steve Rindsberg on
Thanks ...

Not sure what I'll use it for, but something will come up, no doubt.
<g>

==============================
PPT Frequently Asked Questions
http://www.pptfaq.com/

PPTools add-ins for PowerPoint
http://www.pptools.com/


From: Karl E. Peterson on
Robert Comer wrote:
> I very much understand what you mean, but I think WVPC would have to be
> multiple monitor aware (and assignable to specific monitors) for you to get
> what you want, and I'm afraid that's not the case.

Yeah, the more I thought about it last night, that realization dawned
on me. That would definitely seem to be the better enhancement
request, but I'm guessing the odds of that are pretty darned low, huh?

> You can cheat by not
> using full screen mode and just sizing the window correctly I would think...

That works well, except with apps that decide for themselves. Like
PowerPoint in slideshow mode. I'm going to try Chirag's add-in, and
see how that goes, though.

> I wonder if RAIL has this problem independent of WVPC...

Whazzat?

--
..NET: It's About Trust!
http://vfred.mvps.org