Bug 39246 - uim-pref, uim-dict and uim-input-pad-ja should have single instance
Summary: uim-pref, uim-dict and uim-input-pad-ja should have single instance
Status: RESOLVED MOVED
Alias: None
Product: UIM
Classification: Unclassified
Component: helper: toolbar (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: uim-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-14 20:54 UTC by d+bugzilla
Modified: 2012-10-28 08:40 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description d+bugzilla 2011-07-14 20:54:02 UTC 
[ this is forwarded from http://bugs.debian.org/472515 ]

When I click on the prefs button or the method switcher button in the
applet, it opens a new window even if such a window is already opened.
It's easy to create dozens of identical windows that way.

It should really open a window if it doesn't exist and otherwise make
the existing window visible.
Comment 1 Muneyuki Noguchi 2011-07-17 00:40:51 UTC 
Currently, this report is related only to uim-pref because uim-im-switcher is a single instance application from uim 1.6.0 (fixed in #2112).
Comment 2 d+bugzilla 2011-07-17 01:42:52 UTC 
thank you for your checking.
but uim-dict and uim-input-pad-ja should do too.
Comment 3 Muneyuki Noguchi 2012-10-28 03:45:48 UTC 
(In reply to comment #2)
> thank you for your checking.
> but uim-dict and uim-input-pad-ja should do too.
Why do you think that uim-dict and uim-input-pad-ja should have a limitation on number of instances?

Multiple instances of uim-pref and uim-im-switcher make user confused because the configurations which can be set by uim-pref and uim-im-switcher is single. But uim-dict and uim-input-pad-ja aren't related to any configurations of uim.

IMO, we should restrict number of instances only when there is good reason to do.
Comment 4 Muneyuki Noguchi 2012-10-28 08:40:17 UTC 
Moved to https://github.com/uim/uim/issues/13

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.