Messages

16

The Games and other Sierra Adventure stuff / Re: MTBLAST.DRV and SQ3 volume control

« on: February 27, 2022, 01:20:40 PM »

1. Have you tried with ScummVM?

That'd be cheating.

17

SCI Syntax Help / Re: SCI0 - Globalizing my local death sheet Script

« on: February 21, 2022, 09:00:23 AM »

If I had competence, it would've worked 😺

18

SCI Syntax Help / Re: SCI0 - Globalizing my local death sheet Script

« on: February 21, 2022, 08:18:32 AM »

I did write that off the top of my head without testing. Try doit: 0?

19

SCI Syntax Help / Re: SCI0 - Globalizing my local death sheet Script

« on: February 20, 2022, 04:52:30 PM »

Just pick a number that isn't taken by a script yet, I guess? As for how to do a custom Dialog, I'd say study the Print function.



The Print function uses temporary variables to hold a Dialog instance, one DText, one icon, one DEdit, and up to six DButtons, plus a bunch of things to track all that. It first instantiates a new Dialog ((= hDialog (Dialog new:))) and DText, then figures out what text to put in there (is it a Text tuple or a script pointer?), and finally adds the DText to the Dialog ((hDialog add: hDText)). It then goes through all the other arguments, if any, adding icons, setting titles, adding and tracking buttons, and moving things around. Finally, it opens the Dialog, calls Dialog::doit to get the user's response, and disposes it again ((hDialog open: nwNORMAL -1 doit: dispose:), to simplify).

Therefore, here's what I'd do, off the top of my head:

Code: [Select]

(procedure (DeathReport &tmp hDialog hText [str 512] theY)
(= hDialog (Dialog new:))

(Format @str {You have died %u times:} [gDeaths 0])
(= hText (DText new:))
(hText
text: @str
moveTo: 4 4
font: 0
setSize:
)
(hDialog add: hText)
(= theY (+ 4 (hText nsBottom?)))

;;; The iteration starts here
; Put something new in str
(= hText (DText new:))
(hText
text: @str
moveTo: 4 theY
font: 4
setSize:
)
(hDialog add: hText)
(= theY (+ 4 (hText nsBottom?)))
;;; Repeat that part until you're done.

(hDialog
text: {Death Count}
setSize:
center:
open: nwTITLE -1
doit: ; This should block until you click the dialog. Or a button, which we didn't add.
dispose:
)
)
You might wonder if it's safe to reuse hText like that. Well, SCI10's PrintD does it, and that does in fact allow more arbitrary layouts than SCI0's Print.

20

SCI Syntax Help / Re: SCI0 - Globalizing my local death sheet Script

« on: February 20, 2022, 02:59:18 PM »

1. Something like a death screen doesn't need to be a Room per se, but you certainly don't want it as part of Main — there's no reason to keep a large script that may not be needed for a long time in memory.

2. Display or Print... why not a third option? Print is just a convenience function that populates a Dialog, after all, so why not use a Dialog but not Print? That'll take care of both dismissing the window and having a complicated layout inside of it.

21

SCI Development Tools / Re: SCI Companion V3 - alpha build notes/bugs/feature requests

« on: February 12, 2022, 08:53:31 PM »

It does not.

22

SCI Syntax Help / Re: SCI 1.1 - Game class, newRoom method

« on: February 12, 2022, 09:18:14 AM »

I *am* orchestrating room changes via mouse clicks, so this does make some sense that I've got a rogue mouse click that is giving me trouble.

Well ain't that interesting, hmm? What if you commented out the mice-eating?

23

SCI Syntax Help / Re: SCI 1.1 - Game class, newRoom method

« on: February 12, 2022, 07:09:50 AM »

What this does is eat any pending mouse clicks so you can't "buffer" any actions before the new room appears. Here's what it looks like in the original Larry 5 code:

Code: [Select]

;Eat all mice downs and mice up.
(while ((= evt (Event new: (| mouseDown mouseUp))) type?)
(evt dispose:)
)
(evt dispose:)
Input events are produced by the engine and queued up. The Event::new method calls the GetEvent kernel to fetch the next event from that queue, of the given type if specified. So "eating the mice" just repeatedly fetches a mouse click event from the queue, leaving the keyboard stuff, and tosses them out, until there are no more mouse clicks left.

24

SCI Development Tools / Re: QFG1VGA - picture format problem?

« on: February 12, 2022, 06:57:41 AM »

Tested it myself and found it working. Thanks, your changes are on the git repo now.

25

SCI Development Tools / Re: SCI Companion V3 - alpha build notes/bugs/feature requests

« on: February 11, 2022, 02:08:13 PM »

Interesting. Good thing it has quick fix though, but too bad it requires no other changes or you lose stuff.

By the way, 3.2.4 has been out for a few months now. Who knows?

26

Forum Support and Suggestions / Re: HTTPS/TLS

« on: February 11, 2022, 02:00:54 PM »

All this talk about SMF updates and how much XenForo and its add-ons cost, and I'm just sitting here with my own board software that I made...

27

Forum Support and Suggestions / Re: HTTPS/TLS

« on: February 08, 2022, 08:31:47 PM »

Having access to the SMF theme files, I noticed an oddity in the function that writes the navigation bar. $siteUrl is hoisted in via global but it turned out to be blank/unset, so everywhere it said <a href="'.$siteUrl.'/something"> it'd end up with a link to only /something. Relative, not absolute.

As a bit of a hack to make sure that no matter how you got to the board (HTTP or HTTPS) you will go to the unsafe-but-functional main pages, I hardcoded things in the template to have $siteUrl be http:​//sciprogramming​.com and new variable $commUrl be https​://sciprogramming​.com/community, then used the latter for all the links leading to things on the board, with regards to the top of the page.

28

Forum Support and Suggestions / Re: HTTPS/TLS

« on: February 05, 2022, 10:38:53 AM »

I can tell you right now that the cause of the lack of style is that the main site uses an "http://" URL for the stylesheet, and the browser doesn't let you mix security levels like that. What you want to do instead is link to "//sciprogramming.com/community/Themes/MTBlue/css/index.css?fin20", or preferably just "community/Themes/MTBlue/css/index.css?fin20".

29

The Games and other Sierra Adventure stuff / Re: Betrayed Alliance 2 Development Journal

« on: January 29, 2022, 10:03:09 PM »

Well, that's awfully nice of Karl and I wish you both good luck.

30

The Games and other Sierra Adventure stuff / Re: Betrayed Alliance 2 Development Journal

« on: January 29, 2022, 10:26:46 AM »

But are they vectors? :3