Apache OpenOffice (AOO) Bugzilla – Issue 65304
"completed" startup-notification on short-lived slave soffices not called
Last modified: 2006-06-27 11:42:04 UTC
Using gnome - when starting a second instance of an openoffice application launch feedback stays on - example with word processor: i.e. Launch word processor from panel, "starting..." appears and on frame map disappears as desired, but now launch again from pannel "Starting..." appears, but after frame map it remains until timeout. This is with StartupNotify=true in the .desktop files. Trivial patch, perhaps all wrong attached.
Created attachment 36409 [details] simple fix
mmeeks: is this the right way to do this in gtk where the new app just asks the old app to launch a new window kendy: FYI as we were talking about this earlier
seems to be an easy one. However what happens if gdk_notify_startup_complete() gets called twice ? One would hope nothing at all else the first instance will of course do something unwanted. OTOH we could easily protect ourselves against this by setting a bool on the first GtkSalFrame::Show(TRUE). Michael: what is your opinion ?
In the KDE plugin, we simply have m_bStartupDone attribute to remember whether it was called: SalKDEDisplay::~SalKDEDisplay() { // in case never a frame opened static_cast<KDEXLib*>(GetXLib())->doStartup(); [etc.] void KDEXLib::doStartup() { if( ! m_bStartupDone ) { KStartupInfo::appStarted(); m_bStartupDone = true; #if OSL_DEBUG_LEVEL > 1 fprintf( stderr, "called KStartupInfo::appStarted()\n" ); #endif } } IIRC, it was safe to call it twice in the KDE case, but just for case... ;-)
committed in CWS vcl59, added the check for frame already shown
verified in CWS vcl59
merged in 680m173