Author Topic: debugger plugin's tip windows does not show content with horizontal scroll bar  (Read 1140 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6113
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Hi, if the horizontal scroll bar exists, the content get covered, see the 2 images in the attachment.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2894
This is caused when the popup window size is wider than the space left to the right edge of the parent window.

For example: When this happens, move the editor window to the left to allow room for the full popup window. Show the data again,
then the popup window will show correctly.

I know this isn't a fix. ..just sayin'...
« Last Edit: October 22, 2025, 07:45:31 am by Pecan »

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6113
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Thanks. Can we dynamically change the outer window size? Well, we still need to find a way to fix such issue, though this is not a big issue.  :)
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6113
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Not the debug tip window, sometimes, the code completion tip(from the clangd_client plugin) window becomes extremely large, see the blow two screen shot, the tip window cover the whole C::B window, also the tip window extended to another screen.  :(
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2894
Not the debug tip window, sometimes, the code completion tip(from the clangd_client plugin) window becomes extremely large, see the blow two screen shot, the tip window cover the whole C::B window, also the tip window extended to another screen.  :(

 Is there any way you could tell me what "auto" actually is or give me an example as to how to re-create the situation you're showing here?

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6113
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Is there any way you could tell me what "auto" actually is or give me an example as to how to re-create the situation you're showing here?

You can simply do this:

1, clone the code repo or download the zip file:  asmwarrior/parserlib: A c++ recursive-descent PEG parsing library that supports left recursion..

2, open the cbp project in the root folder: https://github.com/asmwarrior/parserlib/blob/master/test_parser_lib.cbp

3, open the file: cpp_lexer_grammar.h in the C::B editor

4, you can use clangd_client, and use the mouse to hover the "token" variable in the line 172

5, you will see a very big tip window which cover the whole screen, note I only tested on Windows 10 OS.

Thanks.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.