headers
Paul | 18 Aug 12:33

XIM and mono-winforms-2.0

Hi,

What do I need to do to get XIM working with winforms? I've built
2.0preview1 (from the tarballs) and that seems fine. When I run a
winform app from a terminal, I get a line "Can't find XIM" (or something
similar) which then causes any input to get messed up (press 7 and
that's the only thing that appears in any text box irrespective of what
you type).

I have canna installed and running, but still no go. Same problem.

It's important that this gets fixed otherwise there are going to be a
lot of winforms apps running on all platforms which are just bust.

TTFN

Paul
--

-- 
Sie können mich aufreizen und wirklich heiß machen!

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Permalink | Reply |
headers
Atsushi Eno | 18 Aug 14:47

Re: XIM and mono-winforms-2.0

Without precise information on what message was actually output, which
IM engine you actually used (env | grep XMODIFERS) etc., it is almost
impossible to fix something from your message. canna itself is of course not
an xim implementation.

winforms/XIM stuff is working without any problem here, and I have
never heard of any problem as of now.

Atsushi Eno

> Hi,
>
> What do I need to do to get XIM working with winforms? I've built
> 2.0preview1 (from the tarballs) and that seems fine. When I run a
> winform app from a terminal, I get a line "Can't find XIM" (or something
> similar) which then causes any input to get messed up (press 7 and
> that's the only thing that appears in any text box irrespective of what
> you type).
>
> I have canna installed and running, but still no go. Same problem.
>
> It's important that this gets fixed otherwise there are going to be a
> lot of winforms apps running on all platforms which are just bust.
>
> TTFN
>
> Paul
>   
> ------------------------------------------------------------------------
>
(Continue reading)

Permalink | Reply |
headers
Paul | 18 Aug 21:00

Re: XIM and mono-winforms-2.0

Hi,

> Without precise information on what message was actually output, which
> IM engine you actually used (env | grep XMODIFERS) etc., it is almost
> impossible to fix something from your message. canna itself is of course not
> an xim implementation.

[paul <at> PB3 ~] env | grep XMODIFIERS
XMODIFIERS=@im=SCIM

[paul <at> PB3 ~] cd mwf-designer
mkdir -p build
cp deps/*.dll build
cp deps/*.mdb build
cd build && mono --debug mwf-designer.exe
Could not get XIM

All text entry boxes show whatever key was pressed first.

Using fedora rawhide, mono/libgdiplus 2.0 preview 1.

HTH

TTFN

Paul
--

-- 
Sie können mich aufreizen und wirklich heiß machen!

(Continue reading)






Permalink
| Reply
| 



  


  

  








headers


Atsushi Eno
 | 
19 Aug 11:39





Re: XIM and mono-winforms-2.0


Hello,

> Hi,
> 
>> Without precise information on what message was actually output, which
>> IM engine you actually used (env | grep XMODIFERS) etc., it is almost
>> impossible to fix something from your message. canna itself is of course not
>> an xim implementation.
> 
> [paul <at> PB3 ~] env | grep XMODIFIERS
> XMODIFIERS=@im=SCIM
> 
> [paul <at> PB3 ~] cd mwf-designer
> mkdir -p build
> cp deps/*.dll build
> cp deps/*.mdb build
> cd build && mono --debug mwf-designer.exe
> Could not get XIM
> 
> All text entry boxes show whatever key was pressed first.
> 
> Using fedora rawhide, mono/libgdiplus 2.0 preview 1.

Hrm, I set my scim to use canna and ran MWF app, but since
my environment is fine and does not result in "Could not get XIM",
I couldn't reproduce this bug (I have no idea how to break XIM support
safely). So far, I assume it is your environment that is broken.
All the XIM initialization sequence is written in
EnsureLayoutInitialized() in
mcs/class/Managed.Windows.Forms/X11Keyboard.cs.

(Continue reading)






Permalink
| Reply
| 



  


  

  








headers


Paul
 | 
22 Aug 00:07





Re: XIM and mono-winforms-2.0


Hi,

> Finally, as a workaround you can set environment XMODIFIERS=dummy to
> avoid call to XOpenIM() which is likely breaking your mono/mwf
> environment.
> We cannot introduce any workaround for you, as we cannot avoid call to
> XOpenIM() while everything looks fine.

It looks like LC_CTYPE en_GB.UTF8 doesn't work. en_US.UTF8 is fine
though.

TTFN

Paul
--

-- 
Sie können mich aufreizen und wirklich heiß machen!



_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list






Permalink
| Reply
| 



  


  

  








headers


Atsushi Eno
 | 
22 Aug 11:00





Re: XIM and mono-winforms-2.0


Hello,

> Hi,
> 
>> Finally, as a workaround you can set environment XMODIFIERS=dummy to
>> avoid call to XOpenIM() which is likely breaking your mono/mwf
>> environment.
>> We cannot introduce any workaround for you, as we cannot avoid call to
>> XOpenIM() while everything looks fine.

I reviewed my code and noticed that XOpenIM() was actually called even
when XSetLocaleModifiers() results in failure. So, my code did not
realize my expectation. I've checked in a fix to both trunk and 2.0
branch, so please retry it.

> It looks like LC_CTYPE en_GB.UTF8 doesn't work. en_US.UTF8 is fine
> though.

That rather sounds like you have some valid setup for en_US.UTF8
but not for en_GB.UTF8.

Atsushi Eno






Permalink
| Reply
| 



  


  

  








headers


Paul
 | 
23 Aug 13:09





Re: XIM and mono-winforms-2.0


Hi,

> >> Finally, as a workaround you can set environment XMODIFIERS=dummy to
> >> avoid call to XOpenIM() which is likely breaking your mono/mwf
> >> environment.
> >> We cannot introduce any workaround for you, as we cannot avoid call to
> >> XOpenIM() while everything looks fine.
> 
> I reviewed my code and noticed that XOpenIM() was actually called even
> when XSetLocaleModifiers() results in failure. So, my code did not
> realize my expectation. I've checked in a fix to both trunk and 2.0
> branch, so please retry it.

That's got it working :-). It's still reporting that it can't find XIM
though...

> > It looks like LC_CTYPE en_GB.UTF8 doesn't work. en_US.UTF8 is fine
> > though.
> 
> That rather sounds like you have some valid setup for en_US.UTF8
> but not for en_GB.UTF8.

Possibly, however as the likes of OOo and Scribus (plus a pile of other
apps which check LC_CTYPE) are not reporting a problem, I've a feeling
it's more down to mono than my set up.

TTFN

Paul
--

-- 

(Continue reading)






Permalink
| Reply
| 



  


  

  


















  





    



Gmane