Copyright © 2007-2008 Diggory Hardy
License: GNU General Public License version 2 or later (see COPYING)


In progress:



To do (importance 0-5: 0 pointless, 1 no obvious impact now, 2 todo sometime, 3 useful, 4 important, 5 urgent):
Also search for FIXME/NOTE/BUG/WARNING comment marks.
4   Should only have one instance of context menu widgets. Service menu callbacks don't get removed!
3   Closing menus when release-click is not on menu or parent (ordinary & context).
3   Dragging and dropping of editable data: should content immediately appear as being dragged?
3   Dragging from anything other than AStringContentWidget.
3   Single-line edit: pressing return should lose keyboard focus and change value
3   Enable dragging from more widgets: bool content, enum
3   Content: setContent specialisations, opAssign should reject more values (particularly for BoolContent).
3   GUI: up-clicks get passed as events and activate objects
3   Widget saving: how to deal with modifier functions, esp. when they discard parameters? Remove feature except for dimdata and handle gui editing separately?
3   Windows compatibility - no registry support (useful to find path).
2   Optimise: memory/reuse of popupContext and dragContentDisplay (in WidgetManager).
2   Check for unnecessary redraws (associated with mouse movement, not clicking).
2   First glyph drawn incorrectly in release mode - ??
2   glBindTexture not working with non-0 index - perhaps use a higher level graphics library at some point.
2   Popup help boxes on hover/right click to display content description.
2   Options need a "level": simple options, for advanced users, for debugging only, etc.
2   Command-line options for paths to by-pass normal path finding functionality.
2   Sensitivity adjustments. From es_a_out:
        /+ FIXME: revise.
        + I can't see any point using HALF_RANGE here, since it should really be used dependant on
        + the device attached, not the axis. Also what about adjusted range like X3's throttle?
        +
        + Sensitivity: is this the right place to adjust it? For things like throttle where the
        + ends of the interval must remain fixed, multiplying cannot be used to adjust and adjusting
        + the curve via a power function doesn't seem to be what we want. For things where the
        + end points needn't remain fixed, multiplying seems the right thing to do, but cannot be
        + done here since we don't know the end points can be changed.
        
        real y = x;
        uint conf = s.pop();
        enum : uint {
            HALF_RANGE	= 0x8000_0000u,
            SENSITIVITY	= 0x0080_0000u,
        }
        // Convert ranges into standard intervals (with or without reverse values)
        if (conf & HALF_RANGE) y = (y + 32767.0) * 1.5259254737998596e-05;	// range  0.0 - 1.0
        else y *= 3.0518509475997192e-05;					// range -1.0 - 1.0
        real a;
        if (conf & SENSITIVITY) a = s.pop();
        /+ When a global sensitivity is available (possibly only use if it's enabled)...
        else a = axis.sensitivity;
        y = sign(y) * pow(abs(y), a);		// sensitivity adjustment by a +/
        myThis.axis[cast(inputID) s.pop()] = y;
        +/
1   Remove ability to scan, then load, mergetag sections. Not so necessary with section creator callback and allows "sliding window" type partial buffering. Also remove dataset and force use of section creator callback?
1   File loading from compressed archives and/or binary archives.