Re: text fields in app don't allow input when running Cygwin X

[KM <info4km at yahoo dot com>]

I don't think this ever went thru


----- Original Message -----
Sent: Thursday, April 11, 2013 12:19 PM
Subject: Re: text fields in app don't allow input when running Cygwin X

one more time - since I got a delivery failure
KM

 
----- Original Message -----
Sent: Thursday, April 11, 2013 8:44 AM
Subject: Re: text fields in app don't allow input when running Cygwin X

Just to give it a try, I added the  -Dawt.toolkit=sun.awt.motif.MToolkit , but when I run it I get an unsatisfied link error (see below).  
 
java.lang.UnsatisfiedLinkError: sun.awt.motif.MToolkit.init(Ljava/lang/String;)V
        at sun.awt.motif.MToolkit.init(Native Method)
        at sun.awt.motif.MToolkit.<init>(Unknown Source)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at java.lang.Class.newInstance0(Unknown Source)
        at java.lang.Class.newInstance(Unknown Source)
        at java.awt.Toolkit$2.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.awt.Toolkit.getDefaultToolkit(Unknown Source)
        at java.awt.Window.getToolkit(Unknown Source)
        at java.awt.Window.init(Unknown Source)
        at java.awt.Window.<init>(Unknown Source)
        at java.awt.Frame.<init>(Unknown Source)
        at java.awt.Frame.<init>(Unknown Source)
        at com.zerog.ia.installer.LifeCycleManager.g(DashoA8113)
        at com.zerog.ia.installer.LifeCycleManager.h(DashoA8113)
        at com.zerog.ia.installer.LifeCycleManager.a(DashoA8113)
        at com.zerog.ia.installer.Main.main(DashoA8113)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.zerog.lax.LAX.launch(DashoA8113)
        at com.zerog.lax.LAX.main(DashoA8113)
 
Thanks for any help
KM
  

________________________________

Sent: Monday, April 8, 2013 3:48 PM
Subject: Re: text fields in app don't allow input when running Cygwin X
  
I saw some responses to my questions in the mailing list archives (did not receive any responses in email - should I have?).   It is an InstallAnywhere application with our custom code/classes for the screens.  So the IA SW may be what has issues, so I may not be able to do anything about this.  I just wanted to ask the question.    We are using an old version of IA.   I tried to add the -Dawt.toolkit=sun.awt.motif.MToolkit ... couldn't really get it to work.  
 
I am still trying though!  Any other insight, please let me know.
KM
  

________________________________

Sent: Monday, March 25, 2013 2:39 PM
Subject: text fields in app don't allow input when running Cygwin X
  
I have an application that I have always compiled on Linux and then invoked via X Windows with my installed Cygwin X.  Basically use a shortcut to startwin.exe (full command is  C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe ).  This always started my X server in the background  (no root window, or invisible root window), and still does.  All I had to do is log into my server, export my DISPLAY and start the app.

However I have recompiled my application with java 7 and now all of the radio buttons, buttons, scrollbars, and checkboxes, etc.  all still work as before.  The only thing that does NOT work is a text field.  I can not get the focus of the mouse in there, nor can I change or enter any data in those fields.  

When I start Cygwin x from the Cygwin xterminal in a windowed env (e.g. starx from command line), and export my DISPLAY on the server, the application works, but is contained within the root window.  I never had to do it this way before and it looks slightly different, no separate window borders etc.

We also use Reflection for an X server - that seems to run the recompiled application fine.

Any ideas?  Also I apologize if I'm not saying this quite right! Thanks for any help.  If you need more info let me know.
KM

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/