| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #747
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Patch (alpha) for Fl_File_Chooser2 |
|---|
| Version: | 1.1.6 |
|---|
| Created By: | Natevw |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1-current (SVN: v4189) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | Natevw
22:51 Mar 04, 2005 |
| type(int) "Sets or gets the current type of Fl_File_Chooser."
It is desirable to select whether or not user is allowed to choose multiple files. However, if the value() is set after the type() is set, MULTI will get switched back to SINGLE - overriding an explicit choice of the class utilizer to allow multiple file selections.
This may be desirable (and perhaps implemented) as a means of showing whether or not a single file is returned. N.b. that there is a method, count(), which provides such information. It seems advisable to use type() for defining what actions are permitted in the chooser, and count() to see how many files are chosen. The overrriding of a previously set type() is not a documented feature.
However, if this would break existing implementations of this class, it should also be noted that Fl_File_Chooser provides a directory() method which can change the current directory without "messing with" the type. If this is the case, the internal change of type() should be documented.
-nate
| |
| |
| #2 | mike
09:28 Mar 25, 2005 |
| Fixed in Subversion repository.
| |
[ Return to Bugs & Features ]
|
| |
