-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fl_Input_::position shadowing Fl_Widget::position #69
Comments
Thanks for the heads-up. This is true, however it would need an API change which we try to avoid as much as possible. One possible solution: deprecate |
Oh, I thought that 1.4 is not considered stable, so API changes are still possible. |
Thanks for your feedback. To explain: we try to keep the API (Application Programming Interface) across all versions so developers don't need to change their program code from one FLTK version to another. You could still compile most of FLTK 1.1 code with 1.3 (with a few minor exceptions) and so you will with 1.4. The ABI (Application Binary Interface) however is not yet final for 1.4, it can still be modified until 1.4.0 gets released, but must be constant during 1.4.x releases. |
FTR: I noticed that
This is just a reminder - code not yet checked. |
Note: we have more than only the methods mentioned above shadowing Fl_Widget::position(). This is what I found (may not be complete):
I wonder if it's worth the effort to change any of these methods, particularly since we need to keep the API for backwards compatibility anyway, at least for some (indefinite) time and you can always use Fl_Widget::position(X, Y) explicitly. Just thinking aloud: maybe we could add another method like Fl_Widget::set_position(int X, int Y) so users can use this instead (w/o a name conflict). |
PR is in #666
|
Just for the record: isn't this |
Yep, I changed my mind when implementing it. Fixed. |
In FLTK version 1.3 Fl_Input_::position method is shadowing Fl_Widget::position virtual method.
Maybe it's time to fix it in 1.4?
The text was updated successfully, but these errors were encountered: