Re: No Luck: JSwat & KToolbar (J2ME)
Nathan Fiedler <[email protected]> Mon, 03 Mar 2003 16:53:04 -0700
| Newsgroups | gmane.comp.java.jswat.user |
|---|---|
| Organization | Blue Marsh Softworks |
| Message-ID | <[email protected]> |
I don't know anything about J2ME, but perhaps this problem is related to bug 431. That bug states that the KVM (as found in the CLDC) will hang when JSwat connects to it in graphical mode. However, console mode seems to work better. You might want to try that (launch jswat with "-console" as the first argument. n Stevens, Brigham wrote: > I’ve had no luck getting JSwat (2.13, and earlier versions) working with > the Wireless Toolkit… > > I launch the MIDlet application from the ktoolbar using the debug menu > option, which launches the VM with all the correct(? I think correct!) > debug options… Connecting with JSWat basically just makes JSwat and the > emulator hang. > > I am using a slightly older version of KToolbar – Which is based on JDK > 131 I believe. Since Ktoolbar has a debug menu option, I don’t think I > need to follow the directions posted for KVM debugging… But then again, > maybe that is the problem? > > I am running JSwat 2.13 under JDK140_01. I will provide more information > from home later… > > Thanks for any insights.. > > --brigham > > > ------------------------------------------------------------------------ > > _______________________________________________ > jswat-user mailing list > [email protected] > http://www.bluemarsh.com/mailman/listinfo/jswat-user