NVPY fails during synchronisation

[Stefan Storåkers]

Enclosed is the log file with all error messages.

As it is now the application starts and then dies after a few seconds.

[平野 勇輝]

That is a known issue. The mitigation has been available on the master branch. Could you try to use the development version and check whether the problem is solved?

The following commands can start the development version.

git clone https://github.com/cpbotha/nvpy.git
cd nvpy
python3 -m nvpy

On 10/27/21 11:29 PM, Stefan Storåkers wrote:

Enclosed is the log file with all error messages.

As it is now the application starts and then dies after a few seconds.

--
You received this message because you are subscribed to the Google Groups "nvpy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvpy+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nvpy/ecd93e01-b932-4131-b221-dec9404ffd1dn%40googlegroups.com.

[Stefan Storåkers]

The problem is not solved.

The following errors were reported when I ran the app.

X Error of failed request:  BadLength (poly request too large or internal Xlib length error)
  Major opcode of failed request:  139 (RENDER)
  Minor opcode of failed request:  20 (RenderAddGlyphs)
  Serial number of failed request:  51195
  Current serial number in output stream:  51195

Looking forward for a solution to this problem.

[平野 勇輝]

Probably the error was caused by the non-BMP character. See https://github.com/cpbotha/nvpy/blob/master/docs/ucs-4.rst for a workaround.

The tk does not support non-BMP characters sufficiently. To completely solve this problem, we need to switch to another UI library. It takes time and effort, so it does not realize yet.

To view this discussion on the web visit https://groups.google.com/d/msgid/nvpy/16aaf80e-fe0b-4203-81f5-a2728493f8c9n%40googlegroups.com.

-- 
平野 勇輝 (Yuki HIRANO)
yuuk...@gmail.com