Jump to content


Photo

Journal error


  • Please log in to reply
4 replies to this topic

#1 Quitch

Quitch

    Perfection

  • Modder
  • 1132 posts

Posted 19 September 2002 - 02:32 PM

WeiDU doesn't seem to spot and flag missing JOURNAL strings.

#2 weimer

weimer
  • Member
  • 1569 posts

Posted 22 September 2002 - 11:23 AM

Cannot reproduce without a testcase. Here's a D file:

BEGIN FOO

IF ~~ THEN BEGIN s0
  SAY ~Hello~
  IF ~~ THEN REPLY ~Goodbye~ JOURNAL EXIT
END

And WeiDU says:

[c:\src\weidu\weidu.asm.exe] WeiDU version 75
[C:\Program Files\Black Isle\BGII - SoA/chitin.key] loaded, 590551 bytes
[C:\Program Files\Black Isle\BGII - SoA/chitin.key] 182 BIFFs, 41793 resources
[C:\Program Files\Black Isle\BGII - SoA/dialog.tlk] loaded, 9649307 bytes
[C:\Program Files\Black Isle\BGII - SoA/dialog.tlk] 79991 string entries
[test.d] PARSE ERROR at line 5 column 38-41
Near Text: EXIT
        syntax error
ERROR: problem parsing D file [test.d]: Parsing.Parse_error

ERROR: Parsing.Parse_error

Please post something that passes with a missing journal string.

#3 Quitch

Quitch

    Perfection

  • Modder
  • 1132 posts

Posted 23 September 2002 - 01:19 PM

Sorry, I mean:

JOURNAL @65

where @65 does not exist.

#4 weimer

weimer
  • Member
  • 1569 posts

Posted 23 September 2002 - 03:13 PM

test.d:

BEGIN FOO

IF ~~ THEN BEGIN s0
  SAY ~Hello~
  IF ~~ THEN REPLY ~Goodbye~ JOURNAL @65 EXIT
END

output:

tani-no-yuri:/cygdrive/c/src/weidu$ ./weidu.asm.exe test.d
[c:\src\weidu\weidu.asm.exe] WeiDU version 75
[C:\Program Files\Black Isle\BGII - SoA/chitin.key] loaded, 590551 bytes
[C:\Program Files\Black Isle\BGII - SoA/chitin.key] 182 BIFFs, 41793 resources
[C:\Program Files\Black Isle\BGII - SoA/dialog.tlk] loaded, 9649307 bytes
[C:\Program Files\Black Isle\BGII - SoA/dialog.tlk] 79991 string entries
[test.d] parsed
Adding FOO to internal list of available DLGs
ERROR: No translation provided for @65
ERROR: cannot resolve strings in FOO
ERROR: Cannot postprocess FOO
ERROR: problem processing D files: Not_found

ERROR: Not_found

Looks like it is noticing the @65 to me. Please post a test case that fails. :-)

I believe that you are encountering the problem, but unless I can reproduce it locally I cannot fix it.

#5 -jcompton-

-jcompton-
  • Guest

Posted 23 September 2002 - 04:27 PM

I believe using the action (AddJournalEntry(), I believe) is going to be superior than the JOURNAL dialogue action call, because by using AddJournalEntry, you'll be able to use TP2 REPLACE and, thus, be able to erase it later.