T-ui report and discussion

[juewuy]

Add your BUG report or Feature for T-ui here!
请在此处提交关于T-ui的BUG或者建议！

[juewuy]

The first bug ，on Xiaomi router @sofia-riese

[sofia-riese]

The first bug ，on Xiaomi router [@sofia-riese](https://github.com/sofia-riese)

OKay, I will try my best to fix it as soon as possible. If you have any other questions about TUI, please feel free to ask.

[sofia-riese]

@juewuy

The current issue encountered is: automatic line breaks splitting characters cause color codes to be lost or become ineffective.

I have resolved this issue by refactoring the content_line function. However, the refactored version utilizes syntax or features specific to Bash.

To maintain maximum compatibility, I haven't yet figured out how to fully convert it to a POSIX-compliant version.Is it acceptable that the script relies on Bash-specific functionality?

[sofia-riese]

@juewuy

The current issue encountered is: automatic line breaks splitting characters cause color codes to be lost or become ineffective.

I have resolved this issue by refactoring the content_line function. However, the refactored version utilizes syntax or features specific to Bash.

To maintain maximum compatibility, I haven't yet figured out how to fully convert it to a POSIX-compliant version.Is it acceptable that the script relies on Bash-specific functionality?

Alternatively, this part of the code could be implemented in another high-level programming language (such as Golang), and then compiled into a binary file for use, thus solving the cross-platform issue. What's your opinion?

[juewuy]

@sofia-riese Sorry, this is not acceptable. Compatibility with ash is mandatory.

If there is no good solution at the moment, we can put this aside for now and revisit the necessity of automatic line wrapping after the localization work has progressed further.

[sofia-riese]

@sofia-riese Sorry, this is not acceptable. Compatibility with ash is mandatory.

If there is no good solution at the moment, we can put this aside for now and revisit the necessity of automatic line wrapping after the localization work has progressed further.

Got it.

I might need an AI assistant to see if I can find a fully POSIX-compliant implementation.

I'll keep refining that section of the code and update here if there's any progress.

[juewuy]

@sofia-riese Alright, thank you for your efforts, and best of luck.

[sofia-riese]

I'm pondering an issue: The “TABLE_WIDTH” parameter in the current tui_layout.sh script is fixed at 60. However, terminals running on mobile devices may have width limitations, leading to the layout issues shown in the image above.

To resolve this problem, the following approaches can be taken:

1. Modify the script to automatically detect the terminal's width. When the terminal width doesn't meet the “TABLE_WIDTH=60” requirement, dynamically adjust the “TABLE_WIDTH” parameter to fit the current terminal width.
   This approach is most user-friendly but poses development challenges and increases the script's code volume.

2. Provide prompts or instructions. If layout errors occur, advise users to manually reduce the terminal's font size to increase its width.

3. Inform users to directly modify the “TABLE_WIDTH” parameter in tui_layout.sh. This is the most direct approach but presents operational difficulty for users unfamiliar with Linux commands.

4. Add a function to modify the “TABLE_WIDTH” parameter within the existing main menu's function 8 “Tools & Optimization,” allowing users to adjust it themselves. I believe this method strikes a perfect balance between development difficulty and user-friendliness.

What do you think? @juewuy