🚀 go-pugleaf

"Bogdan" <boprea@xnet.ro> wrote in message
news:43ecd5bb@newsgroups.borland.com...

> I cannot make a difference between a job that is deleted before
> printing because the user chose to abort the print operation, and
> the job that is deleted from the spooler because it finished printing.

You have to keep track of the job information.  Currently, you are
completely ignoring the pPrinterNotifyOptions and ppPrinterNotifyInfo
parameters of FindNextPrinterChangeNotification().  The ppPrinterNotifyInfo
parameter provides detailed information about each notification.  For
example, you can use it to detect JOB_NOTIFY_FIELD_STATUS,
JOB_NOTIFY_FIELD_PAGES_PRINTED, and/or JOB_NOTIFY_FIELD_BYTES_PRINTED
changes.  Also, you should be keeping track of the active jobs as well.
When a job is added, add its information to a list somewhere.  When the job
is deleted, remove the job from your list.  When the job is written to the
printer, keep track of its printing status.  When the job is deleted, you
can check the last known status to know what the job was doing.

> while(!Terminated)
>  {
>   WaitForSingleObject(Notifier,INFINITE);

By doing that, you won't be able to terminate the thread while it is waiting
for a notification.  You should use CreateEvent() to create a second event
and then use WaitForMultipleObjects() instead.  This way, when the
application wants to shut down the thread, it can signal the event.

>   Changes = 0x00000000;
>   if(FindNextPrinterChangeNotification(Notifier,&Changes,NULL,NULL))
>   {

Where are you calling FindFirstPrinterChangeNotification()?  Which
notifications are you asking it for?


Gambit