Now this implies the MousePointer is still NIL.... How odd?

Another force test

Step II, make sure the drawing routine is actually called!

At least I made sure the show mouse feature was actually called at all!

Let's force some results!

And it remains a mystery

And try it all again!

Let's build again!

Parse error

I hope

Which is also the reason I created NIL, but this glue-script was in pure Lua... Bad idea so it seems

Ah... I see the bug

Oh wait, I looked at the wrong spot

The log appears not very supportive

And let's see

rebuild

Added another debug line to the BUBBLE glue script

Time to find out why!

Added tag INVESTIGATION

It doesn't show, though

Gotta test if it works now

Put mouse pointer in menu

API glue script parse error

Rebuilt

I've altered the internal script to make the mouse pointer more part of the system... (This was actually to keep my general code cleaner, and future games also profit here, so actually win-win).

For that I used my good old DPaint in DOS.... I still love that applications...

Added tag DOS

Designed a mouse pointer (the original game didn't have it as it used the system's own mouse pointer, but for this remake that was not a good idea since XNA turns it off automatically, not to mention that an own mouse pointer makes the game more "out of the system"

And to make them clickable with the mouse

The next step will be to make the menu items actuall work

That looks cool and a lot more clear now

Not placed at right instances.

Wrong rectangle style

Horrible

Never forget "self", Jeroen. I know an enhancement here is in order, but as we don't have that yet, don't forget that!

The Graphic effect could cause some confusion though, so I made sure that's been taken care of with a nice rectangle

No more questions no more questions, what works that works

And suddenly without any vital changes or possible explanations why, the bugged code (that was never bugged) works the way it should (which is only natural since it was never bugged in the first place).

Although I guess some unsafed stuff made it through so let's do that again!

I've added a little synchronizer so I can more easily debug NALA itself

But the window should be bigger, though

I've now configured NALA NOT to work full screen in debug builds of the engine

I think I need to risk ANOTHER total hangup to find out

let's see... :-/

Now that made matters even worse somehow... Why?

Of course and extra test to make sure...

Well, that has been fixed

I am an idiot, hahahahahahahaha!

But the main issue is still not fixed and I need to sort that one out!

And I fixed the bug that called the code that could make the system crash in the first place

At least I rid my system of total hangups

Added tag CHECKED

I was looking in the wrong project.... mesa dumass!

Because

Added tag SOLVED

And now I wonder how my last code could disappear into nothingness

rebuild

I decided that now I was at it to enhance my Blue Screen Of Death a little bit... cosmetically ;)

Added tag ENHANCEMENT

At least that it does, and the error itself now also appears, which is good!

Let's hope this try {} catch will rule this out from happening again!

Okay, whatever caused this, the error coming from it was so great it hung my entire system (thanks to the debugging algorithms Visual Studio uses... figures), but at least I could get another step closer to finding the cause of all evil

This created a complete error though, and I wonder what the hell went wrong there...

I've tried to set up a keyboard feature to browse through the pages

BETTER!

y margin fine tuning

Added tag COSMETIC

GRRR!

Siiiigh

Another deprecrated .NEW instruction

(Please note, I mean my own Blue Screen of Death, and not Windows' Blue Screen of Death. I can use the term, since it's unofficial, and mine doesn't mimick Microsoft's).

But there's always room for another BSOD

Which should now be fixed

ALthough in stead I get a blue screen of death

The menu items had to appear

Okay, I've generated the license blocks... happy now?

But first I wanna eat!
I'm hungry!

Next stop will be to put in the actual menu items

I REFUSE to call this a fix, but at last the issue has become invisible now

Let's put this line in then... :-/

The MidScreen feature appears to keep bugging up

And try the game then

And re-run the build script

Let's add this line to NALA

Ah, maybe this shines a proper light on stuff....

Hmmm, almost looks good enough to me, but why the lower resolution?

Let's test this

recompiled

NALA configured to go full screen all the way now!

Stuff works now

It did require NALA to be recompiled, though....

ret-conflict?

Blitz Font added

A quick library written that can do some neat stuff to BubbleID data

I must not forget to change this in the TeddyBear editor and most notably the Kthura editor as well.

Added tag REMINDER

I think I fixed that.... (At last)

No effect

Well searching the internet did find me an article which may shine a light on this situation... I hope it is, but that has to be tested first...

Added tag RESEARCH

Now Microsoft's exposed as the ultimate ALPHA idiot! In stead of the fading effect the logo is supposed to have, the alpha is only taken to 50% in all pixels where transparency was needed at all, giving an extremely ugly effect.... DANG!

And then I gotta test this again.... (sheesh!)

And then back to my other powershell tab to rebuild the game itself

So I go back to powershell to refire my NALA build script

Fixed that stupid action of mine.... (Geez)

I AM A STUPID COW!

Let's try that again!

Done

Well that's easy to fix

forgot to rebuild NALA

Blue screen, eh?

Don't forget to save before calling the builder, dumbo!

Like I said, the original background cannot be resused due to it being bound to a certain screensize, and the new game using a variable screensize (which is a pity, as the original picture was beautiful)

Menu background

Odd... The system *is* set to perform alpha blending.... Are Microsoft programs really THIS rotten on this department?

Not to mention that I'll need some ALPHABLENDING

I've put the logo on the Main menu screen.... Some fine tuning may be required though

Adapted an internal NIL script (Graphics.nil) due to the new class 'new' handling

The numbers on my screen confirm the fix

Since everything was messed up, I've reset the auto-iconer, however I've changed the numbers to make Aziëlla appear first (as she was the only one of the playable characters who didn't yet show up) and after that everything will recycle from a clean go.... (Hopefully)

Okay, that's fixed then.... Yes, mesa cow!

That was because I messed everything up... Yeah, I'm just an idiot....

Nope, as the wrong picture shows.... Back to the drawing board then....

Does it work now?

As you can see, the auto-icon which had to display Merya is broken....

Geany Syntax Highlighting

Added tag UPDATED

Updated to the new situation

I've come up with a solution for the .NEW() issue that came up causing a conflict with delegates

Brute force class destruction (to prevent conflicts later)

Fixed the short term issues....

FUCK! That was pretty stupid.... I need to rethink a few things here.... And that may put the deprecation of .NEW() on hold.... But what happened makes perfect sense now, though.... :(

Let's see what we get now.... :(

Fixed it!

Ah, so that's is.... :(

And what kind of madness came up now???

A bit more info from NIL why it thinks what it thinks...

Misformed error

I wonder what is happening here... :-/

WHAT THE....

Case error

Identifier conflict

I need to check if this all works, though

I've added a "secret" debug code that will take me into the debug console, however, this key combination will ONLY work in the development version!!!

Only NALA benefits now for me, but it takes only a recompile of the MonoGame engine to make MonoGame benefit here too, which is only one command from PowerShell for me. :)

I've been messing around in Bubble to make it easier to detect if keys are held or not

As a matter of fact .NEW has been deprecated now

Nil has been advanced making use use of that annoying .NEW() method no longer needed.

Added "DEVELOPMENT" tag to the definitions file

Will always run in full screen.... For these kinds of games... The better option....

I'm getting really tired now, so I'm gonna call it a day... Despite the cockroaches I had to squash, I did make some progress.... There are still a lot of things to do... Both on the engine as on game preps, before we can really get onto the road, but the moment I'll post the guy with the gun as the start signal may come soon now....

I still need to find out why removed files are not removed from the list, but that's not a direct concern for Dyrt

Is running

I see that I forgot to add the script I use to compile NALA and add it to the bubble builder.... Well, I've taken care of that!

Added tag POWERSHELL

I've already aliased "Wouldn't it be" by Matt McFarland to be the music playing during the fights against the Order of Onyx... Just like in the original game.

Undummied link to get the flow running

Added tag DONE

Project file updated

Logo will be the same, and has been imported

Added tag ART

Pushed stuff

I refuse to call this a fix, but I cheated a way to get issues with loading music "fixed"

Added tag CHEAT

Temp dummies

Anyway I fixed that!

Because I gave the wrong parapemter to the debugger, but the code in general was unbugged

Added tag STUPIDITY

And now to figure out why the caption contains a function pointer in stead of a strng

Rebuilt and repacked

Well At least that issue is out of the way....

Right, the cause of the error has been found... TQMG tries to pick into null for a JCR6 file... Question is now, how could that be null (as the scripts are read)

Let's see what happens next

Extra data error catcher

I've build in extra capturing of the font loader... It does confirm an error takes place while the font is loading... Now to figure out why that happens.

Why was my devlog tool suddenly down?

no music heard, but that's a later concern... I need tofind out why loading the font doesn't work

Invalid NIL declaration

Moar errors in stack

Error in stack library

link error in music sub

That's indeed the source of all evil....

It appears that loading the font is where it goes wrong

At least it's now confirmed the translation process appears to go well

each error in NIL iteslf

Bugs in debug features are even worse than the bugs you place them in for

A parse error that came up when putting in #say

I've placed a #say at the top of the init.nil script to make at least sure we got the tag where I can test it in code that works!

I've also set Bubble to link the log to this directive

I've added a #say directive in NIL, and hopefully it can shine more light on stuff

More investigation is in order!

And kaboom.... Starting this will crash everything

Let's recover to chain to and see what the logs will show me

Loader appears to work now.... Strangely enough

I'll remove all "delegate" keywords, and try again... That keyword is still a bit bugged within NIL and with var variables we can also do this

Right! Then stuff DOES suddenly appear to be working..... No ignored CSays() and all the data appears to be fitting.... This should imply something goes horribly wrong in loading the main menu

Let's see what happens if I dummy the flow loaders and chainers

What is happening here cannot be possible, and why? Because if it were possible, the commands that work should have been ignored as well, so this entire fuckshit simply doesn't make sense

In the INIT routine the CSay calls are ignored (for no reason), yet the call to the Main Menu script works, compilation errors are even thrown, but the code is after that stage ignored....

NEITHER is the message that music is available, to make things even more odd!