Starting to create custom menus for my system and have ran in to a little snag. I know there is a bullseye.asc file for the bulletins menu, but when I create
a bullseye.ans file it says file not found when loading. Does the system not recognize a .ANS / .RIP etc for the bullseye menu?
Re: Bullseye Menu
By: IronMan to All on Mon Sep 19 2016 04:07 pm
Starting to create custom menus for my system and have ran in to a little snag. I know there is a bullseye.asc file for the bulletins menu, but when I create
a bullseye.ans file it says file not found when loading. Does the system not recognize a .ANS / .RIP etc for the bullseye menu?
Try changing it from bullseye.ans to bullseye.asc
Mojo
---
þ Synchronet þ Mojo's World BBS - mojo.synchro.net
When I renamed it from bullseye.ans to bullseye.asc, the menu will now pull up but it's not showing
any ansi colors. Just plain old ASCII.... Can you not create a bullseye.ans menu? All the other
menus displays ansi menus fine.
Try changing it from bullseye.ans to bullseye.asc
When I renamed it from bullseye.ans to bullseye.asc, the menu will now pull up but it's not showing
any ansi colors. Just plain old ASCII.... Can you not create a bullseye.ans menu? All the other
menus displays ansi menus fine.
Simply renaming an .ans to .asc probably won't work well.. You should run the ans2asc conversion tool (which will convert the ANSI codes to
Synchronet codes).
Starting to create custom menus for my system and have ran in to a little snag. I know there is a bullseye.asc file for the bulletins menu, but when I create
a bullseye.ans file it says file not found when loading. Does the system not recognize a .ANS / .RIP etc for the bullseye menu?
Simply renaming an .ans to .asc probably won't work well.. You should run the ans2asc conversion tool (which will convert the ANSI codes to Synchronet codes).
When I renamed it from bullseye.ans to bullseye.asc, the menu will
now pull up but it's not showing any ansi colors. Just plain old
ASCII.... Can you not create a bullseye.ans menu? All the other menus
displays ansi menus fine.
I haven't looked that closely at the bulletin setup. You could
probably change it to use ans if you wanted but I would just run
ans2asc on your ans file and use the resulting asc file. Don't need to change anything that way.
Try changing it from bullseye.ans to bullseye.asc
When I renamed it from bullseye.ans to bullseye.asc, the menu will
now pull up but it's not showing any ansi colors. Just plain old
ASCII.... Can you not create a bullseye.ans menu? All the other menus
displays ansi menus fine.
Simply renaming an .ans to .asc probably won't work well.. You should
run the ans2asc conversion tool (which will convert the ANSI codes to Synchronet codes).
20 Sep 16 16:06, you wrote to IronMan:
Try changing it from bullseye.ans to bullseye.asc
When I renamed it from bullseye.ans to bullseye.asc, the menu will
now pull up but it's not showing any ansi colors. Just plain old
ASCII.... Can you not create a bullseye.ans menu? All the other menus
displays ansi menus fine.
Simply renaming an .ans to .asc probably won't work well.. You should run the ans2asc conversion tool (which will convert the ANSI codes to Synchronet codes).
ahhhh... so the .asc extension doesn't mean ASCII... i remember when RA introduced similar capability but i never looked into it... i preferred to have
my ASCII screens different from my colored screens... it is something that we might should explore over here a bit more... kinda goofs up the workflow, though, as ya still gotta have ANS screens for thedraw (and similar) to work with before the conversion to asc (not ASCII)...
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDP/IPS yer doin' it wrong...
... Girlfriend wanted. No experience necessary - will train.
---
* Origin: (1:3634/12.73)
I haven't looked that closely at the bulletin setup. You could
probably change it to use ans if you wanted but I would just run
ans2asc on your ans file and use the resulting asc file. Don't need
to change anything that way.
but that doesn't allow for that "looks like walt disney puked here" colors all over the place look that some seem to want...
PS: 5 brownie points to the first one who can say where that quoted phrase comes from ;)
PS: 5 brownie points to the first one who can say where that quoted phrase comes from ;)
PS: 5 brownie points to the first one who can say where that quoted
phrase comes from ;)
I found it, but only thanks to Google. The End (1978).
I never saw the movie, it came out just before I was born. However, anything with Burt Reynolds and Dom DeLuise is usually a good laugh.
Simply renaming an .ans to .asc probably won't work well.. You
should run the ans2asc conversion tool (which will convert the ANSI
codes to Synchronet codes).
ahhhh... so the .asc extension doesn't mean ASCII... i remember when RA introduced similar capability but i never looked into it... i preferred to have my ASCII screens different from my colored screens... it is something that we might should explore over here a bit more... kinda goofs up the workflow, though, as ya still gotta have ANS screens for thedraw (and similar) to work with before the conversion to asc (not ASCII)...
Simply renaming an .ans to .asc probably won't work well.. You
should run the ans2asc conversion tool (which will convert the ANSI
codes to Synchronet codes).
ahhhh... so the .asc extension doesn't mean ASCII... i remember when
RA introduced similar capability but i never looked into it... i
preferred to have my ASCII screens different from my colored
screens... it is something that we might should explore over here a
bit more... kinda goofs up the workflow, though, as ya still gotta
have ANS screens for thedraw (and similar) to work with before the
conversion to asc (not ASCII)...
Well .asc does mean ASCII.. But with Synchronet, an .asc file can
also contain Synchronet attribute codes, and Synchronet will either display them or strip them, depending on whether the user's terminal supports ANSI or not.
And I suppose renaming an .ans to .asc could work.. Synchronet would probably simply send the contents to the user, and if their terminal supports ANSI, then it would interpret and display the ANSI codes.
Since Synchronet can intelligently strip its color codes if needed,
I've been in the habit of simply having .asc files that contain
Synchronet codes. I do have to use asc2ans whenever I want to edit
one with TheDraw, then convert back using ans2asc, which makes the workflow perhaps a little more tedious than it should be.
I wasn't sure if I wanted a separate .ans and .asc version of most of
my files - but I suppose that wouldn't really be much of an issue.
Ok, I am creating my bullseye bulletin menu but have added more than 9 bulletins so of course
when you try to load the 10th one you hit (10) but it of course takes you to the number 1 bulletin.
How could you do this?? would you have to turn off hot keys in order to have over 9 bulletins
posted? Noticed the Vertrauen just has 9 also so I figure I'm not the only one.
Is there a way to turn hot keys off for just the bullseye menu and not the entire BBS?
Sysop: | Ragnarok |
---|---|
Location: | Dock Sud, Bs As, Argentina |
Users: | 136 |
Nodes: | 10 (0 / 10) |
Uptime: | 51:20:11 |
Calls: | 15,173 |
Files: | 19,862 |
D/L today: |
25 files (5,097K bytes) |
Messages: | 1,693,371 |