It works perfectly.
I like to use the Anchor property editor/builder too. It is really useful
with common settings and the always helpful try it out here feature. Cool
example what you can do with property editors.
Rick
White Light Computing, Inc.
www.whitelightcomputing.com
www.swfox.net
...@leafe.com] On
Behalf Of Fred Taylor
Sent: 13 March 2009 02:07
To: profoxt...@leafe.com
Subject: Re: Good reasons to upgrade (was Re: FW: Autoincrement field)
That's what the .Anchor property is for. A value of 5 (top and bottom
absolute) might be what you need.
Fred
On Thu, Mar 12, 2009 at 5:03
Kevin, I 100% agree with you here. When user maximizes Excel he
expects to see more columns, not same number of columns.
If the user wants to widen a column, he has means to do it. In both
Excel and VFP.
(Side note: same rationale applies to why the programmer should NEVER
increase/decrease the
The help file spells that out pretty clearly. Of course, I scratched my head
for a while until I noticed this. The anchor uses the location when the object
is created.
If you want to base anchoring on the control's current position after it is
has been moved, reset the control's Anchor
I've resorted to putting some controls inside a container and setting the
container to grow relatively. The objects in the container are set absolute.
This keeps labels and buttons tight with the grid that resizes.
Tracy
-Original Message-
From: Richard Kaye
Sent: Friday, March 13, 2009
[mailto:profoxtech-boun...@leafe.com] On
Behalf Of Tracy Pearson
Sent: Friday, March 13, 2009 9:43 AM
To: profoxt...@leafe.com
Subject: RE: Good reasons to upgrade (was Re: FW: Autoincrement field)
I've resorted to putting some controls inside a container and setting the
container to grow relatively
Rick Schummer wrote:
It works perfectly.
I like to use the Anchor property editor/builder too. It is really useful
with common settings and the always helpful try it out here feature. Cool
example what you can do with property editors.
Agreed. That was a very nice touch on that feature!
Grigore Dolghin wrote:
(Side note: same rationale applies to why the programmer should NEVER
increase/decrease the font size during resize).
I agree. (Some devs actually do that? Say it ain't so!)
___
Post Messages to: ProFox@leafe.com
(Side note: same rationale applies to why the programmer should NEVER
increase/decrease the font size during resize).
While I agree that the zoom/resize feature is annoying, I have customers who
are visually handicap and they love the zoom feature. Another one of those
personal preferences.
Rick Schummer wrote:
(Side note: same rationale applies to why the programmer should NEVER
increase/decrease the font size during resize).
While I agree that the zoom/resize feature is annoying, I have customers who
are visually handicap and they love the zoom feature. Another one of those
On Fri, March 13, 2009 12:11 pm, Paul McNett wrote:
I think that both are valid but separate concepts:
+ controls should resize to the size of the form, but *not* change font
size.
+ there should be separate Zoom In/Zoom Out/Zoom Normal functions that
change the font size and control size,
So I'm just missing the code in the grid.Resize? Do you bind that to
the form resize with BINDEVENTS?
That's exactly what I wanted it for---to drop the grid with the bottom
when the user resizes.
Tracy Pearson wrote:
It's not totally useless for grids. You do need to add code in the resize
No need to bind anything.
Put code to call a method in the resize event of the grid. In the method
handle the column resizing. When the grid's anchor property is set to allow
horizontal growth, changing the width of the parent container fires the
resize event which calls your method.
Tracy
I've been just calling the grid.AutoFit() method to optimize the grid
columns, assuming that there isn't a huge text field being displayed.
Would there be other downsides to calling that method?
-Kevin
CULLY Technologies, LLC
Tracy Pearson wrote:
No need to bind anything.
Put code to call a
I've not used it extensively. Depending on the data, you might have 5 rows
showing with short information, then when the user scrolls down the
information is cut off. It is the user experience that keeps me from using
it. Spreadsheet programs have that feature, and when I've used it, I've not
, March 12, 2009 3:26 PM
Subject: Re: Good reasons to upgrade (was Re: FW: Autoincrement field)
I've been just calling the grid.AutoFit() method to optimize the grid
columns, assuming that there isn't a huge text field being displayed.
Would there be other downsides to calling that method
Kevin Cully wrote:
I've been just calling the grid.AutoFit() method to optimize the grid
columns, assuming that there isn't a huge text field being displayed.
Would there be other downsides to calling that method?
I too always just used AutoSize for the horizontal display. What I'm
looking
That's what the .Anchor property is for. A value of 5 (top and bottom
absolute) might be what you need.
Fred
On Thu, Mar 12, 2009 at 5:03 PM, MB Software Solutions General Account
mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
Kevin Cully wrote:
I've been just calling the
Fred Taylor wrote:
That's what the .Anchor property is for. A value of 5 (top and bottom
absolute) might be what you need.
Well I'll be darned.for whatever reason, I must have done something
different last time. It works perfectly. I've thrown together a quick
grid sample form and sent
enhancements to TEXT...ENDTEXT
anchors
mo' better convergence of ANSI SQL with VFP SQL
intellisense in watch window
Richard Kaye
Vice President
Artfact/RFC Systems
Voice: 617.219.1038
Fax: 617.219.1001
On Wed, March 11, 2009 11:50 am, Vince Teachout wrote:
John Weller wrote:
It's
On Wed, March 11, 2009 3:18 pm, Richard Kaye wrote:
enhancements to TEXT...ENDTEXT anchors mo' better convergence of ANSI SQL
with VFP SQL intellisense in watch window
The anchors feature sounds very cool, but I must admit that I've not yet
tapped into that. You have, obviously? How many
It's not totally useless for grids. You do need to add code in the resize
event of a grid to account for the width changes. Each grid will be unique,
but can be generic with a property holding the resizable columns. Vertical
changes are a big plus to the user.
-Original Message-
From: MB
22 matches
Mail list logo
