| Subject: | Tickit::Window warnings when cursor position is not set |
It seems to be quite easy to end up with code where $win->{cursor_line} / {cursor_col} are undef, causing Tickit::Window->restore and related code throw warnings.
From a quick look through the code, you'd need to call ->cursor_at for those values to be set. Not sure what the right thing to do here is, but defaulting to (0,0) either in ->restore or when initially creating the window might at least silence the warnings. Alternatively, raising a more informative warning ("cursor position not set") would at least help identify the cause for widget authors?
cheers,
Tom