I need to see how that looks though

Made sure the height is always 150 min.... This would come out better with the portraits anyway, which are by default height 96

The outcome appears in order based on the calculation, eh?

77 looks very strange to me.... How could that height come out, I wonder....

DEBUG: y:1003; h: 77; c:1041

Temp line to get some more data, as I think there's something fishy going on here!

No difference.... I guess that was to be expected, but still

Let's try this....

Not yet sure....

Take Five, let's see what happens, eh?

I've set the y coordinate of the picture to the center of the textbox too

For starters i made sure the color is set to "white", as that may save me a lot of trouble

of course I should have checked that earlier

Oh, I made a vertical auto-center, eh?

It.... works... but I'm NOT happy, meow!

Take Four!

Which didn't end up in an out of memory this time (not that there was any reason to, but when it did throw that error, that reason was non-existent, as well... I I wonder)

And forgotten end

Another forgotten self

Take Three!

Okay NOW I should have that!

I fixed something else.... Now it had to be fixed anyway, but it was not what I though I had fixed.... (Stooooopid)

Let's hope I won't surpass 40 this time :-/

Take Two!

Cow! Use "self"... dork!

Take One

Forgive me my skepsis given what happened today... :-P

Does BoxPic what it has to do here?

Copyright note error

I need a break... Ok?

Calling it... for now.....

Several more repositories updated

Running

It appears to be working... again

Connection failure with GitHub

Note to self about BoxPics.nil -- I forgot about it, but it WILL save me a lot of trouble, so why not make use of that little file :)

Copyright and license blocks

Updated

and requiring 47 takes to get it done, is WAAAAY to much....

And tomorrow I've little time at my hands (which is normal on Sunday for me), so I'm not sure I'll be able to get much done then....

Of course you realize, that due to the big amount of time that was now wasted, I can't get to putting the actual text in

FINALLY

At least I see what I wanted to see... for now...

Take XLVII

Missing field

Take XLVI

Case Error

Take XLV

I've made sure that an empty string is also not accepted by the alternate font loader

Test XLIV

(All this trouble all to get a texbox on screen... And then to think I chose this road to SAVE time)

Picture code as I don't need it now, and it will be rewritten eventually anyway

Take XLIII

I ... think....

?

XLII

Illegal pairs reference usage

Asshole!

Take XLI

Well case header in field "Header" has been fixed

Don't you just hate it that Lua has no specific order for keys in tables?

Take XL

I hope this debug line can tell me why

Now it makes a very idiotic claim... A number is suddenly not a number, eh?

Take XXXIX

I think I fixed that, but as I'm not sure, let's do another test, eh?

Now the system throws an index 0.... Not that odd since Lua (and thus NIL as well) start arrays at 1, but I need to look why index 0 is called at all!

XXXVIII

some more code that I no longer need and which is now causing other (non-existent) errors

Take XXXVII

I've dummied the code... I can retrieve it if needed, but this was no longer very useful, at all... I think it's even better if I leave this as much as possible to BoxText itself now....

This is getting to a point that things do not really make much sense anymore... Rather than trying to make sense out of it I think I'd better dummy all this.

At last.... Well this is only a part of the issue, as I still got a way to go here

XXXVI

krijg toch allemaal de kol&egrav;re... val voor mijn part allemaal dood!

XXXV

AWFUL CODE STRAIGHT FROM THE BOILER ROOM OF HELL! I refuse to call this a "fix", but if it works, it works, and that's the only thing that REALLY matters!

And now the system starts talking bullcrap

Take XXXIV

This does not yet fix everything, but I'm on the road... at least....

I've linked this routine now to the Scenario loader....

I see I prepared a 'fake' GALE class to take care of the previous issue, but as I had so much to do and no way to test it, I forgot about it... Good that I see it now ;)

I've set up a portraits table in the TextBox class

The error at hand is a result of the fact that the scenario loader tries to load pictures over GALE, which was the Lua API engine used in LAURA and LAURA II. This is not compatible with BUBBLE and thus also not with NALA, and therefore that error... So at least we got something that is completely normal....

Indeed, now the error changed indicating something more happened now

Take XXXIII

Well, I guess this will do a few things right then

Links to a non-existent file, eh?

Take XXXII

Done some extra debug lines, hopefully they'll answer a few questions

All subtables are .... empty

Take XXXI

And a debug line has to tell me why that came is done

It says the required tag is missing....

That did fix a lot, but I still got a LOOOOONG way to go!

Take XXX

'nil' value

Case XXIX

Load the scenario script first, DUMMY!

Moving in... I think.... :-/

Take XXVIII

I've added some Trims

Things are not yet the way they should be, but I'm closing in.... Good

Take XXVII

I did mention that space appear to be added when two VMs communicate with each other... I wonder why, but I should make note of it....

I'm sure it's not yet 100% right, but hopefully things are more on my side now

%s was placed, but not in the required sprintf setups as was needed

Take XXVI

Let's redo that one

Take XXV

Let's link two variables together and see what'll happen

The outcome of that line exceeded my wildest expectations.... But not in a good way

Although, I think my mind is clearing up now... I think I know what's wrong.... Oh crap....

I've added an extra debug line which should give me some clarity on this matter, as this is rather fucking GGRRR!

Take XXIV

Added Trims, and hopefully that helps...

So that is indeed the case, eh?

Take XXIII

This line must confirm if that is true

If you ask me, the system is adding spaces.... again....

Take XXII

Quick swap-up

It sees the scenario tag for a file, in stead of the file.... That's not good, eh?

Take XXI

A few fixes in the BoxText linker

Take XX

Ah yeah, that last word "nil" bug, that I still can't get fixed....

Take XIX

needless comment

Take XVIII

LAURA JCR converted to BUBBLE JCR call

The news came so I had to break this off, but let's resume things now, shall we?

Take XVII

Some calls to harsh system routines that LAURA had, but NALA hasn't and which can only lead to very extremely terrible bugs, so I'm better of without them

Anyway, the main problem is fixed there

Still the computer thought it did.... I must find out why the computer says "out of memory" when the entire notion is out of the question!

That still can't cause an "out of memory" though

I did find a missspelled variable

Still no good....

Added tag MURPHY

And I was hoping to play some more Lands of Lore before the News would begin... Of course, coding NEVER allows such a thing to happen....

Take XVI

I think I found it.... NIL is not yet able to declare and assign a value unless it's constant... Why it came to out of memory in stead of throwing a PROPER error, that's beyond me, though....

Right, it's confirmed the substitutor code is to blame (yet it cannot cause this to happen, so I'm still in the dark here).

Take XV

Ah... This happens during the call to the New Game... Maybe that explains something... yet... this is very very odd

The menu starts, and suddenly I get the "not enough memory" notice.... NOTHING can cause that to happen....

Take XIV

I've no idea what I'm doing... Since the engine refuses to give CORRECT data, I'm completely in the dark here

Take XIII

?

Take XII

Does this do the trick?

Take XI

MOAR parse errors

Take X

Parse error

IX

Linked that to BoxText

New gamevar substitution routine (I forgot about that)

Take VIII

MySplit is not just Split

Take VII

Temporary dummied code I won't need for the time being

Added tag DUMMIED

Take VI

NIL syntax is a bit more restrictive than Lua when it comes to direct table definitions

Take V

I removed a line I though I'd need, but as things went, I realized this line was only faulty.... I only forgot to remove it, this the NIL parser threw an error

Take IV

FOUND IT!

III (although this can't change anything, but actually it can't crash on anything either, so what's happening here?)

For some odd reason a WHITELINE has an unknown identifier.... Odd....

Take II

A forgotten self

Take I

Now I need to put everything to the test, which can be hard as I cannot yet see the text being processed, so I must just guess stuff a little....

And set up a function which should show all this....

Box generation based on the space the text in it needs

I've written a generation script (or rather revived the one I used for TFTREVAMPED and adepted it to NIL, to take full advantage of what NIL can do) that will do the end generation. This is important, as the system cannot know how big the screen is beforehand, so I cannot adept the text to this in my own data files. This script will calculate it all out and make it fully suited with your monitor.
This is not yet fully done, as a few more things need to be done (as some LAURA references may still exist, and since LAURA is no longer being used....)

#21

It's a bit senseless having to re-invent the wheel all the time, so let's see how the TextBoxes are generated in The Fairy Tale REVAMPED!

All's well!

A few mistakes I made when linking this (I was too hasty).

I've now set up an auto-linking feature which allowed the BoxText to always perform the correct background rendering based on the current game situation.

All's well

A quick checkup to make sure everything's right

I've restored the original link to the opening SASKIA script so I can start the opening scenario... The menu screen is not yet relevant, that will come once I get into the actual field gameplay (and when that one comes I'll first get into the savegame routine anyway).

Up-to-date

Running

A bug shown by the screenshot... (the amber box next to the first box) has been fixed

Added tag SCREENSHOT

I REFUSE to call this a "fix"

Well, this is the ugly method, but at least it prevents cosmetic issues

Vertical alignment in text ignored?

Changed the vertical alignment of the points

It WAS the cause of all trouble???? WTF?

Forgotten "end" command... Such a thing should NEVER give an out of memory error under any circumstances... However this means a group is not properly ended... Is that the reason why???

I wonder....