I upgraded my system to the latest A38 version, from the old A34 i had for a long time. No problems, no troubles at all. All my scripts and customizations work flawlessly and i like the new changes in the Mystic Configuration. Also the MIS2 (which is now MIS), works fine for me.

The only odd thing i found so far, is that in the Message Text Editor when a word wraps to the next line, it goes wrong/garbled in some way. The last character goes one place back, it leaves a space and the character that was there appears last. :? Is this happening to others too?

So... a big Thank You and Bravo to G00r00 for all of his efforts his making
for Mystic. :)

.----- --- -- -
| Another Droid BBS
: Telnet : andr01d.zapto.org:9999 [UTC 11:00 - 20:00]
. Contact : xqtr.xqtr@gmail.com

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Another Droid BBS (21:1/111)

On 01/05/18, xqtr said the following...

I upgraded my system to the latest A38 version, from the old A34 i had
for a long time. No problems, no troubles at all. All my scripts and customizations work flawlessly and i like the new changes in the Mystic Configuration. Also the MIS2 (which is now MIS), works fine for me.

The only odd thing i found so far, is that in the Message Text Editor
when a word wraps to the next line, it goes wrong/garbled in some way.
The last character goes one place back, it leaves a space and the character that was there appears last. :? Is this happening to others
too?

Yes this was happening to mine as well, I think it was a change from 80 width to 79? Change the end of message bar to 79 and this should resolve itself. :)

Cheers!
Pequito

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

The only odd thing i found so far, is that in the Message Text Editor
when a word wraps to the next line, it goes wrong/garbled in some way.
The last character goes one place back, it leaves a space and the character that was there appears last. :? Is this happening to others
too?

I've not had any issues with the editor, but I've been on Windows mostly lately. I'll see if I notice anything the next time I'm in Linux. If its
easy to give me step by step instructions to be able to see the issue that would be helpful but hopefully I'll see it without needing to go that far.

Are you logging into your BBS locally or through a telnet client when you see this (or both?)

I did make some changes to the editor in the last alpha because some of the code between the ANSI editor and the message editor is shared.

--- Mystic BBS v1.12 A39 2018/01/05 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/05/18, g00r00 said the following...

I did make some changes to the editor in the last alpha because some of the code between the ANSI editor and the message editor is shared.

First. Ho-lee-fuq dude. I think the built in ANSI editor in the config is the best fuckin' thing since sliced bread!

For so long I've edited the shit in pablodraw on my Windows machine and used WinSCP to move it over to where it needs to be. WOW. ;)

That note, when you save an ansi and pick the default settings, it seems to save at the very last character on the last line at the moment. It should probably save to the end of that last line where there are characters present.

Just now I loaded up my menu header template, added something, and saved.
Then in the menu editor I display the file using DF in the header field, so that I can use Mystic's built in columns for spacing as well as easier
editing (adding/removing) of menu options later (never have to edit the ansi again, etc).

When I saved it, I went to said menu and it displayed the ansi great, but the first "column" of the first menu option ended up starting in the middle of the screen, since the very bottom of the ansi header there is one ansi character there. The menu selections started right after that character, rather than beginning on the next line.

While I know that you can easily add a CR after displaying the ansi, saving should probably save to the end of the line of said ansi (like all other ansi editors), rather than the last actual character (this I believe has only ever happened with animation mode in TheDraw).

Otherwise, I'm totally diggin' this thing, and it's going to make my time modding Mystic MUCH easier. ;)

Regards,
Nick

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 01/05/18, g00r00 said the following...

I've not had any issues with the editor, but I've been on Windows mostly lately. I'll see if I notice anything the next time I'm in Linux. If

i am getting this too.

Are you logging into your BBS locally or through a telnet client when
you see this (or both?)

i only call via netrunner so it looks pretty ;)

i type a word it looks like this

"hell how are youo" the letter jumps to the end.

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

First. Ho-lee-fuq dude. I think the built in ANSI editor in the config
is the best fuckin' thing since sliced bread!

Yeah tell me about it!

Ever since around 1.11 when I added in "draw mode" to the FS editor I've had it close to being ready to go. But for some reason I just sat on it for a
couple of years until this xmas vacation.

Now that I have the basic version working and I am using it, I am annoyed at myself for now doing this earlier.

I still need to add some block functions in there and a help file but so far it has worked well for me. One thing I love is that you can set those parameters like abort on/off, display speed, etc, and it will generate the MCI codes for it. But when you reload that same ANSI it will also parse out all of those values so you retain the options between edits.

This is a really nice to have compared to other ANSI editors where the MCI code leaks through and you have to manually edit the damn ANSI anyway after you save it.

I was going to do the same thing for those old "Screen Info" codes but I keep going back and forth on whether or not I should make the effort.

That note, when you save an ansi and pick the default settings, it seems to save at the very last character on the last line at the moment. It should probably save to the end of that last line where there are characters present.

Good find. I'll work on getting this fixed up ASAP.

Otherwise, I'm totally diggin' this thing, and it's going to make my time modding Mystic MUCH easier. ;)

There are so many more things we can do with it too now that is in. Like you mention editing your menu header that you replaced with a file. We can do things like a CTRL+E option that will open up the ANSI file to edit right from header field in the menu editor.

I need to compile a list of ideas like this so I can work on getting them implemented, so if you happen to think of any as you're modding through let me know...

I plan to remod S7 on Linux from the ground up using nothing but Mystic to inspire ideas, but since you're already in the middle of that... ;)

--- Mystic BBS v1.12 A39 2018/01/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I've not had any issues with the editor, but I've been on Windows mos lately. I'll see if I notice anything the next time I'm in Linux. I

i am getting this too.

This seems to be an issue with those who changed their FS editor to 80
columns from the 79 default. This is why I didn't catch it :(

I have it fixed up now for A39 pre-alpha

--- Mystic BBS v1.12 A39 2018/01/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Yeah tell me about it!

One suggestion: if it can be done which maybe not. It is awesome.

Is there anyway you can have it move text around instead of re-typing?
I know thats asking a lot, but hey never hurts to ask.



-Nugax

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

On 01/06/18, g00r00 said the following...

Now that I have the basic version working and I am using it, I am
annoyed at myself for now doing this earlier.

I mean, I've only used it once so far, and it seriously cut my time in half
on one simple addition to the BBS. After my son's wrestling meet tomorrow,
I'll probably jump back in for a bit.

I still need to add some block functions in there and a help file but so far it has worked well for me. One thing I love is that you can set
those parameters like abort on/off, display speed, etc, and it will generate the MCI codes for it. But when you reload that same ANSI it
will also parse out all of those values so you retain the options
between edits.

Awesome. I still have to dive into it more, but just the simple 24 liner edit
I did worked pretty damn good, except the little quirk I ran into.. but
that'll be a thing of a past real soon, I'm sure.

This is a really nice to have compared to other ANSI editors where the
MCI code leaks through and you have to manually edit the damn ANSI
anyway after you save it.

True.

I was going to do the same thing for those old "Screen Info" codes but I keep going back and forth on whether or not I should make the effort.

Not exactly sure what you're referring to here. Do you mean like !1 and such?

Good find. I'll work on getting this fixed up ASAP.

Thank you, good sir!

There are so many more things we can do with it too now that is in.
Like you mention editing your menu header that you replaced with a file. We can do things like a CTRL+E option that will open up the ANSI file to edit right from header field in the menu editor.

I need to compile a list of ideas like this so I can work on getting them implemented, so if you happen to think of any as you're modding through let me know...

This reminds me.

Was it meant to be that making the "Display File" field your ansi, was for one who is adding the commands that are displayed to the actual ansi (as in creating the ansi with the actual menu commands as part of it)? And then when using DF<ansi> in the "Header" field you can utilize the commands displayed from the menu editor itself?

I noticed when putting "mainhdr" in the 'Display File' field, it won't
display the commands listed in the menu editor. But leaving that field blank, and adding "(pipe)DFmainhdr" to the "Header" field, it will.

I prefer the latter, because then I won't have to edit the actual ansi. I can then add or remove commands from the menu editor (main) as I please, and they'll continue to display with the proper column settings set for the menu, etc. Just wanted to make sure this was your original intent.

I plan to remod S7 on Linux from the ground up using nothing but Mystic
to inspire ideas, but since you're already in the middle of that... ;)

So far it's going good. I was able to come up with something for that door
menu mod I mentioned to you awhile back. The main/message section is just
about finished as well as the application and login stuff. I'm adding a
couple new menus and will need to start on the file section soon.

If you change directory structures or anything crazy like that.. are you going to include another "upgrade" executable that does it for you? Or will there
be detailed instruction on how to install from scratch and copy over your
stuff from your current system so as to not break anything?

Regards,
Nick

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Yeah tell me about it!

One suggestion: if it can be done which maybe not. It is awesome.

Is there anyway you can have it move text around instead of re-typing?
I know thats asking a lot, but hey never hurts to ask.

The very message you quoted mentioned I was working on block functions. :) What the block functions will do is allow you to select blocks and move, copy, stamp, etc.

You can already cut and paste lines in the same way that you can in the message editor, text editor, Nano, etc using CTRL+K and U

--- Mystic BBS v1.12 A39 2018/01/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Now that I have the basic version working and I am using it, I am annoyed at myself for now doing this earlier.

I mean, I've only used it once so far, and it seriously cut my time in half on one simple addition to the BBS. After my son's wrestling meet tomorrow, I'll probably jump back in for a bit.

It has some issues still, and some missing features. I've added in some of the block functions though, and besides the bugs I'm still working through, it has made it SOOOOO much more useful.

As of now I have the block selection, fill by attribute, character, both, or new attribute, and block-based centering. I need to add in copy/move/stamp and I think the block functions will be a great start.

For me, fill and center are what I end up using the most but occasionally a copy/stamp too.

Awesome. I still have to dive into it more, but just the simple 24 liner edit I did worked pretty damn good, except the little quirk I ran into.. but that'll be a thing of a past real soon, I'm sure.

Yep that has been "fixed". There is a "CRLF at EOF" option now in the Save file dialog so you can set if you want it there or not, but it will always default to "Yes".

I was going to do the same thing for those old "Screen Info" codes bu keep going back and forth on whether or not I should make the effort.

Not exactly sure what you're referring to here. Do you mean like !1 and such?

Yes. Like you might press "CTRL+S" and it'll open up a dialog where you can configure those values. When you save it, it'll automatically populate the ! codes. When you load it, it will parse those ! codes and populate the CTRL+S dialog.

Was it meant to be that making the "Display File" field your ansi, was
for one who is adding the commands that are displayed to the actual ansi (as in creating the ansi with the actual menu commands as part of it)?
And then when using DF<ansi> in the "Header" field you can utilize the commands displayed from the menu editor itself?

Yes. I think if you note the description it says something like "replaces the internally generated menu" and it literally means that it does. So yeah its intended not display commands. If you want the commands then you just add a header/foot ANSI to wrap around the commands.

--- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/08/18, g00r00 said the following...

Yep that has been "fixed". There is a "CRLF at EOF" option now in the Save file dialog so you can set if you want it there or not, but it will always default to "Yes".

Sounds like a plan.

Yes. Like you might press "CTRL+S" and it'll open up a dialog where you can configure those values. When you save it, it'll automatically populate the ! codes. When you load it, it will parse those ! codes and populate the CTRL+S dialog.

Jeez man. Beginning to make things so easy grandma can do it! ;)

Yes. I think if you note the description it says something like
"replaces the internally generated menu" and it literally means that it does. So yeah its intended not display commands. If you want the commands then you just add a header/foot ANSI to wrap around the
commands.

Perfect. That's what I've been doing, but figured I'd ask.

Regards,
Nick

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Good afternoon

I am having a big problem with mutil

I can send messages but can not toss them into the bbs (mystic)

can you please contact me via email @ Richard@cmrk.net

I will not be able to see any answer to this message right now untill I can toss messages into the bbs

Thank you very much

Richard Szajkowski AKA The Wizzard

U.S.S. Alliance BBS (Brampton) (Born 1984 Reborn 2017)

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: U.S.S. Alliance (BBS Brampton) (21:4/111)