Hello Paulie420,
Pretty dumb for a wise guy ;) - its way more simple:
1. create a dir in the themes dir
2. create the subdirs and copy the files you need/want from the existing theme 3. edit the theme.ini and change the theme name
4. start mystic config and it detects the new theme now
5. start editing
I noticed in the config that you also need to change the appearance
order.
using data from an older text theme - but... getting it ironed out. Now
I just have to figure out how to change to a new theme, and how I'll handle that with my setup.
using data from an older text theme - but... getting it ironed out. N I just have to figure out how to change to a new theme, and how I'll handle that with my setup.
You probably want to set your custom theme as the default theme for new users (Configuration --> General Settings --> Default Theme).
And perhaps stop Mystic from asking new users what theme they'd like (Configuration --> New User Settings 2 --> Ask Theme: No).
Users will still be able to select a theme of choice from the Account Settings menu unless you restrict usage for the theme you don't want
them to use.
For instance, if you don't want anyone to use the stock
theme (the one in the "themes/default" directory), you can do so with
default (or the theme(s) you want to disallow) --> List ACS: %Editors --> Theme/Prompt Editor The % ACS will disallow everyone (including the SysOp).
Also note that you will have to change the selected theme for each and every existing user manually; Editor --> User Editor --> <username> -->
1 (Settings 1) --> Theme --> enter the theme directory name of your
custom theme. If a user has a theme selected (e.g. the stock "default" one) to which he/she doesn't have access (as per the List ACS of the theme), Mystic will complain and disconnect the user on login, if I
recall correctly.
Hope this helps! :)
Best regards
Zip
I don't wanna change anything, just ALLOW a couple users to SELECT the ascii as a theme option. I'll prolly just do this in the User Account menu, and again - I don't want the to REALLY be an option - just there
for those who NEED it.
Sounds great!
Actually the ability to support ASCII is one of the things I like with Mystic.
Actually the ability to support ASCII is one of the things I like with Mystic.
And being able to use pipe (MCI) codes in .ASC files and having Mystic translate it to ANSI or ASCII as needed, on-the-fly, is a very nice feature!
my themes when I ran a (GI)14, but you just gave me a thought and... I have ascii set to NOT allow ANSI; I bet that means that it won't display it to ANSI users, hence.... ..... :P I bet when I set that to true it
I think I just ironed out my last issue, and you weren't even trying to answer that part. :P
my themes when I ran a (GI)14, but you just gave me a thought and... have ascii set to NOT allow ANSI; I bet that means that it won't disp it to ANSI users, hence.... ..... :P I bet when I set that to true it
Ah, yes, that sounds like it could be it!
- to no avail. And it LOOKS like there might be some theme issues in the newest a47 build; some info in the WHATSNEW.TXT... so I'm really
thinking its not me.
default.. named something else. See if Mystic sniffs that one OK. Really weird; I can force a switch to 'ascii', use it... force a switch back - but it won't list it in a normal theme switch menu command.
Anyway, I feel that I learned a LOT about themes... and I still thank
you for that. :P
I had some trouble with the theme editor not saving the fallback choices correctly, but it was corrected as of the 07/06/21 A46 prealpha (for x86_64 in my case).
Yeah, really strange... No error messages in the node*.log logfiles?
turn on 'ask user themes at login' to ON and see if both are listed
there. If they ARE, that might explain that its JUST an issue when using the (GE) 14 menu command to display themes.
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 19:01:47 |
| Calls: | 516 |
| Files: | 6,992 |
| D/L today: |
3 files (36K bytes) |
| Messages: | 288,602 |