Hello VEE,
I want, that at killing the window of my VXE application the message created by me was called. How it to make?
--
Sergei Petrov
NTNK,
127254, Ogorodny proezd 5,
of.506,Moscow, Russia
mailto:petrov@ntnk.ru
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
I want, that at killing the window of my VXE application the message created by me was called. How it to make?
--
Sergei Petrov
NTNK,
127254, Ogorodny proezd 5,
of.506,Moscow, Russia
mailto:petrov@ntnk.ru
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
the class Name for Agilent VEE 6 and above is 'AgilentVEE'.
best regards,
G. Nied
-------------------------------------------------------------------------
Georg Nied - Software-Development - Hansestr.7 - 51149 Cologne - Germany
Tel: +49 2203 9770915 - Fax: +49 2203 9770924 - eMail:info@gn-software.de
-------------------------------------------------------------------------
-------- Original Message --------
Subject: [vrf] RE: AW: RE: Printer scaling and orientation at runtime? (14-Apr-2003 10:13)
From: werner_jacoby@agilent.com
To: vrf@it.lists.it.agilent.com
> Hi Shawn,
>
> this seems to be a powerful function.
> I've problems running it in Vee Pro 6.03, since
> the 'class name' seems not to be Agilent_VEE,
> neither VEE PRO or similar.
>
> How to find such a class name ?
>
> Thanks & cheers,
> Werner.
>
>
> > -----Original Message-----
> > From: Shawn Fessenden [mailto:shawn@testech-ltd.com]
> > Sent: Monday, April 14, 2003 06:35
> > To: VEE vrf
> > Subject: [vrf] RE: AW: RE: Printer scaling and orientation at runtime?
> >
> >
> > All (and Horst) -
> >
> > > The better way to do this is to
> > > use a Device Independent Bitmap.
> > [snip]
> > > in my opinion it's out of VEE's
> > > practical reach.
> >
> > I was wrong. Using the memory copy routines and constants to name the
> > various members of the structures necessary to create and
> > manipulate DIBs,
> > this task becomes almost no more difficult than in any other language.
> >
> > Big thanks to Georg Neid from whom I lifted the Set Variable
> > mechanism in
> > LoadConstants. Without something like this I wouldn't have
> > attempted to do a
> > PrintScreen in the first place. In return you can have my
> > LoadLibs, though
> > this one is one step short of the one I really use
> >
> > So here is the PrintScreen program using a DIB. This produces
> > far superior
> > output to that produced by the DDB version. I've also fixed a
> > problem with
> > the GetPrinterDC function that I didn't notice before. This
> > had to do with
> > choosing a printer only and doesn't show up if you feed a
> > printer name to
> > the function.
> >
> > The one remaining issue is that the output is misaligned with
> > the printer
> > for some reason, producing a slight wrap-around on the right
> > side of the
> > output. This probably has something to do with the fact that
> > DIB scan lines
> > have to be aligned on DWORD boundaries and I didn't provide
> > for this in the
> > GetBits function but I'm too lazy to track it down at the
> > moment. Come to
> > think of it, GetBits really ought to be called FindDIBits.
> >
> > Also, this version assumes a 24 bits per pixel source. This
> > means that to
> > use this you'll have to have either 16- or 24-bit color set
> > on your screen
> > display properties. The GetBits function needs to be modified
> > to calculate
> > the offset of the bit array by adding the size of the color
> > palette to the
> > size of the BITMAPINFO header. An example of this calculation
> > is in the
> > DdbToDib function on line 21. The variable lAddMem is the offset we're
> > looking for. Palletized bitmaps have biBitCount values of 1,
> > 4 and 8 (16-bit
> > color is treated as 24). To print palletized DIBs, the
> > StretchDIBits call in
> > the Main function needs to pass DIB_PAL_COLORS instead of
> > DIB_RGB_COLORS.
> > Again, I'm just too lazy to fix it.
> >
> > Speaking of which, if the source bitmap is palletized then
> > that palette
> > should be retrieved, selected into the source DC and realized
> > before the
> > call to GetDIBits. I was just too lazy to do this. The
> > comment, "If source
> > has a logical palette, realize it here first" in the DdbToDib
> > function is
> > the place to do this.
> >
> > Compatibility with Windows 9x versions fails because of
> > GetPrinters. This
> > method assumes a flavor of Windows NT. This can be fixed
> > using the method I
> > mentioned earlier - read the [Devices] section of win.ini
> > into an array and
> > replace equal signs with commas. I'm very sorry, but I don't
> > want to fix
> > this either. The rest of it *is* 9x compatible. In fact, it's
> > almost Windows
> > 3.1 compatible.
> >
> > The function CanUseDIB should probably be used, but in the
> > field any printer
> > driver that doesn't support DIB use should be thrown away.
> > Except of course
> > plotter drivers. Any printer driver that doesn't support DIBs
> > or raster ops
> > will produce blank output from this program.
> >
> > This can be further optimized by replacing the calls to
> > GlobalXXX with calls
> > to the HeapXXX functions instead. Some of the Windows
> > wrappers can go away,
> > like StartDoc. StartDocA can be called directly from a
> > formula, but I just
> > don't like the look of StartDocA in code. Have fun with it.
> > -SHAWN-
> >
>
> ---
> You are currently subscribed to vrf as: g.nied@gn-software.de
> To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
> To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@it.lists.it.agilent.com".
>
> If you need help with the mailing list send a message to "owner-vrf@it.
> lists.it.agilent.com".
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".