File: _Bugs.txt

package info (click to toggle)
pose 3.0a3-3
  • links: PTS
  • area: contrib
  • in suites: potato
  • size: 15,500 kB
  • ctags: 20,548
  • sloc: ansic: 72,579; cpp: 50,198; perl: 1,336; python: 1,242; sh: 363; makefile: 290
file content (43 lines) | stat: -rw-r--r-- 2,056 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
========================================================================
Bug List for the Palm OS Emulator
Copyright 1998-1999 Palm Computing, Inc.

Please send bug reports, comments, suggestions, etc. to devsupp@palm.com
========================================================================

This document contains the list of known significant bugs in the Palm
OS Emulator.  This list is not complete -- many insignificant or
low-runner bugs have been omitted just to keep up the signal to noise
ratio.

*	Neil needs to receive cmdInitDatabase when his app is installed.

*	You can't reliably change the time with the Preferences App.  The
	time is generally synched with the host PC time.

*	It's not a good idea to load applications while the Launcher (the
	"Applications" application) is running.  If the program you're
	loading doesn't already exist, it won't show up in the list of
	installed application until you quit and restart Launcher.  If the
	application you're loading _does_ already exist, the Launcher won't
	refresh it's list, and will end up with a stale reference to the
	version you'd just replaced, leading to a Launcher crash.

*	We've seen one case where MacEmulator will draw the LCD area with a
	white background in single-scale mode instead of green.  The cause
	of this problem appears to be with an out-of-date driver for a video
	acceleration board.  Unless this is an issue for you, we probably
	won't try to figure out a workaround.

*	When working with an external debugger, make sure the ROM is awake
	(and not sleeping with a blank screen).  Otherwise, communication
	between the two applications will not occur.

*	For performance reasons, Poser currently never validates the
	emulated PC.  Thus, if the PC every becomes invalid (perhaps because
	theemulated stack was overwritten and a corrupted return address was
	moved into the PC), Poser may crash when trying to use it to fetch
	the next opcode.

*	When using NetLib redirection, NetLibSelect doesn't support the
	use of sysFileDescStdIn or sysFileDescStdOut.