Closed indrekj closed 14 years ago
Yes, I did not know anyone was looking ;-) Pad extends Window and adds methods to it.
I would not really expect a user to be doing anything that has to differentiate between these, actually the widgets may be concerned, And this is only if you are embedding one widget inside another such as SplitPane or Scrollpane (and also TabbedPane).
Perhaps you are using some older code. There are major changes happening. I now only use pads if you are embedding. Thus, for all other practical purposes all widgets would be only using one window class and writing to it.
The difference between pads and windows only comes in Class Form in def repaint where i check the type and either call wrefresh or buffer_to_screen depending on type.
I am currently working on textviews within splitpanes and its coming along fine.
if @window.window_type == :WINDOW
@window.wrefresh
else
if @parent_buffer!=nil
@window.set_backing_window(@parent_buffer)
@window.copy_pad_to_win
end
end
From rwidget.rb, class Form, def repaint.
Just checked Yes TabbedPane is broken due to some major change in Form and Widget (and Window).
I will get around to rectifying it asap. Thanks.
Someone is always watching :P
Thanks for the info. That was fast.
In VER::Pad#copy_pad_to_win: @otherwin is not always a Pad object. It is sometimes a VER::Window object, but VER::Window does not have the
smaxrow
method.code and error log: http://gist.github.com/273597
I now that rbcurse19 is under development, but just letting you know.