I reported about the bug that spoils the configuration after an update. But as I said before that's a bug in Eclipse 3.0.1 itself, so we shouldn't blame PalmSource for it. The bug should be gone with Eclipse 3.0.2, so once you've updated for the first time.
I agree to the resource editor issue... This thing shouldn't have been released. I'm not so in trouble like you, because fortuneately I don't let the re create the id's, but there are some strangelets in it. For example, I click on the visible part of a modal form and change it's ID, but that won't change the form id (I have to click on the blank part in the form and then change it). Or, if I set the list id of a popup trigger, next time I click on it the id is 0 again. > If you decide to update PODS anyway - make sure you make a backup > of your old Resource Editor first. I second that. It would be a good idea to have a bug reporting system accessible to developers here for PODS. That would be much more constructive than posting to this mailing list. I really like PODS and the people who develop it, but PLEASE @PalmSource don't publish software that you didn't fully test! Or let us developers test betas and give us access to a bug tracking system. I'd be the first to sign up for it. It's a pain to post bugs here, it sounds picky to post about every little bug here in this mailing list. You have a strong cummunity, please make use of it. Kind regards Benjamin -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
