If the user is getting a black screen, then you've done something wrong. Yes, the BBS "fallsback" to just the main.msg or main.sc if main.XXcol.\* doesn't exist. That's how it already works. It does *not* fall back to the "Next largest" size. That is something I'll ponder and keep this issue open for.I do see that I didn't have a basename.ext file - definitely my misunderstanding of the docs. But since the main.ext would most likely be a 80x24 screen it still has issue of having the smallest file being displayed on a 160x45 terminal, despite a 132x37 file existing. I know it's not an emergency but more and more boards are experimenting with widescreen and these are just things that I've noticed since doing so with synchronet. If other sized columns start being used, will we have to create a file for each one of them? > As for your random menu problem, you need a .msg or .asc file for *each* base filename. Just convert those .ans to .msg and get rid of the .ans version unless you really need the animation sequences.Using bbs.menu('random*') will display all files that start with random, without taking into consideration the xxcol portion of the name. So on a 132 column screen I see random.msg, random.132col.msg and random.80col.msgRegarding conversion - I have come across several screens like ones with extended colors and custom glyph fonts that do not convert properly, even with the -ice and -132 arguments. Artists are doing a lot with ansi lately, why convert to a format non-native to their original work to use features like randomizing or bbs.menu_exists() when bbs.menu() displays them just fine as ANS otherwise? Why gatekeep randomizing!? (I'm kidding! haha)I've attached some examples in pablodraw and in syncterm with the output and the command I used to convert.After a bunch of experimenting I see randomizing doesn't work when using a full path to the file - that was a big part of my issue (that and not having them all as .msg files as I thought I only need one as the basename.msg and the rest could be other extensions. I have menus and other files all over the place in an attempt to keep them organized. lolI looked over the wiki and this may the source of my misunderstanding.> Each of these file types may be preempted by a terminal-width specific file with a name ending in .Xcol.ext where X is the (exact) number of screen columns (e.g. usually 80 or 40) and .ext is one of the supported file extensions from the above list.> If you only have one display file for any particular base filename, it should have either a .msg or .asc extension and contain no terminal-control sequences (e.g. ANSI, PETSCII, or RIP).This sounds to me as if I only have one display file, it must be a .msg or .asc - otherwise the "menu/display file selection priority list" has .ans at the very top. Why give .ans 1st priority if it doesn't seem to work with a couple of the features of bbs.menu()? I apologize for the wall of text!Anyway, I appreciate all you do and all the work you put into synchronet. Thank you for pondering this request!--- SBBSecho 3.15-Linux
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 12 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 06:47:10 |
| Calls: | 113 |
| Calls today: | 1 |
| Files: | 50,349 |
| D/L today: |
53 files (10,144K bytes) |
| Messages: | 297,046 |