[interfacekit] Re: BApplication tests crash

> It looks like everyone is on vacation these days (the list is 
> completely idle),
> so I tought to put some "meat" on the fire.
> 
> I noticed that BApplication "QuitRequest" tests are crashing these 
> days. They
> worked just fine before Axel added the creation of the system default 
> BCursors
> in BApplication. 
> 
> By deductive reasoning, I tought that something is broken in cursor
> creation/destruction code :)
Perhaps. I have been having crashes,too. For quite some time I've been 
attempting to hunt down a problem that I've had for quite some time 
where BApplication will crash (IIRC) in InitData, but everything is 
just hunky-dory inside the server, and nothing looks wrong.

> I would've started researching the issue, but I know Pahtz has worked 
> on the app
> server's code, so I wanted to see if his code fixes the problem 
> before.
> 
> Though, I see it's not been integrated in the cvs yet. Any reason for 
> that? 
Pahtz's code changes are actually some sweeping changes to the 
messaging classes. It makes some mostly-internal changes to the 
PortLink class and, in doing so, eliminates the need for PortMessage, 
Session, and PortQueue. While I won't speak for Adi, but I must admit 
that I'm thankful for the changes because I had a feeling that there 
had to be a way to , but I couldn't figure out what it was. Anyway, we 
haven't seen them yet because I was going to integrate the changes into 
the tree (Pahtz doesn't have CVS access) and I went on vacation before 
I could do it. It's also been a *lot* of work -- Window.cpp is like 70K 
in size and View.cpp is like107K.  The face that All the changes to the 
App and Interface Kits are done and some of the files for the server 
are done. You should see a pretty big check-in for all this within a 
day or two, barring major problems.

--DW

Other related posts: