Attached is a sample project that dynamically instantiates 10
business card sized DrawingAreas within a Panel on a forum. The form
represents a North American letter-sized sheet of paper. Since the Draw
event must be used to draw within each of the Drawing areas, and the the
Drawing Areas
Typographical error in the code (not that it is causing a problem).
This line
mDrawingAreaMatrix[X] = NEW DrawingArea(Panel1) AS Card CInt(X)
CInt(X) is redundant and not at all what I was thinking about when I
typed that line. It should more properly read;
mDrawingAreaMatrix[X] =
Paint.Begin and use cached mode? Trying that now.
On 09/03/2014 11:14 AM, Stephen wrote:
Typographical error in the code (not that it is causing a problem).
This line
mDrawingAreaMatrix[X] = NEW DrawingArea(Panel1) AS Card CInt(X)
CInt(X) is redundant and not at all what I was
Uh huh. It figures, almost four hours after the initial post,
frustration levels climbing, I sent that email then the solution hits me
square between the eyes.
Yes use cached mode.
On 09/03/2014 11:18 AM, Stephen wrote:
Paint.Begin and use cached mode? Trying that now.
On 09/03/2014
Everything works now?
Jussi
On Wed, Sep 3, 2014 at 6:28 PM, Stephen sbun...@smartsonsite.com wrote:
Uh huh. It figures, almost four hours after the initial post,
frustration levels climbing, I sent that email then the solution hits me
square between the eyes.
Yes use cached mode.
On
mDrawingAreaMatrix[X] = NEW DrawingArea(Panel1) AS Card CStr(X)
I'm beginning to think that what I am trying to accomplish is not
possible. How can a Draw event that is not in the compile-time source be
accessed during run-time?
I don't know why you need multiple drawing areas, but
Yes indeed :) Using cache mode for each instantiated DrawingArea we
can manipulate them as desired.
You asked why am I using 10 drawing areas, oddly enough the answer is to
simplify things from a layout standpoint... didn't figure on having this
much trouble with it... but persistence (and
You asked why am I using 10 drawing areas, oddly enough the answer is to
simplify things from a layout standpoint...
Just figure out how to draw one card and make multiple copies of it to same
one big drawing area..?
Now to print the darn things.
Yeah... to print the things you need to
Has anyone got some good documentation on how to use a Drawing Area,
quite frankly I've gone cross-eyed trying to make sense of it by parsing
the paint example.
Steve.
--
Slashdot TV.
Video for Nerds. Stuff that
FMain contains subs named Example## (where ## are numbers).
These subs are executed in Draw event DrawingArea1_Draw(), with command
Object.Call(Me, $sFunctionName). So that Example1 is same as Arc ,
Example2 is Arc negative, Example3 is Clip, etc.
You can write all the content of those subs
I guess it is the need to use the draw event in order to do anything
with the drawing area that had me spun. I think in terms of methods,
properties and events, but I do not think in terms of events being the
very thing that actually does the work.
I'm thinking of it now in terms of Macros,
I guess it is the need to use the draw event in order to do anything
with the drawing area that had me spun. I think in terms of methods,
properties and events, but I do not think in terms of events being the
very thing that actually does the work.
Draw event is called every time drawingarea
On 09/02/2014 06:22 PM, Jussi Lahtinen wrote:
I guess it is the need to use the draw event in order to do anything
with the drawing area that had me spun. I think in terms of methods,
properties and events, but I do not think in terms of events being the
very thing that actually does the work.
13 matches
Mail list logo
