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
So I do a notcurses_get and I get a NCKEY_RESIZE back. I naively assumed that I could ask notcurses_term_dim_yx for the new dimensions. Alas these give me the old dimensions. Looking through the code, there is a "update_term_.." function, which I could call. That probably does what I want, but since this is not "official" API, I wonder if I am not walking in a pitfall here. I don't want to render anything at this point.
Ideally of course the new size would be part of ncinput, so I don't have to do this 😉
The text was updated successfully, but these errors were encountered:
hrmmm, i believe notcurses_term_dim_yx() following receipt of the NCKEY_RESIZE ought indeed return the new size. if it's not, that's almost certainly a bug. with that said, resizing is not the cleanest code in notcurses.
you ought not need call anything else. i'll look into this, thanks.
So I do a
notcurses_get
and I get aNCKEY_RESIZE
back. I naively assumed that I could asknotcurses_term_dim_yx
for the new dimensions. Alas these give me the old dimensions. Looking through the code, there is a "update_term_.." function, which I could call. That probably does what I want, but since this is not "official" API, I wonder if I am not walking in a pitfall here. I don't want to render anything at this point.Ideally of course the new size would be part of
ncinput
, so I don't have to do this 😉The text was updated successfully, but these errors were encountered: