Changelogs
Overview
These changelogs reflect the history of all files in the Subversion repository. The changelog has been generated at 2016-05-09 08:38:04
Changelog for wxWidgets (70435 changes):
2009-09-22 15:06 JS, revision 620142009-09-22 15:06 JS, revision 62013Fixed #9996 (incorrect XML output in Ansi build for non-ASCII character)
2009-09-22 14:13 PJC, revision 62012Fixed #9996 (incorrect XML output in Ansi build for non-ASCII character)
2009-09-22 12:58 JS, revision 62011Added automatic linking of ribbon libraries when using MSVC.
2009-09-22 12:03 JS, revision 62010Fixed wxBORDER_THEME breakage
2009-09-22 12:03 JS, revision 62009Don't use deprecated background style
2009-09-22 08:12 JJ, revision 62008Don't use deprecated background style
2009-09-22 02:23 VZ, revision 62006Update OpenVMS makefile
2009-09-22 02:23 VZ, revision 62005Call wxApp::ProcessPendingEvents() from wxX11 event loop. Now that this function is not called from idle time (because it should be called before, see r61441), the event loop must call explicitly so do it from wxGUIEventLoop::Dispatch() in wxX11. A probably better (but more time-consuming) fix would be to make wxX11 use wxEventLoopManual as there doesn't seem to be any reason not to.
2009-09-22 02:23 VZ, revision 62004Override DrawLabel() to avoid crossing out disabled labels in mono theme. DrawButtonLabel() crosses out the buttons to indicate that they are disabled (for lack of any other options in mono renderer) but this looks really bad for the labels, so don't do it. Closes #11220.
- M /wxWidgets/trunk/include/wx/univ/renderer.h
- M /wxWidgets/trunk/src/univ/button.cpp
- M /wxWidgets/trunk/src/univ/ctrlrend.cpp
2009-09-22 02:22 VZ, revision 62003Add a separate wxControlRenderer::DrawButtonLabel() too. wxControlRenderer::DrawLabel() was used by both wxStaticText and wxButton but their labels may need to be drawn differently and wxRenderer does have different DrawLabel() and DrawButtonLabel() to do it. Now also add a separate method for the buttons to wxControlRenderer. See #11220.
2009-09-22 02:22 VZ, revision 62002Implement wxGetActiveWindow() for wxX11. Now that wxGetActiveWindow() is used when showing modal dialogs, it became critical to implement it as otherwise an assert happens every time a dialog is shown and because creating the assert dialog itself results in another (same) assert, this immediately results in a crash. So implement it even if in a very trivial (but hopefully not too incorrect) way.
- M /wxWidgets/trunk/include/wx/univ/window.h
- M /wxWidgets/trunk/include/wx/window.h
- M /wxWidgets/trunk/src/univ/winuniv.cpp
2009-09-22 02:22 VZ, revision 62001Implement wxWindow::DoGetBorderSize() in wxUniv. As some wxUniv classes implement DoGetBestClientSize(), the new code in wxWindow::DoGetBestSize() implementation calls DoGetBorderSize() which asserts because it's not implemented, making it impossible to even start the minimal sample -- fix this.
- M /wxWidgets/trunk/src/common/utilscmn.cpp
- M /wxWidgets/trunk/src/gtk/app.cpp
- M /wxWidgets/trunk/src/gtk/utilsgtk.cpp
- M /wxWidgets/trunk/src/x11/utilsx.cpp
2009-09-22 02:22 VZ, revision 62000Define wxSetDetectableAutoRepeat() for X11-based ports only. This function is not needed in wxGTK2 as GTK+ sets detectable auto-repeat on its own in gdk_display_open() anyhow, so move its implementation to src/x11/utilsx.cpp where it can be used by wxX11 and wxMotif which do need it.
2009-09-21 22:10 VZ, revision 61999Move wxSetDetectableAutoRepeat() to a section compiled in wxCore. This function was mistakenly defined in a section of utilscmn.cpp compiled as part of wxBase, so it wasn't correctly exported from the core library and linking any wxX11 applications failed when using compiler with visibility support.
2009-09-21 16:45 VZ, revision 61998Recognize old wx{CHB,LB}_XXX styles in XRC. Situation with wxBK_XXX vs wxXXB_XXX remains confusing, the comments in the code suggest that the former is preferred but the latter are documented for wxListbook and wxChoicebook (although they don't even exist for wxTreebook). So it seems unwise to not recognize the wxXXB_XXX versions in XRC as people could easily decide to use them instead of wxBK_XXX values -- and this is also consisten with wxNotebookXmlHandler which does recognize both wxBK_XXX and wxNB_XXX already. Change wxListbookXmlHandler and wxChoicebookXmlHandler to also always recognize these styles. Closes #10725.
2009-09-21 16:45 VZ, revision 61997Restore socket initialization times counter. The change of the counter to a simple boolean in r61985 broke the code which called both Initialize() and Shutdown() multiple (but the same number of) times. As this is the documented correct behaviour, restore the counter to cater for it even if we don't really need it any longer.
2009-09-21 16:45 VZ, revision 61996Don't call wxSocketBase::IsInitialized() from worker threads. This function should be used in the main thread only and calling it from wxSockAddress unconditionally resulted in asserts in the unit test.
2009-09-21 15:11 SC, revision 61995Abort on asserts in worker threads. Throwing an exception from worker threads is useless as it is not caught by our wxUnitTestProtector which only protects the main thread, so abort immediately to be sure to provide at least some information about the problem as otherwise nothing may be output at all and the program can end up deadlocked.
2009-09-21 15:10 SC, revision 61994on iPhone default is to cover entire screen
2009-09-21 15:08 SC, revision 61993fixing cast warnings on OSX 10.6
2009-09-21 15:00 VZ, revision 61992fixing include type
2009-09-21 15:00 VZ, revision 61991Account for the margins used by Windows around status bar text. Because Windows uses margins around the text drawn in the status bar, naively setting a field width to the size of the text didn't work (see previous commit for an example). As this seems a natural enough thing to do, account for this margin inside wxStatusBar itself to avoid the user code the trouble of having to call some special function to do it. Notice that this does mean that fields not containing text may be slightly larger than needed, but we consider that this (rarer) case is less important. Also account correctly for the status bar grip size. And while we still hard code its size, do it in a clearly named function instead of using completely mysterious constants here and there. Closes #10696.
2009-09-21 15:00 VZ, revision 61990Add a test of precisely sized status bar fields. Modify the status bar sample to use two fields of just the right size for their contents to confirm that this doesn't work correctly under at least MSW currently (see #10696). Notice that we need two fields because the behaviour/problem is different for the last field and all the other ones.
2009-09-21 15:00 VZ, revision 61989Simplify the status bar sample by removing wxBitmapButton. The sample code was complicated by having USE_STATIC_BITMAP and using wxStaticBitmap or wxBitmapButton depending on it. Neither important for a wxStatusBar sample so just use wxStaticBitmap always and make the code simpler and more readable.
Show status bar panes rectangles in the sample. Display the rectangles returned by wxStatusBar::GetFieldRect() to be able to visually check if they are correct. See #10696.