Hi Jean Maurice!
This sounds pretty much like exactly what I was after. I'd appreciate it
very much if you could send it along either to FoxPro or to my email
address at b...@cogeco.ca.
Thanks, again!
Bill
On 2015-03-07 12:56 AM, Jean MAURICE wrote:
Hi William,
as I am an old foxer, I
William, I use a different resize but probably follows the same principle
I declare 2 public variables in my main.prg
PUBLIC trheight
PUBLIC trwidth
If the system leaves the main screen I set the trheight and trwidth
variables
On any screen/form where I want to scale the screen, I INIT
William Pew wrote on 2015-03-06:
Hi Tracy!
Thanks for the quick reply. Actually what I'm trying to do is 'automate'
a feature that's already built into mwresize. If you right click the
resizer tab in the bottom right hand corner of the form mwresize pops
up a small menu of choices
William Pew wrote on 2015-03-06:
Hello, again!
Here we go with yet another resizer question.
I have not been able to find a drop in automatic resizer to handle
screen resolution differences among computers. If anyone knows of one
I'd be very interested - problem solved.
Hi William,
as I am an old foxer, I began to design form in 800*600 and with mwresize they
match screen resolution automatically but it is not always beautiful :
things can become too big. Si I have modified Markus'class to limit the 'growing
ratio'.
What I have done is built a form
Hi Tracy!
Thanks for the quick reply. Actually what I'm trying to do is 'automate'
a feature that's already built into mwresize. If you right click the
resizer tab in the bottom right hand corner of the form mwresize pops
up a small menu of choices (75%, 85%, 95%, etc) which, when you make a
Hey there RK,
Yes - I've been starting to use this a Lot - both in this small system we
have (that my Boss wants to run on a Tablet) - and also as part of the
Re-Write of this OLD BIG system we have (which currently runs under Windows
but the screens are code running in windows that look like DOS
On 3/27/2013 4:01 PM, Kurt wrote:
Does this mean that in order for the ReSizer stuff to work right - that I
MUST Get Out of VFP7 - and stick w/VFP9???
Why would you want to stay in VFP7 anyway especially when VFP9 is an
option?? It's not like the EULA is any friendlier.
--
Mike
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Kurt
Sent: Wednesday, March 27, 2013 4:01 PM
To: profoxt...@leafe.com
Subject: RE: MWResize implementation
Hey there RK,
Yes - I've been starting to use this a Lot - both in this small system we have
(that my
: Wednesday, March 27, 2013 4:13 PM
To: profoxt...@leafe.com
Subject: RE: MWResize implementation
There were so many improvements to the grid control alone in VFP 9 that I
would run to get out of 7. Not to mention much better support for more
current versions of Windoze.
I'm still poking at the active
Richard Kaye wrote on 2013-03-06:
For anyone following along, I 've narrowed it down to the
saveOriginalSize method where it attempts to add a property on the fly. My
suspicion is the property is already there and attempting to add the same
property causes the C5 error. More to come...
--
My first theory was wrong. It was not related to attempting to add a property
at runtime that already existed. (And thanks Tracy :-). I do know that is the
sort of thing that can cause C5 errors which is why I thought it was the
culprit.) Although I do wonder why the statement at line 95 of the
12 matches
Mail list logo
