Subj : Re: Mystic MPL Question
To   : Black Panther
From : g00r00
Date : Tue Oct 20 2020 04:23 am

 BP>  g0> they will hard code "c:\mystic\temp%3" to construct the node director
 BP> 
 BP> I'm guilty of doing this as well... :) But, I'm in the process of
 BP> changing all of my doors to be run via a bash script. Mystic will just

Yeah its not anyone's fault for using it.  Its the old way things worked for 
many years. A lot of information out there is outdated and tells people to do 
it, and then those people spread this bad habit while helping others because 
thats how they learned.

I should have pushed to get the right information out there more, and updated 
documents to say not to do this.

 BP> it runs the doors. Trying to get dosemu to play nice has been a bit of a
 BP> challenge though.

I've heard from Ryan that DOSEMU2 is the way to go these days, although I have 
not tried it.

 BP>  g0> To counter this issue, I was thinking about making "door profiles" to
 BP>  g0> help them rebuild everything easier.
 BP> 
 BP> How would that work?

The Mystic 2 demo from 2001 had door profiles so it work like that, if you ever 
saw it (probably not many saw that version these days).

You'd basically have a "Execute Door Profile" menu command and pass it the ID 
of the door you want to run.  There would be a door configuration just like a 
message/file area with an "Active" setting and a ton of default doors already 
set up.  For most popular doors you'd just be able to install the door to the 
proper directory and set the door to Active. 
 BP> WOW! And I thought I might have been pushing the limits. :) I guess my
 BP> total of 125,000+ files isn't too bad then...

I think in real world terms you are pushing limits I guess that not a lot of 
people collect that many files!  But in terms of what the software is supposed 
to be capable of you're not even close to limits. :)

 BP> I didn't think you'd have it done that quick! That sounds great! When is
 BP> the next pre-alpha coming out? ;)

Its out now go get it!

It took maybe 4-6 hours to get it into place since I had the idea mostly 
working already outside of Mystic 1.  I got really sucked into it this evening 
and got it all done in one sitting!

 BP>  g0> SetMarquee('This is my marquee', X, Y)
 BP>  g0> 
 BP>  g0> Ch := MarqueeInput;  // This will scroll the marque while waiting for
 BP>  g0> key and resume the next time you call MarqueeInput
 BP> 
 BP> Ohhhhh, I'm already thinking of ways I could use that. :)

Yeah it'd be pretty cool, easy to use thing.  It'll just be a drop in 
replacement for "ReadKey"

--- Mystic BBS v1.12 A47 2020/10/20 (Windows/64)
 * Origin: Sector 7 | Mystic WHQ (77:1/138)

.