Bug 199383 - pinyin help property not showing in aux
pinyin help property not showing in aux
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: scim-pinyin (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Qian Shen
: i18n
Depends On:
Blocks: SCIM
  Show dependency treegraph
 
Reported: 2006-07-19 01:22 EDT by Lawrence Lim
Modified: 2015-10-25 21:54 EDT (History)
4 users (show)

See Also:
Fixed In Version: scim-pinyin-0.5.91-11.3.fc6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-07-30 21:20:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lawrence Lim 2006-07-19 01:22:17 EDT
Description of problem:
Have not seen this feature in action. However, I dont see much difference in the
input after enabling it.

Version-Release number of selected component (if applicable):
scim-pinyin-0.5.91-11.1.fc6

How reproducible:
Always

Steps to Reproduce:
1.in scim setup, enable (checked) 'Show Pinyin Property in the tool bar'
2.reload Desktop
3.
  
Actual results:
shows an additional icon in the aux window

Expected results:


Additional info:
Comment 1 Qian Shen 2006-07-20 06:01:27 EDT
Gtk2 update from 2.8 in fc5 to 2.10 in fc6 from fc6, which cause some problems
in UI. Remove "g_object_set ( renderer_num, "alignment", 0.5, NULL);" in
add_column() . 

cvs diff -r 1.2 scim-pinyin-helper.patch
Index: scim-pinyin-helper.patch
===================================================================
RCS file: /cvs/dist/rpms/scim-pinyin/devel/scim-pinyin-helper.patch,v
retrieving revision 1.2
retrieving revision 1.3
diff -r1.2 -r1.3
211c211
< @@ -0,0 +1,1124 @@
---
> @@ -0,0 +1,1123 @@
1067d1066
< +  g_object_set ( renderer_num, "alignment", 0.5, NULL);
Comment 2 Lawrence Lim 2006-07-30 21:20:52 EDT
Confirmed fixed. Can see it in the aux window now.

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