I didn't see any replies to this, so I'm resending it. I intend to look at the sources myself, but I probably won't have the opportunity until this weekend... > It seems that something is still not quite right with the way in which > POSE > saves my .psf sessions. Here is the behavior, as well as how to reproduce > it. > > 1. Fire up POSE 3.0a3 on NT. (a1 and a2 also seem broken in the same > manner.) > 2. Set preferences to "never save session" > 3. Create a new: Palm III + matching rom > 4. Once the new device finishes resetting, save the session to .\POSE > Sessions\III.psf > 5. Right click, select "new" and create a new: Palm IIIx + matching rom > 6. Save this session as IIIx.psf > 7. Close POSE. > > At this point, double-clicking either .psf file launches POSE with the > correct session. However, now try the following: > > 8. Start POSE and select new: Palm V + matching rom > 9. Quit POSE -without- saving the session. > > Now double-click either III.psf or IIIx.psf and notice that instead of > loading the correct session, they both initialize POSE as a new Palm V. > > > > ---------- > Owen G. Emry > Noblestar Systems Corp. > Mobile Computing Practice > [EMAIL PROTECTED] > > > > > ---------- > Owen G. Emry > Noblestar Systems Corp. > Mobile Computing Practice > [EMAIL PROTECTED] > >
