FOX GUI Toolkit

On Wed, 25 Oct 2000, you wrote:
> Hello Jeroen,
> 
> I would _highly_ recommend to add the following little gcc-dependency to your
> source code. In FXString.h, line 228, change
> 
>   FXString& format(const char *fmt,...);
> 
> to
> 
>   FXString& format(const char *fmt,...)
> #ifdef __GNUG__
>     __attribute__((format (printf, 2, 3)))
> #endif
>    ;
> 
> 
> If you do so, then gcc will parse the provided fmt string and check
> if the other arguments passed through ... are matching. This catches
> a lot of errors.
> 
> 
> (BTW yesterday I've seen a 0.000 displayed from a %.2f format
>  -- beating dead horses :-))

This is a very useful suggestion.  Grepping through the /usr/include
directory, I see several other softwares (curses, ncurses, and so on)
do the same thing also.

I agree, this can save many a wild goose chase, so I'll add this right
away.

I'll turn into a macro, however, as this might reduce the #ifdef spaghetti.


	- Jeroen


-- 
+-------------------------------+--------------------------------------------+
| E-Mail : jvz@...        | The FOX Platform Independent GUI Toolkit:  |
| USMail : 215 Wynn Drive,      |                                            |
|          Huntsville, AL 35805 |  Official Site:                            |
| Phone  : (256) 726-4820       |     http://www.cfdrc.com/FOX/fox.html      |
| Fax    : (256) 726-4806       |     ftp://ftp.cfdrc.com/pub/FOX            |
| WWW    : http://www.cfdrc.com |                                            |
+-------------------------------+--------------------------------------------+
| Copyright (C) 09:20 10/25/2000 Jeroen van der Zijp.   All Rights Reserved. |
+----------------------------------------------------------------------------+

On Wed, 25 Oct 2000, you wrote:
> Hello Jeroen,
> 
> I would _highly_ recommend to add the following little gcc-dependency to your
> source code. In FXString.h, line 228, change
> 
>   FXString& format(const char *fmt,...);
> 
> to
> 
>   FXString& format(const char *fmt,...)
> #ifdef __GNUG__
>     __attribute__((format (printf, 2, 3)))
> #endif
>    ;
> 
> 
> If you do so, then gcc will parse the provided fmt string and check
> if the other arguments passed through ... are matching. This catches
> a lot of errors.
> 
> 
> (BTW yesterday I've seen a 0.000 displayed from a %.2f format
>  -- beating dead horses :-))
> 
> Ciao
> Dirk


Well, thanks again for the suggestion; I've implemented it and while
I found a number of harmless warnings, I did find one serious one
with a missing argument.

So it's been worth the effort already!

fxerror(), fxwarning(), fxmessage(), fxtrace(), FXMessageBox::error(), FXMessageBox::warning(),
FXMessageBox::question(), FXMessageBox::information(), FXString::format(), FXStringFormat()
are now all checked.

One little catch was that the "this" argument is included in the count.

To take advantage of this, compile your code with gcc and option -Wformat.

As I have done these with macros, if you define your own printf or scanf like
functions you can use these to macros to cause gcc to check the arguments
against the format:


	FX_PRINTF(if,ia)

	FX_SCANF(if,ia)


Where if is the index of the format string, ia is the index of the varargs.
the macros are defined as nothing on non-GCC machines.


Regards,


		Jeroen

-- 
+-------------------------------+--------------------------------------------+
| E-Mail : jvz@...        | The FOX Platform Independent GUI Toolkit:  |
| USMail : 215 Wynn Drive,      |                                            |
|          Huntsville, AL 35805 |  Official Site:                            |
| Phone  : (256) 726-4820       |     http://www.cfdrc.com/FOX/fox.html      |
| Fax    : (256) 726-4806       |     ftp://ftp.cfdrc.com/pub/FOX            |
| WWW    : http://www.cfdrc.com |                                            |
+-------------------------------+--------------------------------------------+
| Copyright (C) 10:30 10/25/2000 Jeroen van der Zijp.   All Rights Reserved. |
+----------------------------------------------------------------------------+

Now wait! When I exit the FOX app, everything goes back to normal. It only
happens
while my app is running. BTW, I'm using 0.99.131.

Windows 2000 Pro has this nice (?) drop shadow arrow cursor. Earlier FOX
versions kept this cursor even when I move the cursor over the FOX app. The
latest FOX version however seems to use its own flat cursor, and doesn't
restore the default cursor.

I'll check if this is all my fault, but I just wanted to check if anybody
else is experiencing the same problem.

- Daniel



> -----Original Message-----
> From: Daniel Gehriger [mailto:gehriger@...]
> Sent: Wednesday, October 25, 2000 9:17 AM
> To: Fox Mailing List
> Subject: Cursor problem ?
>
>
> (Windows 2000 Pro)
>
> In my application, I change the cursor to crosshairs and other
> customized shapes. Of course, when I move off my app's window,
> other applications change the cursor to arrows, wait arrows etc.
> So far, so good. However, I noticed that once I displayed a small
> cursor in my app, this somehow also limits the size of all other
> cursors. The result is that a couple of pixels at the bottom and
> at the right of the default Windows arrow are cut off, even when
> I exit my FOX app...
>
> Any ideas ?
>
> - Daniel

On Wed, 25 Oct 2000, you wrote:
> (Windows 2000 Pro)
> 
> In my application, I change the cursor to crosshairs and other customized
> shapes. Of course, when I move off my app's window, other applications
> change the cursor to arrows, wait arrows etc. So far, so good. However, I
> noticed that once I displayed a small cursor in my app, this somehow also
> limits the size of all other cursors. The result is that a couple of pixels
> at the bottom and at the right of the default Windows arrow are cut off,
> even when I exit my FOX app...
> 
> Any ideas ?

FOX builds many cursors already with the same code as what you're using 
(in FXApp::FXApp) and those seem to work fine.

The code in FXCursor::create() actually ALWAYS creates a 32x32 cursor; if
you specify a smaller bitmap, it just fills out the rest with zeros' masking
off the unused portion; so the specified size should make no difference.

The only thing I can think off is that custom cursors should be
destroyed after you no longer need them; FOX does not track sharable resources
like icons, cursors, images, and so on, so its up to the application code
to delete them when no longer needed.

Failing to do this may cause GDI to run out of handles.  This *may* be what's
going on (I'm not sure how running out of handles would manifest itself under
Windows).

Note, under X all most resources are freed automatically when the app quits;
I've been told that Windows may not be doing that, and therefore have gone
through some considerable amount of work to make sure all reachable, owned
resources are deleted when appropriate; but shared resources such as cursors
are not owned by the widgets that use them and have to be deleted explicitly.


Hope this helps finding the problem,



			- Jeroen



-- 
+-------------------------------+--------------------------------------------+
| E-Mail : jvz@...        | The FOX Platform Independent GUI Toolkit:  |
| USMail : 215 Wynn Drive,      |                                            |
|          Huntsville, AL 35805 |  Official Site:                            |
| Phone  : (256) 726-4820       |     http://www.cfdrc.com/FOX/fox.html      |
| Fax    : (256) 726-4806       |     ftp://ftp.cfdrc.com/pub/FOX            |
| WWW    : http://www.cfdrc.com |                                            |
+-------------------------------+--------------------------------------------+
| Copyright (C) 08:10 10/25/2000 Jeroen van der Zijp.   All Rights Reserved. |
+----------------------------------------------------------------------------+

Hi !

I use FOX on a Windows2000 and NVIDIA TNT2 chip and it works fine without
problems, I do not have any INTEL 440BX chipset though....

Mikael

----- Original Message -----
From: "Daniel Gehriger" <gehriger@...>
To: "Fox Mailing List" <foxgui-users@...>
Sent: Tuesday, October 24, 2000 8:04 PM
Subject: [Foxgui-users]OT: OpenGL freezes


> Hello,
>
> one of my FOX applications uses OpenGL. Some Windows computers (2000, 98)
> freeze randomly when accelleration is being used. The freezes happen
> randomly, and the computer needs to reset. Observed with NVDIA Riva TNT
128
> and ATI Rage 3D LT Pro on at least three computers. They all seem to use
the
> INTEL 440BX chipset, though.
>
> Has anybody of you had similar problems (eg. with the CFDRC softs for
> Windows ) ?
>
> Thanks for any help !
>
> - Daniel
>
> _______________________________________________
> Foxgui-users mailing list
> Foxgui-users@...
> http://lists.sourceforge.net/mailman/listinfo/foxgui-users