> Since each drawing area is the same size, the same drawing commands,
> right down to the coordinates, are used to draw on each one, only a
> portion of the contents of each small DrawingArea changes (in this case
> its a QR Code). Everything else remains the same.
Sounds perfect place to pass c
On 09/03/2014 04:27 PM, Tobias Boege wrote:
> On Wed, 03 Sep 2014, Stephen wrote:
>> On 09/03/2014 02:33 PM, Jussi Lahtinen wrote:
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
On Wed, 03 Sep 2014, Stephen wrote:
> On 09/03/2014 02:33 PM, Jussi Lahtinen wrote:
> >> 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
> >
On 09/03/2014 02:33 PM, Jussi Lahtinen wrote:
>> 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..?
>
>
Since each drawing a
> 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 t
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 h
>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 area
Everything works now?
Jussi
On Wed, Sep 3, 2014 at 6:28 PM, Stephen 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 09/03/2014 11:18
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 11
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
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] =
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 are
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 th
> 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 drawing
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, usi
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 sub
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 m
17 matches
Mail list logo
