| | [ Return to Bugs & Features | Post Text | Post File | Prev | Next ]
STR #2792
| Application: | FLTK Library |
|---|
| Status: | 5 - New |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Change of logic used on browser_ when no selection |
|---|
| Version: | 1.4-feature |
|---|
| Created By: | dfatfl |
|---|
| Assigned To: | Unassigned |
|---|
| Fix Version: | Unassigned |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
[ Post File ]
Trouble Report Comments:
[ Post Text ]
| |
| #1 | dfatfl
21:26 Dec 09, 2011 |
| This patch changes how the selection of an item in a browser_ widget is selected if there is no selection on a hold (or checkbox) type browser. Basically up selects bottom, down selects first, previously down would select second item, first never selected. The local variable name was changed to make more since (so it shows more changes that actually occurred). Basically now browser_ of that type can send an item_next or item_prev request with a null value so all derived classes need to be able to handle a null. | |
| |
| #2 | AlbrechtS
03:35 Feb 07, 2019 |
| Moved from 1.3-feature to 1.4-feature.
This STR has been superseded, see also cumulative patch in STR 3485:
https://www.fltk.org/str.php?L3485 | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |
FLTK Apps 
