Thanks to all for the help.. I am close enough now to taste it. I had DebugPrefs, but I also added in DotDotTwo, which did the trick. Apparently my graffiti skills suck. Now I can bring up the debugger window, but the app will never finish downloading to the handspring... Ick.
But, in a cowardly attempt to avoid debugging on actual hardware, does anyone know of any differences offhand that would make a palm & handspring act differently in code that did the following: create a new list with LstNewList populate it set it as the popup list for a Table with a popup trigger in the cell repeat several times. I get the situation where all but the last list doesn't show up at all, only getting an arrow which disappears when I tap on it (no list appears). The last list in the table tends to work fine. Very odd. Again, this problem does not occur in the emulator (running a Palm VII rom), or on my kyocera 6035, just my friend's visor prism and my own visor neo. I'm beginning to dislike handspring. Thanks as always for all the help! On 7/22/02 3:16 PM, "Kevin OKeefe" <[EMAIL PROTECTED]> wrote: > Sacrificing the lamb will only work if you walk around in circles chanting the > appropriate mantras.... > > Handsprings are a little funny. > > You can either find and download the application DebugPrefs which will force > your handspring debug in USB, or you can enter shortcut .. and then before > entering the 2, hold the up button down and keep it held while entering the > two and keeping it held until the debugger connects. > > Hope this helps, > Kevin > > -----Original Message----- > From: Lally Singh [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 22, 2002 11:40 AM > To: Palm Developer Forum > Subject: I'm an idiot (was: Re: Remote Debugging to a handspring (I have > DebugPrefs)) > > > I've got the converter, I've plugged it all in. Now CW sees my > PalmConnect USB adaptor, and I started using the "shortcut" stroke > as displayed in Codewarrior's Palm Help. I *think* there's > some communication going on, but I'm not sure of that, and no > matter what, I can't debug the app. I type in shortcut..2 > and the visor beeps once, and I press enter to let CW know > that I typed in the shortcut, and... it times out. When > I try to see the debug log, CW times out telling me that > some other app is using the serial port. I've turned off > the serial monitor and the palm desktop extension. > > There has to be something really simple I'm missing here. Do > I need to sacrifice a lamb? I'm in farmer country, so the lamb > can be easily acquired. > > Thanks in advance! > > On 7/20/02 10:29 PM, "Ben Combee" <[EMAIL PROTECTED]> wrote: > >> In article <91585@palm-dev-forum>, [EMAIL PROTECTED] says... >>> >>> Hey all. I just got my first app ready to go, and it runs >>> great on my Palm, but it has a fatal exception on my >>> friend's handspring. So, I bought a handspring to do >>> some remote debugging on. This is CW 7, Mac OS 9, and a >>> Handspring neo trying to work together. I setup DebugPrefs, >>> reset, and type in /..2. I get the little shortcut bar >>> when I hit the /, but upon typing the "..2", nothing happens. >>> CW times out and I can't connect. I've got CW setup to >>> talk over the "Internal Modem" (sounds wrong, but the >>> only other option was the infrared port, which sounds >>> wronger :-). >>> >>> Any help in getting this debugging connection working would >>> be great. Thanks all. >> >> To debug to a Handspring device from a Macintosh, you need a USB-to- >> Serial adapter (Keyspan and Palm both sell these), then you need a >> serial cradle for the Handspring. USB debugging to the Visor is only >> supported on Windows. > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
