[fpc-pascal] fpGUI Toolkit v0.7-rc2 for FPC 2.4

Schindler Karl-Michael karl-michael.schindler at web.de
Fri Apr 9 10:41:42 CEST 2010


Hi

Am 08.04.2010 um 22:45 schrieb Graeme Geldenhuys:
> From the backtrace the initial problem starts with the call to
> WindowSetSupportPING() on line 1424 in fpg_x11.pas. Clearly the Mac
> "window manager" doesn't support all the usual features of modern
> Linux window managers does.

To some extend X11 is treated as a step child on Mac OS X.

> The WindowSetSupportPING() is not a
> critical feature - PING support simply detects if a program is not
> responding and then prompts the user if they would like to kill the
> app or continue waiting.
> 
> If you comment line 1424, does that resolve the X11 error you get?

I get the same error with line 1468:

    fpgApplication.netlayer.WindowAddProtocol(FWinHandle, xapplication.xia_wm_delete_window);

commenting out this, i get the error on 1828

  XGetGeometry(xapplication.display, TfpgX11Window(awin).FWinHandle, @rw, @x, @y, @w, @h, @bw, @d);

where I stopped.

> I'll research further to see if there is a way I can query window
> manager features in a more reliable manner.

when asking on the darwin mailing list, i received this answer:

   Explicit XSync or XInterAtom() to make sure the messages don't pass, queued in the night, and then you try an operation on an object which was queued but not serviced.

     You can see if sync is what's required by turning it on using the server option, so that you get it on every request, whether you want it or not.  Documentation on how to do this for Mac OS X's X11 server is at <http://developer.apple.com>.

This does not tell me much, but I'll search around. Maybe, it tells you more than me.

> Regards,
>  - Graeme -

Michael




More information about the fpc-pascal mailing list