[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Kapp and Qt designer issue
From:       Ian Reinhart Geiser <ian () geiseri ! com>
Date:       2004-03-18 13:09:38
Message-ID: 200403180809.40428.ian () geiseri ! com
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,
	It seems that the nullchecks while well intentioned seem useless on my 
system, as the kapp pointer is initialized and there for NOT 0.  This is one 
of the crashes when you try to use Qt designer now.  My question is how would 
this be best to work with.  Since we cannot test a pointer for validity other 
than a null check, should we just make the kapp ptr null in the widget 
plugin? if so can i just #include <kapplication.h> and set kapp = 0L;?

	Second do we also require that every kapp ptr access be null checked in 
kdeui?  While cumbersome this seems like the only way to ensure that the kapp 
ptr is NOT accessed from the Qt widgets.

	This may not be the whole problem, but gdb seems to think this is the one 
thats crashing my Qt designer everywhere else.

	Cheers
	-ian reinhart geiser

	
- -- 
- --:Ian Reinhart Geiser <geiseri@yahoo.com>
- --:Public Key: http://geiseri.myip.org/~geiseri/publickey.asc
- --:Public Calender: http://geiseri.myip.org/~geiseri/publicevents.ics
- --:Jabber: geiseri@geiseri.myip.org
- --:Be an optimist -- at least until they start moving animals in 
- --:   pairs to Cape Canaveral. ~ Source Unknown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAWZ+SPy62TRm8dvgRAq0RAJsF/EWkz7k6yy3CWLkIzF5Ug4wyhACeK7O/
fzKHlR56XXenjk7waR1l6Pw=
=vmKw
-----END PGP SIGNATURE-----


!DSPAM:4059a184169711166916928!


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic