On Tuesday 18 May 2004 00:54, Tuomo Valkonen wrote:
> The systray patch has now been merged to both ion2 and ion3 in svn.
> There was an incorrect use of XFree in the patch and also another
> in the module. I fixed them, but don't think they are related to
> the kbluetoothd problem.
Thanks a lot for merging this patch, I just became accustomed to using kde 
apps with system tray icons without the need for adding kludges for every 
fresh application :)

As for kbluetoothd: I really think the best way (not only for system tray 
icons, but also other windows in very small frames), to make transients 
independent from their owner if the owner window is (e.g.) smaller than 60x60 
pixels. Or even better, if the suggested window size from the transient is 
more than the double space which the current frame can provide, make it 
independent.

This would also make it easier for layouts, where you have a small frame on 
either side of the screen for an instant messenger e.g., and you want to open 
its configuration dialog, which does not fit at all in this frame.
With the current implementation, you would either need to setup kludges (if 
possible), or move the window with the transient to a larger screen and edit 
your options. after that you need to move the main window back to the smaller 
frame.
By making transients independent, if the size of the frame is _by far_ not 
large enough, you would only need to move the configuration dialog to a 
larger window, but not move the main window back to the original frame.

As for the stack trace of the crash:
I did install the gentoo ebuild of Ion, so I think there are no debug 
information in my executable.
How can I check/perform a stack trace? Or is it just the "core" file, which 
sometimes get generated, when a program crashes?

regards,

--
Martin

Reply via email to