C / C++ / MFC

Error executing function ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL)

24-Nov-08 0:13

prasadbuddhika wrote:
how can i call the event

You may call it 'MaxLengthExceededEvent' Big Grin | :-D

Warning: humorless people! Big Grin | :-D

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

modified on Monday, November 24, 2008 4:09 PM

Re: fire an event

Code-o-mat24-Nov-08 1:02

Code-o-mat

24-Nov-08 1:02

Check out the EN_MAXTEXT notification, maybe it's what you need.

Md Saleem Navalur23-Nov-08 23:54

Md Saleem Navalur

23-Nov-08 23:54

Hi,

I am calling this function, from my MFC app in VS 2005.

ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL);

If this call is made, printer selection dialog opens, if i select a printer and click ok, printing starts and everything works fine.

However, there is case, if the printer dialog is open and I do not click on ok and wait for a few seconds (say more than 10 sec), a server busy dialog shows up.
Server Busy
This action cannot be completed because the other program is busy. Chose
'Switch To' to activate the busy program and correct the problem.

But 'Switch To' activates the Start menu, and there is no way to make the
Server Busy error to go away except by killing my program altogether, and
then deleting the print task from the task list.

And i do not want to use, OLECMDEXECOPT_DONTPROMPTUSER for the second param.
Any suggestions please....

Thanks in Advance.
Saleem

Re: Error executing function ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL)

Ahmed Charfeddine24-Nov-08 3:08

Ahmed Charfeddine

24-Nov-08 3:08

What happens to the "server busy dialog" when you click OK on the print dialog ?

Re: Error executing function ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL)

Md Saleem Navalur24-Nov-08 19:57

Md Saleem Navalur

24-Nov-08 19:57

Nope, you cannot do anything with the app once the server busy dialog comes.
You have to kill the app from the task manager, and also the print window has to be killed.

Re: Error executing function ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL)

Ahmed Charfeddine24-Nov-08 21:47

Ahmed Charfeddine

24-Nov-08 21:47

I see..
I think this is because of the way how OLE request are dispatched : the OLE client sends a request which is not handled within the context of it current thread, rather by another thread (of course this may be dependent on the type of OLE server which you are dealing with).
Then the client blocks on sort of double events : one related to a timeout for a timer that has already been started ny the client, the other is related to a notification sent back by the OLE server which it finalizes the request job.
In your case, what happens is that the timeout occurs before the request is done.This has lead to a bizarre situation between the OLE client and the OLE server. Of course because of the way this has been internally coded (not because of your code).
I think your only solution is to try play on the timeout value or even force somehow the OLE framework not to show the busy dialog..
Link : http://support.microsoft.com/kb/248019[^]

Good luck.

Re: Error executing function ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL)

Md Saleem Navalur25-Nov-08 1:03

Md Saleem Navalur

25-Nov-08 1:03

Thanks for the inputs.

This what is tried ..
{
OleInitialize(NULL);

ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL);

OleUninitialize();
}

This does not work.
Then i tried this...

{
AfxOleGetMessageFilter()->EnableBusyDialog(FALSE);
ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL);
}

This did not work either.

Any inputs will be great.

Thanks,
Saleem

Re: Error executing function ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL)

Ahmed Charfeddine25-Nov-08 2:14

Ahmed Charfeddine

25-Nov-08 2:14

try COleMessageFilter::SetRetryReply in order to force your app, to repoll on the OLE server response, when the internal timer is expired.

Re: Error executing function ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL)

Axel Zur3-Feb-11 20:22

Axel Zur

3-Feb-11 20:22

Try this instead:

AfxOleGetMessageFilter()->EnableNotRespondingDialog(false);
ExecWB(OLECMDID_PRINT, OLECMDEXECOPT_PROMPTUSER, NULL, NULL);

Problem using Pointer Functions

ajorge200823-Nov-08 23:32

23-Nov-08 23:32

Hi to all!

I never used Pointer Functions, and now i'm trying to use a C Pointer Function in Visual Studio 2005. But there's a problem... the pointer function isn't working properly... This kind of functions doesn't work in the same way in C and in C++?

My pointer function declaration in C is:

void (*FktFunction)( void * RegistFuncPtr, TOnDriverEvent eventcallback);

and the call definition is:

(*FktFunction)(TDriverLayer_RegisterDevice, TSMAData_OnNewEvent);

At this time, the function TDriverLayer_RegisterDevice isn't working at all.

The declaration of that function is:

int TDriverLayer_RegisterDevice(struct TDevice * newdev);

Anyone could help me with this?

Best regards.

CPallini23-Nov-08 23:40

23-Nov-08 23:40

ajorge2008 wrote:
void (*FktFunction)( void * RegistFuncPtr, TOnDriverEvent eventcallback);

RegistFunctPtr is NOT a function pointer.
Smile | :)

ajorge200824-Nov-08 0:18

24-Nov-08 0:18

Hum... I've changed the Pointer Function definition to this one:

void (*FktFunction)( int (*RegistFuncPtr)(struct TDevice * newdev), TOnDriverEvent eventcallback);

But the register device function still not working Frown | :(

Could you give me any help please?

Best regards.

Cedric Moonen24-Nov-08 0:56

Cedric Moonen

24-Nov-08 0:56

ajorge2008 wrote:
But the register device function still not working

Which means what exactly ? Please be precise in your answer (e.g. if you have a compilation error, supply the error message).

Cédric Moonen
Software developer

Charting control [v1.5]
OpenGL game tutorial in C++

ajorge200824-Nov-08 1:03

24-Nov-08 1:03

Ok
I'm debugging the program that uses those functions mentioned earlier. I've attached a checkpoint on TDriverLayer_RegisterDevice function body and it doesn't stop there. So i'm thinking that when running my program, that function isn't even being considered. But we're calling it from (*FktFunction)(TDriverLayer_RegisterDevice, TSMAData_OnNewEvent); ?! That's the problem...

Best Regards.

CPallini24-Nov-08 1:03

24-Nov-08 1:03

Possibly you should post more code.
Smile | :)

ajorge200824-Nov-08 1:09

24-Nov-08 1:09

Declaration:

void (*FktFunction)(int (*RegistFuncPtr)(struct TDevice * newdev), TOnDriverEvent eventcallback);

Calling:

(*FktFunction)(TDriverLayer_RegisterDevice, TSMAData_OnNewEvent);

int TDriverLayer_RegisterDevice(struct TDevice * newdev)
{
   struct TDevice * CurDev;

   /*
   ** Geraet schon mit diesem Namen registriert?
   */
   foreach(&DeviceBase, CurDev)
   {
      if (strcmp(newdev->cName, CurDev->cName) == 0)
      {
         /* Geraet mit diesem Namen schon da! */
         return PHY_ERROR_DEV_TWICE;
      }
   }


   /*
   ** insert new driver in internal driver list
   */
   newdev->DriverID = NextUniqueDriverID++;//set unique driver ID for this driver
   ADDTAIL(&DeviceBase, &newdev->Node);

   return PHY_OK;
}

CPallini24-Nov-08 1:32

24-Nov-08 1:32

ajorge2008 wrote:
foreach

??? (the above is not a C++ statement).

ajorge2008 wrote:
FktFunction

What function is this pointer assigned to?

Smile | :)

ajorge200824-Nov-08 1:39

24-Nov-08 1:39

foreach is earlier defined as a function to search any kind of object we need to find in a list.

FktFunction pointer is assigned to

int TDriverLayer_RegisterDevice(struct TDevice * newdev)

CPallini24-Nov-08 1:42