X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/ddcc5f5bc6336d1b02923e731d25d95380c6dc30..186005466d585f5553e6acc7d963cd5b62c3ea9f:/docs/motif/todo.txt diff --git a/docs/motif/todo.txt b/docs/motif/todo.txt index ee35bec834..1852d3c4ba 100644 --- a/docs/motif/todo.txt +++ b/docs/motif/todo.txt @@ -1,7 +1,7 @@ wxMotif TODO ------------ -Updated: 12/11/98 +Updated: 11/02/99 -------------------------------o------------------------- @@ -13,84 +13,47 @@ Also, grep for TODO comments in source. High Priority ------------- -- Work out why XFreeFont in font.cpp produces a segv. This is - currently commented out, which presumably causes a memory leak. - -- Colour setting in widgets (almost done). Should scrollbars take - on the background colour? Not right for e.g. wxScrolledWindows, - so maybe have wxSystemSettings value for scrollbar colour, and/or - ability to set scrollbar colour independently. +- Have a central/per app file for colour settings, with a wxWin + app to allow changing settings interactively. -- Optimize wxWindow OnPaint to avoid flicker, collapsing Expose events - as per flicker fix in 1.68. It will be tricky to avoid - interfering with non-wxScrolledWindow widgets except by - explicitly testing for wxScrolledWindow. +- Implementation of default event processing (i.e. passing on an intercepted + event such as OnChar to the system). Currently, such events are processed + anyway, so for example intercepting left-click in a widget doesn't disable + the default behaviour. See TODOs in window.cpp. -- Implementation of OnEraseBackground. How? Call OnEraseBackground - just before OnPaint? Will duplicate Xlib's own erase of the background. - However, this is usually OK, because the default wxWindow::OnEraseBackground - can do nothing (SetBackgroundColour will make the background look OK). - And if a custom OnEraseBackground uses the same colour as the window - background, no flicker will be seen. If it does something else, such as - painting a tiled bitmap, then a slight flicker might be seen unless - X can be persuaded not to repaint the window background by default. - -- wxNotebook bug: why doesn't the notebook sample appear until the - user resizes the window again? But it's OK for MDI. Strange. +- wxRadioBox doesn't show up in the controls sample, though it's + OK on other dialogs (e.g. printing sample). - wxSpinButton -- Tidy dialogs such as the colour and font selectors. - -- Use generic wxTreeCtrl, wxListCtrl: debug and enhance these. - We're close to having these working: mostly scrolling to work out. - -- Find out why modal dialogs give a grab warning. - -- wxSystemSettings. Eventually, should have control panel-like utility - to change colours/fonts but meanwhile should maybe read them - from a file. - -- wxThread (hopefully, similar to wxGTK) - -- wxGrid: scrollbars don't hide; problem with cell selection. - -- MDI: seems to be broken for a more complex application I'm testing. - Frame decorations don't draw properly, and a child window doesn't - process events properly. So probably we should have an alternative - implementation that uses tabs, a la wxGTK. The system menu could - be implemented using a pop-up menu that applies to the currently - active window. - -- Controls in a wxToolBar don't work. Probably due to form layout - problems; the workaround is to use a separate panel for controls. +- wxToolTip - Miscellaneous events. -- Write makefiles for all samples and utilities. +- Use wxImage to load other formats into wxBitmaps, such as PNG, BMP. -- Create some samples for testing. +- Allow wxFrame and other widgets to have mouse event handlers. Low Priority ------------ +- Painting a retained window could be optimized further (see + wxWindow::DoPaint). + +- Visuals: how to select an appropriate one? See Thomas Runge's + visual patch for 1.68 -- should be straightforward to port to 2.0. + +- Work out why XFreeFont in font.cpp produces a segv. This is + currently commented out, which presumably causes a memory leak. + - Better makefile system that can put objects in different dirs. - Use wxGTK config system? It's really complex to debug and - doesn't offer a way of compiling apps outside the wxWin - hierarchy. - Extra wxBitmap formats: PNG, BMP. Could use old wxWin 1.68 wxImage code (derived from XV) for BMP/GIF but it's very bloated. However, when implemented as extra bitmap handlers, the code won't be linked - unless needed. - -- Print/preview framework in print.cpp (see wxGTK). - -- Enhance event handling such that you override e.g. left-click - and unless you call the base OnMouseEvent, the click won't be - sent to the button. Required for Dialog Editor. + unless needed. Update: see if wxImage can handle these formats. -- Get Dialog Editor working under Motif. +- Get Dialog Editor working (better) under Motif. - New wxHelp version: try using the XmHTML widget at http://www.xs4all.nl/~ripley/XmHTML/. @@ -107,11 +70,7 @@ Low Priority - add the driver code to src/motif/helphtml.cpp (a frame, toolbar, history list). -- Optimize screen refresh for non-native widgets, e.g. wxWindow - created with Create(), using technique in flicker patch for 1.68 - (see JACS for latest patch). - -- Copy and paste, drag and drop. Use a standard X drag +- Drag and drop. Use a standard X drag and drop standard - see http://www.cco.caltech.edu/~jafl/xdnd/ or use Motif drag and drop as described here: http://www.motifzone.com/tmd/articles/DnD/dnd.html @@ -130,19 +89,9 @@ Low Priority - Reimplement combobox using Lesstif's widget (avoiding GPL'ed widget currently used). -- Write generic wxDirDialog (directory selector) - -- Use native Motif dialogs for wxMessageBox - - Miscellaneous classes e.g. wxJoystick (identical to GTK's one for Linux) -- Blit scaling - -- Could eventually alter the MDI widgets to be more Windows-like - -- currently it's half-hearted (menus are on children, whereas - they should replace the main parent frame menu). - - Get ODBC classes and sample working. - Work out why wxTextCtrl doesn't work as a stream buffer under