Part of the clarification was interpreted as HTML...here's try #2..

Part of the clarification was interpreted as HTML...here's try #2..:
[ Follow Ups ] [ Post Followup ] [ Dioxide's CForum ]

Posted by Isildur on December 28, 2000 at 13:37:57:

In Reply to: Pueblo users - tell me if you've seen this bug... posted by Isildur on December 28, 2000 at 12:11:13:

It seems the problem isn't with anchors, since I got the previous example I gave to work.

Pueblo seems to pick and choose which text it wants to parse. When I entered the standard action:

#action {^<%0hp %1m %2mv>} {#var {hp} {%%0}; #var {ma} {%%1}; #var {mv} {%%2}}

It will update -some- of the times the prompt comes across my screen, but not all. It seems to like it when CF generates the prompt (i.e. when day changes to night, the weather changes, etc.) but not when -i- generate it (by pressing enter, casting a spell, etc.)

So unless I'm missing something, which is entirely possible, Pueblo's implementation of tintin commands is pretty damn sketchy. That's a real shame considering how much nicer looking (and overall better) is is than WinTin.

Follow Ups:

Post a Followup

Name:
E-mail:
Subject:
Comments:	> It seems the problem isn't with anchors, since I got the previous example I gave to work. > Pueblo seems to pick and choose which text it wants to parse. When I entered the standard action: > <text>#action {^<%0hp %1m %2mv>} {#var {hp} {%%0}; #var {ma} {%%1}; #var {mv} {%%2}}</text> > It will update -some- of the times the prompt comes across my screen, but not all. It seems to like it when CF generates the prompt (i.e. when day changes to night, the weather changes, etc.) but not when -i- generate it (by pressing enter, casting a spell, etc.) > So unless I'm missing something, which is entirely possible, Pueblo's implementation of tintin commands is pretty damn sketchy. That's a real shame considering how much nicer looking (and overall better) is is than WinTin.

[ Follow Ups ] [ Post Followup ] [ Dioxide's CForum ]