Having a hard time trying to get the system to recognize where to load
the menu screens from.
When you create a new theme, it asks where your text, menu and script paths are. Made the necessary additions, and the menus are created in
the correct path, but whenever I edit a menu and try and use a screen
from that specific path (which I figured it would pull from the Edit
Theme screen), it wants to keep loading the default TEXT path screens.
Anyone else have an issue like this?
Having a hard time trying to get the system to recognize where to load the menu screens from.
When you create a new theme, it asks where your text, menu and script paths are. Made the necessary additions, and the menus are created in the correct path, but whenever I edit a menu and try and use a screen from that specific path (which I figured it would pull from the Edit Theme screen), it wants to keep loading the default TEXT path screens.
Anyone else have an issue like this?
--- Mystic BBS v1.12 A31 (Windows)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)
Having a hard time trying to get the system to recognize where to load
the menu screens from.
When you create a new theme, it asks where your text, menu and script paths are. Made the necessary additions, and the menus are created in
the correct path, but whenever I edit a menu and try and use a screen
from that specific path (which I figured it would pull from the Edit
Theme screen), it wants to keep loading the default TEXT path screens.
Anyone else have an issue like this?
On 01/17/17, maskreet said the following...
Having a hard time trying to get the system to recognize where to loa the menu screens from.
When you create a new theme, it asks where your text, menu and script paths are. Made the necessary additions, and the menus are created in the correct path, but whenever I edit a menu and try and use a screen from that specific path (which I figured it would pull from the Edit Theme screen), it wants to keep loading the default TEXT path screens
Anyone else have an issue like this?
I know that the different themes have the ability to 'fall back' to the default theme. Maybe if you have the option turned on to 'fall back',
you might turn that off and see if the problem persists.
Having a hard time trying to get the system to recognize where to load
the menu screens from.
When you create a new theme, it asks where your text, menu and script paths are. Made the necessary additions, and the menus are created in
the correct path, but whenever I edit a menu and try and use a screen
from that specific path (which I figured it would pull from the Edit
Theme screen), it wants to keep loading the default TEXT path screens.
On 01/17/17, maskreet pondered and said...
Having a hard time trying to get the system to recognize where to loa the menu screens from.
When you create a new theme, it asks where your text, menu and script paths are. Made the necessary additions, and the menus are created in the correct path, but whenever I edit a menu and try and use a screen from that specific path (which I figured it would pull from the Edit Theme screen), it wants to keep loading the default TEXT path screens
OK so assuming you have the paths and files set up for the theme.. the issue is you can't access that theme - right?
Assuming your theme is called 'test' minus the quotes
Do you have a test.txt file in the data directory that you cloned from default.txt file?
Do you allow users when logging in to select that theme?
If you are just testing your new 'test' theme out for yourself and have not opted to choose it from the options presented from login (assuming
you turned that on) have you updated the file name of the theme to use against your user record?
Config > User Editor > Page 2 > Theme
Hello Gryphon!
You posted some time ago the included mpl for changing message area's in mystic.
Would you have an updated one I could try, as this has issues going to area's.
I've found that when selecting an area it's not choosing the area I
moved the cursor to.
Also I have 230+ area's in the fidonet group, is bumping the "Var Bases' area to 300 enough to
cater for a group with that many area's?
I've found that when selecting an area it's not choosing the area I moved the cursor to. Vo> Also I have 230+ area's in the fidonet group, is bumping the "Var Base" area to 300 enough to
cater for a group with that many area's?
You can bump to a max of 500 for the areas before having to do things outside that array. So increasing it should help fix the issues you are having also their are a few more alternatives out there as well from
xqtr and some others you can try and use as well. =)
On 01/25/17, Pequito said the following...
I've found that when selecting an area it's not choosing the are moved the cursor to. Vo> Also I have 230+ area's in the fidonet group, is bumping the "Var Base" area to 300 enough to
cater for a group with that many area's?
You can bump to a max of 500 for the areas before having to do things outside that array. So increasing it should help fix the issues you having also their are a few more alternatives out there as well from xqtr and some others you can try and use as well. =)
The problem is that they don't work on my system. Even when using them
in the area change for the four fsx areas. I can select the mystic echo (fourth one on my system), but it wont change to that area and stays on the first area (fsx netmail) on my system....
I've been running the stock mystic area change menu command for ages due to these issues. The group change is usiung the go-fgrp/go-mgrp scripts and work fine.
May I suggest you give a try to bt-gasel-1.0a.zip if you have some spare time ? It a complete rewrite of original code with the area-bug fixed
Hello Fabian, bt-gasea is great but on my system having more than 2000 message areas, it does not work, any chance you can change this? Thanks.
I'm on it. I'l have to do some cleanup although since memory is short under MPL (no object bigger than 65k). I'll be back shortly.
Fabian
Hello Fabian, bt-gasea is great but on my system having more than 2000 message areas, it does not work, any chance you can change this? Thanks.
If you have more than 1450 areas in a single group, I sadly can't help
you now and the only way would be to split your groups in smaller
subsets.
I've been running the stock mystic area change menu command for ages to these issues. The group change is usiung the go-fgrp/go-mgrp scrip and work fine.
I did call your system, it must not be avail for us normal users for
group change etc, guessing its op only for now till you figure it out?
I never used any others and made my own but know how they work and or
how to make em work when you have em.
The one from xqtr does not work for you?
May I suggest you give a try to bt-gasel-1.0a.zip if you have some spare time ? It a complete rewrite of original code with the area-bug fixed (when area ID is not the same as area number in list, when you delete
and add/insert new areas) ? It's the very same script to does the job
for group/base selection for files and messages. Customizable with easy
to use templates...
Let me know if you can't find it or if you want me to repost it
somewhere ...
May I suggest you give a try to bt-gasel-1.0a.zip if you have some sp time ? It a complete rewrite of original code with the area-bug fixed
Hello Fabian, bt-gasea is great but on my system having more than 2000 message areas, it does not work, any chance you can change this? Thanks.
I just tryed to connect to your system, and got a black screen and then nothing. Had to hangup.
If you have more than 1450 areas in a single group, I sadly can't hel you now and the only way would be to split your groups in smaller
That's fine Fabian. thanks my friend :)
If you have more than 1450 areas in a single group, I sadly can' you now and the only way would be to split your groups in smalle
That's fine Fabian. thanks my friend :)
I had a few ideas last night ; sleep is always so productive o_O
I'll keep you posted.
The way I over-came this issue was to read all the areas, store them into their own data file and read it back showing the listing.
The way I over-came this issue was to read all the areas, store them their own data file and read it back showing the listing.
That's a good way to solve that problem, but you duplicate data and that is usually not the best way since duplicated data tends to be obsolete :S
I'll most probably try to maintain a memory buffer of a subset of all available areas, and load/unload the buffer as required ; that could be fast for the user and not that heavy for the system. The only difficult part is for a dynamic search since you don't have everything in ram,
this part needs to be solved.
BTW, is your mpl available somewhere ? I would gladly have a look at
what you wrote :)
If you have more than 1450 areas in a single group, I sadly can't hel
That's fine Fabian. thanks my friend :)
Good news ! Excellent news in fact !! Problem is solved :) I have dynamic buffer working:))))))))))))
Good news ! Excellent news in fact !! Problem is solved :) I have dyn buffer working:))))))))))))
Just to let you know the progress I made this week-end. Buffered navigation induced heavy headhaches when moving backwards, due to non sequential internal Mystic ID for groups/areas that occurs during insert/delete.
Hello Gryphon!
You posted some time ago the included mpl for changing message area's in mystic.
Would you have an updated one I could try, as this has issues going to area's.
I've found that when selecting an area it's not choosing the area I
moved the cursor to.
Also I have 230+ area's in the fidonet group, is bumping the "Var Bases' area to 300 enough to
cater for a group with that many area's?
Yeeeeha ! bt-gasel v1.1a is released ! It is able to generate lightbar menus for groups and areas selection for up to 30,000 items in each category. There is still a limit though, which I'd prefer not, but I
Source has been uploaded on some BBS, and is available at my place of course, with the name of bt-gasel-1.1a.zip
[...]You posted some time ago the included mpl for changing message area's
cater for a group with that many area's?
I think that if you bump up the Var Bases to 300 would fix your problem,
But on the other hand, I think that pequito had managed to make a MPL to do exactly what you are wanting. Maybe he can help you with it.
like you thought. But I have to confess, I don't use that anymore, ever since g00r00 came out with the new file_list format. I've just went
working good sofar. I'm about to put it through more tests, as the previous version would crash mystic.
Please upload to Agency BBS and I will hatch it out to all systems connected to the FSX_MUTL file area :)
The way I over-came this issue was to read all the areas, store them their own data file and read it back showing the listing.
That's a good way to solve that problem, but you duplicate data and that is usually not the best way since duplicated data tends to be obsolete :S
I'll most probably try to maintain a memory buffer of a subset of all available areas, and load/unload the buffer as required ; that could be fast for the user and not that heavy for the system. The only difficult part is for a dynamic search since you don't have everything in ram,
this part needs to be solved.
Hi Gryphon,
like you thought. But I have to confess, I don't use that anymore, e since g00r00 came out with the new file_list format. I've just went
Do you have any info on that, somewhere ?
bt-gasel-1.1c.zip was just uploaded to the Agency BBS in local files/uploads. A quick fix for a malfunctional PageUp key. Should be
fine now.
Suggest you limit your text in the file_id.diz to just 40 columns and say 7-10 lines long. The rest of the info I would put in a separate text
Do you want to just have a crack at that before I send it out?
I'm off painting my house again this Saturday morning so will be looking
I'll follow your guidelines, my Master :) Your teaching is pure wisdom.
Updated file will be uploaded in a few minutes
I'm off painting my house again this Saturday morning so will be look
I wish you good luck, so much work
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 72:39:24 |
Calls: | 2,119 |
Files: | 11,149 |
D/L today: |
45 files (9,960K bytes) |
Messages: | 950,581 |