I want my old graffiti back

[ptracker]

I have returned to the palm after a little break.
So I thought that I would get a Palm TX I quite like it, BUT I hate the new graffiti. Is there any way I can get the old Graffiti back?


Please any ideas?

Tracker

[sblop]

Hi. :-)
You can find the old version at www.info2us.dk/archive/palm
Copy it to the ram with resco exp, and reset.

In some cases it makes the TX crash more frequent.

So remember to take a backup.

/Benjamin

[Dick Tracy]

G1 will make your TX unstable.

[technical1]

Not mine. I use TealMover to get rid of one of the 2 Grafitti2 libraries. One of them you can't delete, the other you can, then immediately use the soft reset tool & assuming you have copied the needed files, voila- you will have G1. This is one of the only things I use TealMover for these days; Resco Explorer is so powerful, esp the new v3!

This delete one of the grafitti2 library files & soft reset process must be repeated whenever there is a hard reset, or a crash -

otherwise, it works fine on my TX.

[thenrik]

I've had no problems with G1 on my TX--hate G2. I installed it with FileZ. If you can't find the files on line, I could email them.

Tom

[FerdFerd]

So far as I know from the things I've read here and elsewhere, G1 on a TX causes crashes only when you are filling out a form, such as a URL in Blazer, and the text extends beyond the length of the available line. Then the TX is reported to crash.

So long as users are aware that this happens, using G1 should be fine. For some users, the condition causing the crash never occurs and they therefore don't experience crashes.

I haven't tried to use G1 on my device. I made peace with G2 and liked it fine, until a couple of months ago I began to use the ATOMIK keyboard through myKbd. I need to practice more, but I've been using that exclusively for text entry since then.

[technical1]

I think that the Blazer crash issue is more related to available db cache than grafitti itself, just that adding text will eat up avail dbcache; not 1000% sure - so if any can correct me, please do...

[braj]

I personally think the digitizer in the TX is a bit wonky with Grafitti, even if you go to G1 (which I tried and only crashed in Blazer). Using myKBD seems altogether the fastest way to enter text to me personally.

[ebonair]

I personally think the digitizer in the TX is a bit wonky with Grafitti, even if you go to G1 (which I tried and only crashed in Blazer). Using myKBD seems altogether the fastest way to enter text to me personally.


I would have to agree with that. I have used TealScript to emulate G1 for years now and it just doesn't quite work as well on the TX as it did on my Zodiac. I can still pick up my Visor and use G1 very quickly and accurately. On the TX I am constantly redrawing characters. I think some of this has to do with the quality of the digitizer because even the Zire 72, my accuracy was much better. I currently use myKbd which, although slower, is pretty accurate.

The perfect entry system? Mostly G1 and a *good* digitizer with two differences:
1. Recognize u and v without having to do a backwards stroke.
2. Recognize a dash automatically on the number side instead of a space

Single stroke is the way to go...

[cyberdude]

I was used to G1 and didn't like G2 at all (6 strokes to make a $ or # - don't remember which). I tried MessagEaseST, then settled on myKbd with the Atomik keyboard (I've since modified it to my own needs). I love mykbd - it is not aonly an excellent text entry app, but the macro features alone make it worthwhile (and they persist after the demo expires - hence the name of the other thread "Free macros for everyone ...").

[Cyker]

Agreed - Single stroke can't be beat ;)

[_Em]

$ is 2 strokes; # is 6 -- "|#|".

The one that always gets me is the _ key -- I keep on forgetting the key sequence right when I need it.

[Ou_Boet]

Generally I'm happy with G2. However, as mentioned before some of the new strokes are rediculously laborious and unintuitive. I'd like to see a G3 which combines the best of both. Keep a lot of the G2 "natural" strokes but ditch any two (or more) stroke chractors and replace with the G1.

OB