Custom-building your own SSCI

[troflip]

Idea for easy add: ability to vertically flip views.

[Kawa]

Easy perhaps, but still ASM. Tch, we'll see.

[MusicallyInspired]

Easy perhaps, but still ASM. Tch, we'll see.

It's "tsk" not "tch", you barbarian you.

[Kawa]

So with a little help from IDA and a few liters of diet coke, I found out that startasm.s was being assembled wrong. This broke restore/restart, which works by longjmp, and saving if it were to fail. And woah boy how it broke.

Turns out that MASM was generating extra code around the setjmp and longjmp procedures, because they have parameters. The originally released code did not specify any, but MASM wouldn't take it because the proto definitions did have parameters. To quote the MASM 6.11 manual:

When you use the PROC directive with its extended syntax and argument list, the assembler automatically generates the prologue and epilogue code in your procedure.

If a procedure does not have any parameters or local variables, the prologue and epilogue code that sets up and restores a stack pointer is omitted, unless FORCEFRAME is included in the prologuearg list.

We want to do the opposite here, though...

If you want to revert to the standard prologue or epilogue code, use PROLOGUEDEF or EPILOGUEDEF as the macroname in the OPTION statement.

Code: [Select]

OPTION EPILOGUE:EPILOGUEDEFYou can completely suppress prologue or epilogue generation with

Code: [Select]

OPTION PROLOGUE:None
OPTION EPILOGUE:None

This has of course been tested and confirmed. The scibuild.zip file in my stash has been updated accordingly.

[troflip]

If you're still working on this, other than the x/y axis flipping (which is useful for having mirror or floor reflections), you can:

- have a flag that says ignore the priority comparison when drawing a view (so it always draws)
- have a flag that tells a view not to write to the visual screen (combined with the above, useful for cutting out holes of lower priority in a scene... like for a window)
- have a flag that tells a view not to write to the priority screen (lets you apply a "decal" onto a surface of varying priority)
- have a flag that inverts the priority compare (why would you do this? I have a crazy reason to do this)

[Kawa]

I'm gonna need another field for those flags.

[troflip]

Yes, you will.

[Kawa]

Y'know, I haven't done anything with this for a bit now, but the fact you can build versions that have menu bar support like the terp that came with LSL6 did remind me of something. I did mention menu bars on page one about (Kawa 3).

SIERRA.EXE has no debugger and no menu bar, basically the one intended for public use. SIERRAM.EXE adds SCI0-style menu bar support to that, and is basically what LSL6 came with. SCI.EXE includes the debugger, and SCITESTR.EXE has both.

Given a SIERRAM terp (custom built or LSL6's), what's stopping you from being cheeky and removing the icon bar?

Edit: and yes, I did add that "& 2 to check if menus are available" thing:

Code: [Select]

case 3: //KAWA_ISDEBUG
  //(Kawa 3) ;Returns 1 if debug version, 2 if menu bars are enabled, 3 if both.
  acc = isDebugVersion;
#if TESTER
  acc |= 2;
#endif
  break;

[Kawa]

Given no resource.cfg, the original interpreter will say it can't find the configuration file and to run the install program.
Given a config file with a missing video driver -- literally no videoDrv = ____ line at all -- it'll say it couldn't install the video driver but not how to fix it.

So I edited mine to detect the fact that there's no driver specified and simply say, "please run the install program." No script #, no IP #, just a simple request so next time you run it there will be a video driver to try and load.

Now I should update my install program to secretly reset to defaults if these things are missing too cos I just loaded a no-driver config and it was full of blanks (update: done and uploaded.)

[Kawa]

Oh, and another thing that I did. Ending text screens. B800 screens, ENDOOM screens, whatever you wanna call 'em. If the data's not there, it reverts to the regular quit message.

[MusicallyInspired]

ASCII ending screens are the best.

[Kawa]

It's about time I added a new feature.



(Display {This text is outlined automagically!} dsCOORD 8 8 dsALIGN 2 dsCOLOR 31)

Alignment can be 0 for left, 1 for center, or -1 for right. Seems a waste of a whole 16-bit word, why not make 2 left-outlined and 3 center-outlined?

In any case I can now draw outlined text in any font I damn well want.




In KERNEL.C:

Code: [Select]

RGrafPort savePort;
RPoint newPenLoc;
word penColor = 0, outline = 0; //add these two
width = colorIt = -1;
mode = TEJUSTLEFT;


Code: [Select]

case p_color:
penColor = *args++; //instead of calling PenColor directly
break;

Code: [Select]

//get size of text rectangle
RTextSize(&r, text, -1, width);

if (mode & 2) RInsetRect(&r, -1, -1); //not sure if needed but eeeeeh

//move the rectangle to current pen position
MoveRect(&r, rThePort->pnLoc.h, rThePort->pnLoc.v);

Code: [Select]

//opaque background
if (colorIt != -1) RFillRect(&r, VMAP, colorIt);

//add this whole thing.
if (mode & 2) {
mode &= ~2;
ROffsetRect(&r, 1, 0); RTextBox(text, FALSE, &r, mode, -1); //right...
ROffsetRect(&r, 0, 1); RTextBox(text, FALSE, &r, mode, -1); //bottom right...
ROffsetRect(&r,-1, 0); RTextBox(text, FALSE, &r, mode, -1); //bottom...
ROffsetRect(&r,-1, 0); RTextBox(text, FALSE, &r, mode, -1); //bottom left...
ROffsetRect(&r, 0,-1); RTextBox(text, FALSE, &r, mode, -1); //left...
ROffsetRect(&r, 0,-1); RTextBox(text, FALSE, &r, mode, -1); //top left...
ROffsetRect(&r, 1, 0); RTextBox(text, FALSE, &r, mode, -1); //top...
ROffsetRect(&r, 1, 0); RTextBox(text, FALSE, &r, mode, -1); //top right...
ROffsetRect(&r,-1, 1); //and back to the center.
}
PenColor(penColor); //NOW we set our pen color!

//now draw the text and show the rectangle it is in
RTextBox(text, FALSE, &r, mode, -1);Outlines are always in black because it calls PenColor(0) before parsing the arguments.

[troflip]

Add another bitmask/flag for controlling which of the 8 "outline texts" are drawn. Then you can do things like dropshadows, or fake a blur on the text if the outline color is partway between your text color and your screen (this is how I do the hover effect on the verbs in Snowspirit).

[Kawa]

I was thinking of having the 4 bit do dropshadows... by the way, I mentioned this on Twitter but there's an extra value in Display that's not in your header file, 121 "noshow".

[Kawa]

Okay, I moved the thing into its own pseud, dsSTROKE 122, and made it a bitfield. You'll notice there was an unused outline variable in that code I posted...

Code: [Select]

case p_noshow:
showIt = 0;
break;
case p_stroke:
stroke = *args++; //this was that variable.
break;


Code: [Select]

if (stroke)
{
ROffsetRect(&r, 1, 0); if (stroke &   1) RTextBox(text, FALSE, &r, mode, -1); //right...
ROffsetRect(&r, 0, 1); if (stroke &   2) RTextBox(text, FALSE, &r, mode, -1); //bottom right...
ROffsetRect(&r,-1, 0); if (stroke &   4) RTextBox(text, FALSE, &r, mode, -1); //bottom...
ROffsetRect(&r,-1, 0); if (stroke &   8) RTextBox(text, FALSE, &r, mode, -1); //bottom left...
ROffsetRect(&r, 0,-1); if (stroke &  16) RTextBox(text, FALSE, &r, mode, -1); //left...
ROffsetRect(&r, 0,-1); if (stroke &  32) RTextBox(text, FALSE, &r, mode, -1); //top left...
ROffsetRect(&r, 1, 0); if (stroke &  64) RTextBox(text, FALSE, &r, mode, -1); //top...
ROffsetRect(&r, 1, 0); if (stroke & 128) RTextBox(text, FALSE, &r, mode, -1); //top right...
ROffsetRect(&r,-1, 1); //and center.
}Useless offset calls, but this does ensure you end up in the right spot.