Dual Monitor Problem

[Brak]

Hello,

I am trying to run VFP 5.0 on a dual monitor system.

If I drag the program onto the secondary monitor I lose the ability to click on anything. I can't click in the command box, I can click on the menu.

What is going on, and is there a fix for it?

Thanks in advance.


B"H
Brak

 

[craigber]

VFP 5.0 does not support dual monitors.

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[Brak]

Why is that?

Shouldn't they release a patch to fix this?

The programs I make using Borland C++ 4.5 (ca 1994) work fine on both monitors.

Every program I have regardless of when it was made (even Win3.1) work on both monitors just fine.

The only one with an issue is Fox. Why is that?

Its very frustraiting as when I try to use fox, or a program compile by fox, it can only work on the primary monitor.

And in a world which multi-monitor setups are becoming common place, it really decreases the value of the programs you make with it.

So what can be done?

 

[craigber]

Yes, there is a fix...it's called an upgrade. It works fine in 9.0

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[Brak]

But someone should have't to pay MS for the patch to a bug in their product.

Since 5.0 has this flaw, they should release a free patch/upgrade. Not require people to buy the program a second time in order to recieve the fix.

And again, why does only FP have this problem? The 16-bit apps I make with a win31 C compiler work perfectly. But here is a 32bit app and it doesn't work!

They really should have a service patch for this issue.

Just my 2 cents.

 

[Mike Lewis]

Brak,

I sympathise with your frustration, but I'm not sure I agree.

Is the lack of dual-monitor support really a bug? Is it something that is provided at the operating system level, and which all applications are expected to support, or is it a feature that an application must explicitly impliment?

Even if it is a bug, I'm not sure that it's reasonable to expect Microsoft to issue a fix for products or versions they no longer support. Like you, I object to having to pay a vendor to correct their mistakes. But Microsoft never claimed that VFP was bug-free.

I'd be interested in hearing what other folk think.

Mike



__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[wgcs]

I think it's unreasonable to expect a patch for VFP5 now...

What OS are you running VFP5 on, Brak? If WinXP, I don't think that XP was released before MS stopped supporting VFP5.

As to all the other programs working, and not VFP, that is irritating, but I think it has to do with VFP's window management. In v5, particularly, the internal VFP controls did not have window handles.. much of the screen painting/input (mouse) handling is handled by VFP's internal window manager due to it's cross-platform (Dos/Mac/Unix/Win) design. It seems that newer VFP's are getting more tightly bound to windows in architecture (and seem "better" because of it: each window has an .hwnd property... we can bind events to window's Window Events... we can interact with OLE drag-and-drop... etc)...

PLUS, as reported, the latest VFP works fine with Dual Monitors: MS isn't going to do anything for vfp5.

- Bill

Get the best answers to your questions -- See FAQ481-4875.