Greg Ercolano wrote:
Before these become 'written in stone' when fltk.1.3.x releases,
can they be changed to something more readable, like:
FL_SORT_ASCEND
FL_SORT_DESCEND
I think that does sound better. +1
IMHO, FL_SORT_ASCENDING and FL_SORT_DESCENDING would be even better.
Before these become 'written in stone' when fltk.1.3.x releases,
can they be changed to something more readable, like:
FL_SORT_ASCEND
FL_SORT_DESCEND
I think that does sound better. +1
IMHO, FL_SORT_ASCENDING and FL_SORT_DESCENDING would be even better.
Agreed, even
I noticed these two new defines in Fl_Browser_.H for 1.3.0:
#define FL_SORT_ASC0 /** sort browser
items in ascending alphabetic order. */
#define FL_SORT_DESC 1 /** sort in
descending order */
Before these become 'written in stone' when
Before these become 'written in stone' when fltk.1.3.x releases,
can they be changed to something more readable, like:
FL_SORT_ASCEND
FL_SORT_DESCEND
I think that does sound better. +1
IMHO, FL_SORT_ASCENDING and FL_SORT_DESCENDING would be even better.
D.
MacArthur, Ian (SELEX GALILEO, UK) schrieb:
I noticed these two new defines in Fl_Browser_.H for 1.3.0:
#define FL_SORT_ASC0 /** sort browser
items in ascending alphabetic order. */
#define FL_SORT_DESC 1 /** sort in
descending order */
Before
I noticed these two new defines in Fl_Browser_.H for 1.3.0:
#define FL_SORT_ASC0 /** sort browser items in ascending
alphabetic order. */
#define FL_SORT_DESC 1 /** sort in descending order */
Before these become 'written in stone' when fltk.1.3.x
