Kapp and Qt designer issue

[ian reinhart geiser]

Lubos Lunak said:
> On Thursday 18 of March 2004 15:23, Ian Reinhart Geiser wrote:
>> On Thursday 18 March 2004 09:17 am, Lubos Lunak wrote:
>> > On Thursday 18 of March 2004 14:56, Ian Reinhart Geiser wrote:
>> > > On Thursday 18 March 2004 08:52 am, Waldo Bastian wrote:
>> > > > On Thu March 18 2004 14:09, Ian Reinhart Geiser wrote:
>> > > > > 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.
>> > > >
>> > > > You may want to find out why that happens then.
>> > >
>> > > This happens because Qt designer dosent use Kapp, it uses QApp and
>> the
>> > > kapp ptr is never initialized.
>> >
>> > kapplication.cpp:136: KApplication* KApplication::KApp = 0L;
>>
>> Is this going to happen even if it is called from designer?
>
>  That's no real initialization. The pointer is NULL already in the binary
> (or
> it should be cleared after loading into memory, I'm not sure if it's in
> .data
> or .bss - but that doesn't matter).
>
>> From what I can see no.
>
>  The attached testcase disagrees. You have a problem somewhere. Maybe
> valgrind's VALGRIND_MAKE_READABLE could help (if it makes things
> read-only, I
> don't know).
Hrm, so your Qt designer wont crash when you open a ui file with a
KLineEdit in it?  Somehow now all UI files that contain KDE widgets crash.
Im on my ppc now, so Ill have to try with valgrind later this evening. 
Ideally we can get to the bottom of this soon, since no-one can edit ui
files at this point.

Cheers
-ian reinhart geiser






!DSPAM:4059cd19204563135918468!