I wouldn’t call this a bug - but why does “ScrollWidow” use ‘winid’ and not ‘id’ for the parameters??? It is not consistent with the most of the rest of the classes.
I may have discovered other similar such issues - so there may be a reason. So anybody knows let me know please.
Where do you see that? The ScrollWindow function within wx.Window doesn’t take a window identifier – it scrolls its “self”. There is a ScrollWindow function in win32gui, but that takes a native operating system window handle, which is entirely different from a wx ID.
I wouldn’t call this a bug - but why does “ScrollWidow” use ‘winid’ and not ‘id’ for the parameters??? It is not consistent with the most of the rest of the classes.
—
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
I wouldn’t call this a bug - but why does “ScrollWidow” use ‘winid’ and not ‘id’ for the parameters??? It is not consistent with the most of the rest of the classes.
Where do you see that? The ScrollWindow function within wx.Window doesn’t take a window identifier – it scrolls its “self”. There is a ScrollWindow function in win32gui, but that takes a native operating system window handle, which is entirely different from a wx ID.
“ScrollWidow” use ‘winid’ and not ‘id’ for the
parameters??? It is not consistent with the most of the
rest of the classes.
Where do you see that? The ScrollWindow function within
wx.Window doesn’t take a window identifier – it scrolls its
“self”. There is a ScrollWindow function in win32gui, but
that takes a native operating system window handle, which is
entirely different from a wx ID.
class is manufactured on the fly for wxPython. (in C++ it’s a
macro that evaluates to a template expansion IIRC.) I’ve created
an issue for it so I don’t forget about
it.
–
You received this message because you are subscribed to the Google
Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it,