You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, cool library for doing vt100 with a small footprint. Theres an issue with text style generation i encountered once stuff starts to get a bit more complicated than just a hello world.
Basicly, the main issue, I think, is with the toString() (or maybe with diff algos). I had bgMod or fgMod ending up with a "0" then it will reset basicly everything before that - even the background color just applied. defaultMod() can also write "0" but is less of an issue i guess.
A workaround seems to be: just specify both colors on all styles you use, then you don't run into it !
I tried to fix it naively, but found out the steps that have been taken to not reapply the same styles, etc. when writing out, and this complicates the matter.
The member function on "Style" we are talking about:
Hey, cool library for doing vt100 with a small footprint. Theres an issue with text style generation i encountered once stuff starts to get a bit more complicated than just a hello world.
Basicly, the main issue, I think, is with the toString() (or maybe with diff algos). I had bgMod or fgMod ending up with a "0" then it will reset basicly everything before that - even the background color just applied. defaultMod() can also write "0" but is less of an issue i guess.
A workaround seems to be: just specify both colors on all styles you use, then you don't run into it !
I tried to fix it naively, but found out the steps that have been taken to not reapply the same styles, etc. when writing out, and this complicates the matter.
The member function on "Style" we are talking about:
The text was updated successfully, but these errors were encountered: