Standard window event handler on OS X

View: New views
3 Messages — Rating Filter:   Alert me  

Standard window event handler on OS X

by Andreas Menzi :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi everyone,

Did anybody ever try to install a standard window event handler on a  
window that carries the plugin area? I am working with scrollbars and  
need to have the standard handler to draw the scrollbar controls. The  
problem when installing the standard handler (which is  
inconprehensibly not installed) on the window  is that the event  
"eAE_Deinit " isn't sent to the plugin any more and let's me guess  
that other 4D functionality won't work anymore.

andy
**********************************************************************
4D Plugins hosted by 4D, Inc.                      http://www.4D.com/

    Register for 4D Summit 2009 Today
    Early Bird Pricing Ends August 28th - http://www.4D.com/summit

To Unsubscribe:                      mailto:4D-Plugins-off@...
***********************************************************************


Re: Standard window event handler on OS X

by Miloslav Bystricky :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On 24 Jul 2009, at 12:06, Andreas Menzi wrote:

> Did anybody ever try to install a standard window event handler on a  
> window that carries the plugin area? I am working with scrollbars  
> and need to have the standard handler to draw the scrollbar  
> controls. The problem when installing the standard handler (which is  
> inconprehensibly not installed) on the window  is that the event  
> "eAE_Deinit " isn't sent to the plugin any more and let's me guess  
> that other 4D functionality won't work anymore.


We did it, so it can be done. We worked on it many years ago, so I do  
not remember the details, but if you have specific question I can take  
a look into code.

In general, 4D does not like if you install your own event handler,  
and if there is another plugin that's try to install event handler  
(for drag & drop, for example) there are more problems. The problem is  
not with installation but rather with deinstallation of event handler  
- if it is not done properly it may hang or crash 4D and we did not  
found a way how to do this properly.

WE ended with creating a fake window over the plugin area, and we  
install drag & drop handler and scrollbars to this window. As 4D does  
not know anything about this window, there are less problems with 4D.

The above holds for 4D 2004, with v11 we are still testing it. In  
theory, in v11 all this stuff should be easier.

Regards,

Peter Bozek
http://www.inforce.sk

**********************************************************************
4D Plugins hosted by 4D, Inc.                      http://www.4D.com/

    Register for 4D Summit 2009 Today
    Early Bird Pricing Ends August 28th - http://www.4D.com/summit

To Unsubscribe:                      mailto:4D-Plugins-off@...
***********************************************************************


Re: Standard window event handler on OS X

by Andreas Menzi :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks for your reply. I was wondering if you were able to get the  
deinit event from 4D when the standard handler is active? If you could  
take a look in your old code, that would be great! Thanks in advance.

regards, andy

Am 28.07.2009 um 23:00 schrieb Miloslav Bystricky:

>
> On 24 Jul 2009, at 12:06, Andreas Menzi wrote:
>
>> Did anybody ever try to install a standard window event handler on  
>> a window that carries the plugin area? I am working with scrollbars  
>> and need to have the standard handler to draw the scrollbar  
>> controls. The problem when installing the standard handler (which  
>> is inconprehensibly not installed) on the window  is that the  
>> event  "eAE_Deinit " isn't sent to the plugin any more and let's me  
>> guess that other 4D functionality won't work anymore.
>
>
> We did it, so it can be done. We worked on it many years ago, so I  
> do not remember the details, but if you have specific question I can  
> take a look into code.
>
> In general, 4D does not like if you install your own event handler,  
> and if there is another plugin that's try to install event handler  
> (for drag & drop, for example) there are more problems. The problem  
> is not with installation but rather with deinstallation of event  
> handler - if it is not done properly it may hang or crash 4D and we  
> did not found a way how to do this properly.
>
> WE ended with creating a fake window over the plugin area, and we  
> install drag & drop handler and scrollbars to this window. As 4D  
> does not know anything about this window, there are less problems  
> with 4D.
>
> The above holds for 4D 2004, with v11 we are still testing it. In  
> theory, in v11 all this stuff should be easier.
>
> Regards,
>
> Peter Bozek
> http://www.inforce.sk
>
> **********************************************************************
> 4D Plugins hosted by 4D, Inc.                      http://www.4D.com/
>
>   Register for 4D Summit 2009 Today
>   Early Bird Pricing Ends August 28th - http://www.4D.com/summit
>
> To Unsubscribe:                      mailto:4D-Plugins-off@...
> ***********************************************************************
>

**********************************************************************
4D Plugins hosted by 4D, Inc.                      http://www.4D.com/

    Register for 4D Summit 2009 Today
    Early Bird Pricing Ends August 28th - http://www.4D.com/summit

To Unsubscribe:                      mailto:4D-Plugins-off@...
***********************************************************************