1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
FAQs
====
Why?
- Why not?
- To improve and extend the capabilities of CLI and TUI applications.
- Terminals emulators have always been and always will be!
What about Windows support?
- Only the new `Windows Terminal <https://github.com/microsoft/terminal>`_ seems to have proper ANSI support and mordern terminal emulator features.
- Drawing images and animations doesn't work completely well with Python for Windows. See :doc:`issues`.
- If stuck on Windows and want to use all features, you could use WSL + Windows Terminal.
Why are colours not properly reproduced with :py:class:`BlockImage`'s ``DIRECT`` render method?
- Some terminals support direct-color control sequences but actually use a **256-color pallete**. This limits color reproduction.
Why are images out of scale?
- If :ref:`auto-cell-ratio` is supported and enabled, call
:py:func:`~term_image.enable_win_size_swap`. If this doesn't work,
then open an issue `here <https://github.com/AnonymouX47/term-image/issues/new>`_
with adequate details.
- Otherwise, adjust the :term:`cell ratio` using :py:func:`~term_image.set_cell_ratio`.
.. _query-timeout-faq:
Why does my program get garbage input (possibly also written to the screen) or phantom keystrokes?
- This is most definitely due to slow reponse of the terminal emulator to :ref:`terminal-queries`.
- To resolve this, set a higher timeout using :py:func:`~term_image.set_query_timeout`. The default is :py:data:`~term_image.DEFAULT_QUERY_TIMEOUT` seconds.
- You can also disable terminal queries using :py:func:`~term_image.disable_queries` but note that this disables certain :ref:`features <queried-features>`.
|
