TinTin++ Mud Client The TinTin++ message board

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
TinTin++ Mud Client

TinTin++ 2.01.0 (Beta)

 
Post new topic   This topic is locked: you cannot edit posts or make replies.    The TinTin++ message board Forum Index -> Announcements
View previous topic :: View next topic  
Author Message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Sat Mar 02, 2013 11:38 pm    Post subject: TinTin++ 2.01.0 (Beta) Reply with quote

http://tintin.sf.net/download/tintin-beta.tar.gz

Code:

event.c        Added the VARIABLE UPDATE <VAR> event.

cursor.c       Added stripping of semi-colons when auto tabbing.

configure.in   Better error handling by Slysven.


Also fixed the issues with #cursor PASTE BUFFER and #line log.
Back to top
View user's profile Send private message Send e-mail
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Sat Aug 10, 2013 5:40 pm    Post subject: Reply with quote

I haven't been around much lately so I'd like to thank everyone who helped out answering questions on the forum, much appreciated! Ecstatic

And I'm hoping to have something to beta test soon. Smile
Back to top
View user's profile Send private message Send e-mail
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Mon Aug 26, 2013 7:42 pm    Post subject: Reply with quote

Code:

parse.c        Added support for nesting using the . argument.

mapper.c       Added map_search_compile option, increasing search speed.

list.c         Added #list TOKENIZE option.

cursor.c       Fixed the cursor PASTE BUFFER option.


With this update #var list.item x; is equivalent to #var list[item] x.

Map searches are compiled and optimized, making them significantly faster on large maps.

The tokenize option breaks up a string into a character list. This is an alternative to using #parse. There's no untokenize option as of yet.
Back to top
View user's profile Send private message Send e-mail
balthus



Joined: 07 Jul 2009
Posts: 39

PostPosted: Thu Aug 29, 2013 5:05 am    Post subject: Reply with quote

Spotted a small bug in the mapper. Down exits are not showing in the default map view.

2.00.9:
Code:

                                             +
                                           [#]
                                           -


2.01.0 beta:
Code:

                                             +
                                           [#]

Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Thu Aug 29, 2013 5:45 pm    Post subject: Reply with quote

Thanks, I've uploaded a new beta with this bug fixed.
Back to top
View user's profile Send private message Send e-mail
balthus



Joined: 07 Jul 2009
Posts: 39

PostPosted: Sat Aug 31, 2013 3:22 am    Post subject: Reply with quote

That is fixed, thanks.

Found another issue though, getting:

#SHORTEST PATH: UNKNOWN ERROR.

on some #MAP find paths.

I have checked with the same map/paths in 2.00.9 and this issue isn't happening.
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Sat Aug 31, 2013 7:56 am    Post subject: Reply with quote

Can you give me an example map and an example search that fails?
Back to top
View user's profile Send private message Send e-mail
balthus



Joined: 07 Jul 2009
Posts: 39

PostPosted: Sun Sep 01, 2013 5:59 am    Post subject: Reply with quote

PM'd
Back to top
View user's profile Send private message
karvec



Joined: 16 Jul 2010
Posts: 50

PostPosted: Tue Sep 10, 2013 8:39 am    Post subject: Reply with quote

I was using my chatlog, i.e. snippet
Code:
#alias {-cl} {
        #format {datestamp} {%t} {%Y-%m-%d};
        #format {timestamp} {%t} {[%H:%M] };
        #line log /home/karvec/mud/logs/$datestamp.log {$timestamp\};
        #line log /home/karvec/mud/logs/$datestamp.log;


to log chat in a specific date-named log file, however i keep getting "FILE NOT FOUND" with the new beta.

If I pass it as

Code:
#line log {/home/karvec/mud/logs/{$datestamp}.log};
it works, but it makes the filename in brackets.

Is there something I can do to fix this?

Here's the debug output.

Code:
#DEBUG ACTION {{^((A ghostly form of )?[A-z0-9@]+ (<HM-[A-z]+>:|-=\(OMP\)=-|LTs?         
\([\[\]0-9A-z\[\], ]+\)|tells?( you)? \(?[A-z0-9,@]+\)?:|g?shouts:)|\[(Clan|PARTY|Auction
)\] [A-z\(\) ]+:)}}                                                                     
[18] -cl                                                                                 
#DEBUG ALIAS {-cl} {}                                                                   
[02] format {datestamp} {%t} {%Y-%m-%d}                                                 
[02] format {timestamp} {%t} {[%H:%M] }                                                 
[02] line log {/home/karvec/mud/logs/{$datestamp}.log} {$timestamp\}                     
[02] line log {/home/karvec/mud/logs/{$datestamp}.log}                                   
[18] -xchatlog                                                                           
#DEBUG ALIAS {-xchatlog} {}                                                             
[02] class {xchatlog} {open}                                                             
#CLASS {xchatlog} HAS BEEN OPENED.                                                       
[02] action {^{\S}} {#class {xchatlog} {kill}} {99}                                     
#OK. {^{\S}} NOW TRIGGERS {#class {xchatlog} {kill}} @ {99}.                             
[02] action {{^(\s)*$}} {#class {xchatlog} {kill}} {99}                                 
#OK. {{^(\s)*$}} NOW TRIGGERS {#class {xchatlog} {kill}} @ {99}.                         
[02] action {^{\s{1,40}\S}} {-cl}                                                       
#OK. {^{\s{1,40}\S}} NOW TRIGGERS {-cl} @ {5}.                                           
[02] class {xchatlog} {close}                                                           
#CLASS {xchatlog} HAS BEEN CLOSED.                                                       
[02] bell                                                                               
You tell Mythkeeper: test                                                               
#DEBUG ACTION {{^(\s)*$}}                                                               
[02] class {xchatlog} {kill}                                                             
#CLASS {xchatlog} HAS BEEN KILLED.


That's the successful version that produces a files like "{2013-09-10}.log", the unsuccessful just spams "#FILE NOT FOUND" above the #line log...

I'm also experiencing the same problem as Balthus, as well as rooms that are set with a high room weight are not being evaluated properly. (I.e. room weight is 1000, still running through it to make a total of 6 steps instead of 15)

**EDIT** I used the 2.01.0 code in 2.00.9, and it worked perfectly (before, 2.00.9 wasn't actually logging a line.) So not sure what's going on, but I'm happy.
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Tue Sep 17, 2013 7:52 pm    Post subject: Reply with quote

I've updated the beta with a fix for the #map find issues.

$datestamp.log is no longer valid syntax as it's the equivalent of: $datestamp[log]

I'm trying to mimic Lua to some degree, though it is annoying in cases like these.

You could use:

Code:

#alias {-cl} {
        #format {datestamp} {%t} {%Y-%m-%d.log};
        #format {timestamp} {%t} {[%H:%M] };
        #line log /home/karvec/mud/logs/$datestamp {$timestamp\};
        #line log /home/karvec/mud/logs/$datestamp;


Or alternatively:

Code:

#var logextension {.log}
#line log /home/karvec/mud/logs/$datestamp$logextension


Or alternatively:

Code:

#line escape {variables;escapes} #line log /home/karvec/mud/logs/$datestamp\.log


Or alternatively:

Code:

#var dot .
#line log /home/karvec/mud/logs/$datestamp${dot}log
Back to top
View user's profile Send private message Send e-mail
balthus



Joined: 07 Jul 2009
Posts: 39

PostPosted: Wed Sep 18, 2013 10:50 am    Post subject: Reply with quote

Map find fix works, thanks. Thumbs Up
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Sun Sep 29, 2013 1:58 pm    Post subject: Reply with quote

Code:

session.c      #session takes a filename as an additional argument, if the
               session succesfully connects the file will be read.

variable.c     Fixed #echo {%f} {5 / 3} handling.

cursor.c       Added #cursor get and #cursor set options.
Back to top
View user's profile Send private message Send e-mail
balthus



Joined: 07 Jul 2009
Posts: 39

PostPosted: Tue Oct 01, 2013 8:09 am    Post subject: Reply with quote

Getting a compile error in the latest version of the beta during "make":


Code:

..yadda...
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c variable.c
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c list.c
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c forkpty.c
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c cursor.c
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c memory.c
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c system.c
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c line.c
gcc -Wall  -D_GNU_SOURCE -DHAVE_CONFIG_H     -c tokenize.c
tokenize.c: In function ‘handleswitchtoken’:
tokenize.c:273:2: error: too few arguments to function ‘mathexp’
In file included from tokenize.c:28:0:
tintin.h:1249:13: note: declared here
make: *** [tokenize.o] Error 1
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Tue Oct 01, 2013 6:46 pm    Post subject: Reply with quote

Thanks, should be fixed now. Smile
Back to top
View user's profile Send private message Send e-mail
balthus



Joined: 07 Jul 2009
Posts: 39

PostPosted: Wed Oct 02, 2013 4:26 am    Post subject: Reply with quote

Yep, works again now.
Back to top
View user's profile Send private message
karvec



Joined: 16 Jul 2010
Posts: 50

PostPosted: Sun Oct 06, 2013 2:49 pm    Post subject: Reply with quote

Thanks Scandum for the syntax fix! Smile
Back to top
View user's profile Send private message
nya



Joined: 25 Jun 2012
Posts: 39

PostPosted: Mon Nov 11, 2013 6:10 am    Post subject: Reply with quote

Nice work! Testing things out, I've found:

#CURSOR {SET} shows some weird behavior for me, where the input position indicator (eg visually, not logically - if you, for example, typed stuff, it'd still be inserted in the right place!) moves to the right by a number of characters equal to whatever's in the paste buffer, rather than being based on what you gave as an argument to the #CURSOR {SET}.

I assume this is due to cursor.c:1111, which has strlen(gtd->paste_buf) instead of strlen(arg). Changing the former to the latter seems to have fixed the issue for me!

Also, the variable event is cool, but it looks like it fires before the variable changes and doesn't seem to pass any arguments. Is there any way to retrieve the variable's new value without any tricks (eg #delay)?
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Thu Nov 14, 2013 8:35 am    Post subject: Reply with quote

I think I reused the buffer paste code and forgot to change that section, nice catch. Smile

I changed the VARIABLE UPDATE event to report the variable name as %0, and the variable argument as %1.

This way both the old and new values are available.
Back to top
View user's profile Send private message Send e-mail
karvec



Joined: 16 Jul 2010
Posts: 50

PostPosted: Sun Nov 17, 2013 11:52 pm    Post subject: Reply with quote

Alright, when I try to #zap just once, it doesn't exit to the main session...

It throws a debug and terminates the program, here's the output.

Code:
DEBUG_STACK[000] = do_zap(0x1416910,0x142bde0)               
DEBUG_STACK[001] = [3k - Karvec] do_one_line()               
DEBUG_STACK[002] = substitute(0x1416910,0x14285c0,0x45897a,1)


Is it something I'm doing? Or is anyone else having this problem as well?
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Mon Nov 18, 2013 12:48 am    Post subject: Reply with quote

Looks like something triggers on zap. Can try doing it with #debug all on to see what is happening.
Back to top
View user's profile Send private message Send e-mail
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Mon Dec 30, 2013 12:19 pm    Post subject: Reply with quote

Code:

variable.c     Added better support for large variables.

memory.c       Added utility functions for infinite string support.


It should now be possible to use #read and #write with large variables, but certain operations will still result in crashes until I switch over all functions to use infinite string support.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic   This topic is locked: you cannot edit posts or make replies.    The TinTin++ message board Forum Index -> Announcements All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads
TinTin++ Homepage

Powered by phpBB © 2001, 2002 phpBB Group