[HS] Re: Autosave on item action
"chrisant_wa" <[email protected]> Wed, 09 Feb 2011 20:39:24 -0000
| Newsgroups | gmane.comp.handhelds.palm.handyshopper |
|---|---|
| Message-ID | <[email protected]> |
--- "mad_ady" <mad_ady@...> wrote: > However, I have just upgraded my PDA from Windows Mobile > 6.1 to 6.5.3 and I keep having this problem sometimes: > whenever I close the program and reopen it I get a warning > telling me the database was not closed properly and it > loads what was previously saved. > This doesn't happen all the time, but it usually happens > when I am in the store ready to shop and notice that my > list is usually empty. This is not nice (happened 4 > times in the last month). > > I am not using a special program to kill applications > instead of sending them in the background, What device is this? For example, all HTC devices have a built in special program that kills applications instead of sending them in the background. There will be an option to disable that somewhere in the HTC control panel settings. Some other manufacturers have similar "enhancements". > but I am ocasionaly rebooting my PDA (other processes > make it hang). I know there is a manual save button (that > works fine), just that sometimes I forget to click on it > while making changes, and this spells disaster. HS has always automatically saved whenever it is sent to the background, and whenever the screen is powered on while HS is the active app. So unless you are rebooting while HS is open, the rebooting should not be affecting HS. I bet your device has taken over the [X] button and is killing apps without your knowledge, and that this is leading to the problem. Look into turning off that "feature" of your device. > I would like to ask for a feature request - a user > selectable option to enable autosave when a change is > done to the database (either an item is checked/unchecked, > or something is added or changed). It might lower > performance, but it my case it would bring sanity back :) > > Is my proposal something feasible, or is there a known > workaround for my problem? That could result in HS hanging for several seconds after every action you perform (tiny databases might hang only for half a second, very large databases could hang for 30+ seconds).