Author Topic: Python debugging ... long strings  (Read 726 times)

jporkkahtc

  • Senior Community Member
  • Posts: 2433
  • Hero Points: 202
  • Text
Python debugging ... long strings
« on: September 25, 2020, 09:51:46 pm »
I read an entire file into a variable.

Now "Locals" doesn't work well because Slick doesn't truncate the string.
Its confusing because the "Value" part is many lines and the "Name" part is centered vertically.


So....it would be good for Slick to truncate the display of the string to something reasonable (2-3 lines worth?), while still making the entire contents available with Contents -> Copy, or a separate pop up dialog to display the entire content (with a scrollbar).

It got weirder when I undocked, then redocked locals.
I'll upload a video to support to show the weird behavior.

jporkkahtc

  • Senior Community Member
  • Posts: 2433
  • Hero Points: 202
  • Text
Re: Python debugging ... long strings
« Reply #1 on: September 25, 2020, 10:05:23 pm »
Notice that "match_line" is displayed as if it is huge, when it isn't.
Then when local is docked, match_line is display correctly.

In docked and undocked "line" isn't display well at all.
Line is the variable with a lot of text.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1651
  • Hero Points: 140
Re: Python debugging ... long strings
« Reply #2 on: September 28, 2020, 01:37:07 pm »
The text will be truncated for the next build.

This only part of the fix, because Copy only copies the truncated version, and I'm still need to look into that.