You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can boxes be added to stock menus that are absent of .mnu, .msg, or .ans files? Allowing the SysOp to create line design (single, double line, etc..), color, and box style. The goal would be to be able to use the awesome auto detect terminal width and auto adjust menu columns. This would then also add the correct number of ansi line characters to the box to fit the users terminal size. EChicken did this to his Synchronet BBS for an example be it 40 column, 80, 132, 160 etc...
The text was updated successfully, but these errors were encountered:
Hmmm .. echicken has auto scaling menus based on terminal size. And mystic has box selection types within the theme editor. One can pick color and style of line. WWIV is ahead of the game by having auto scaling (to terminal size) menu width. It would be nice to see the border around it follow suit. If I were to say edit the transfer menu using the menu editor, pick the color and style of line I wanted, and call it a day. It would be neat to see it adjust to terminal width. Not sure if that is of help, just a feature request. The alternative is doable by simply having different.132.ans files for each terminal width, just not always easily modified in menus such as chains when games are added, each ANSI would then also require being changed. It's a convenience feature and snappy.
Can boxes be added to stock menus that are absent of .mnu, .msg, or .ans files? Allowing the SysOp to create line design (single, double line, etc..), color, and box style. The goal would be to be able to use the awesome auto detect terminal width and auto adjust menu columns. This would then also add the correct number of ansi line characters to the box to fit the users terminal size. EChicken did this to his Synchronet BBS for an example be it 40 column, 80, 132, 160 etc...
The text was updated successfully, but these errors were encountered: