Bug 199547 - history is NOT updated while changing tables from scim-setup
Summary: history is NOT updated while changing tables from scim-setup
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: scim
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: SCIM
TreeView+ depends on / blocked
 
Reported: 2006-07-20 10:01 UTC by A S Alam
Modified: 2013-07-03 00:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-08-01 03:13:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Image showing HISTORY (71.85 KB, image/png)
2006-07-25 13:26 UTC, A S Alam
no flags Details

Description A S Alam 2006-07-20 10:01:31 UTC
Description of problem:
while Add/remove tables from scim-setup and run 'scim-setup' command, then
table is Add/removed from scim-menu, but History Above the menu is not update
ex:

Version-Release number of selected component (if applicable):


How reproducible:
scim-1.4.4-24.fc6
scim-bridge-gtkimm-0.2.4-1.1.fc6

Steps to Reproduce:
1. select scim table (Hindi-inscipt) (so that it added to history)
2.  start typing 
3. open scim-setup
4. uncheck a table (Hindi-inscript)
5. Apply and scim-restart
  
Actual results:
table is present in History, but also you can select and type with Hindi-inscript

Expected results:
table should Remove from History as table is removed from History

Additional info:

Comment 1 Jens Petersen 2006-07-25 11:23:36 UTC
What do you mean by "history"?

Comment 2 A S Alam 2006-07-25 13:26:27 UTC
Created attachment 132980 [details]
Image showing HISTORY

Comment 3 Jens Petersen 2006-08-01 03:13:40 UTC
I think this not a bug of the "history" (aka recently used IMEs list) but
a limitation of current scim: basically it needs to be restarted for
the currently installed IMEs to be correctly reflected in the menu.
I think once scim looks an IME module it keep it in memory.
I expect this to improve in scim2.


Note You need to log in before you can comment on or make changes to this bug.