FLTK logo

STR #543

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 Home  |  Articles & FAQs  |  Bugs & Features  |  Documentation  |  Download  |  Screenshots  ]

Return to Bugs & Features | Roadmap 2.0 | Post Text | Post File | SVN ⇄ GIT ]

STR #543

Application:FLTK Library
Status:4 - Pending
Priority:1 - Request for Enhancement, e.g. asking for a feature
Scope:3 - Applies to all machines and operating systems
Subsystem:Core Library
Summary:can't change position of Fl_Input_ subclasses through position()
Created By:mberghma.pandora
Assigned To:spitzak
Fix Version:Unassigned
Update Notification:

Receive EMails Don't Receive EMails

Trouble Report Files:

Post File ]

No files

Trouble Report Comments:

Post Text ]
Name/Time/Date Text  
#1 mberghma.pandora
03:01 Sep 24, 2004
The position(x, y) function of Fl_Widget is hidden in the Fl_Input_ class through 'function hiding'.

(The new function changes the cursor position.)

Now, to do a general layout change of e.g. a Fl_Output**, you can't use the position(x,y) anymore in the same way as other classes would, unless you use Fl_Widget::position(x,y) explicitly, or resize(x,y,w,h) (my current solution).

Since I find this confusing, and I don't think this is an intended feature, I was wondering if you could change the Fl_Input_ interface a little to make this work again...


PS: maybe this happens in more than 1.1.5rc2 but that's te one I use now.
#2 mike
06:35 Sep 24, 2004
We can't change the API in 1.1.x, as that would break binary compatibility.

Reassigning to 2.0 where we may be able to change this (might, in fact, already be changed...)
#3 spitzak
12:38 Sep 26, 2004
Not fixed in 2.0 yet, but it should be. Probably the fix is to rename Input::position to something else, but I'm not sure what. cursor() sounds the best but there is already a Widget call by that name. Perhaps point() (ie there is a point() and a mark()). Or insertion_point()? Any other ideas?


Return to Bugs & Features | Post Text | Post File ]


Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.