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

Select Changelog:

FileZilla 3, FileZilla Server,
Legacy FileZilla 2, Legay FileZilla Server

Select page:

[] [1 2 3 4 238 471 705] []

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2015-01-30 16:53 VS, revision 78422

Handle 5+ letter codes in TranslateFromUnicodeFormat() Unicode TR #35 v26 allows for five-letter (MMMMM) or even six-letter (EEEEEE) forms of some of the fields, but TranslateFromUnicodeFormat() asserts in these situations. Fix it to fall back to short forms for MMMMM and EEEEEE that are used in practice e.g. on OS X if the user has custom formatting settings. Consulting the table of sensible specifiers from http://userguide.icu-project.org/formatparse/datetime, it appears these two were the only omissions in this function.

2015-01-29 13:25 VZ, revision 78421

Reset wxUSE_LIBNOTIFY if libnotify not detected in configure. This avoids WARNING: libnotify not found, wxNotificationMessage will use generic implementation. followed by Which GUI toolkit should wxWidgets use? GTK+ 2 with support for libnotify at the end.

2015-01-27 12:51 VZ, revision 78420

Fix wxEVT_TREE_STATE_IMAGE_CLICK generation in wxMSW wxTreeCtrl. Use GET_{X,Y}_LPARAM() to extract them from the event position, which handle negative coordinates (and coordinates can perfectly well be negative when using multiple displays) correctly, unlike {LO,HI}WORD(). Closes #16812.

2015-01-27 12:49 VZ, revision 78419

Fix wxEVT_TREE_STATE_IMAGE_CLICK generation in wxMSW wxTreeCtrl. Use GET_{X,Y}_LPARAM() to extract them from the event position, which handle negative coordinates (and coordinates can perfectly well be negative when using multiple displays) correctly, unlike {LO,HI}WORD(). Closes #16812.

2015-01-27 12:03 VZ, revision 78418

Improve wxThread::SetPriority() comment and documentation. Don't claim that SetPriority() can only be called before the thread is created, this is just wrong. Do document that it must be done after creating the thread in wxMSW (this is a limitation of this port as POSIX implementation allows calling it at any moment and could be lifted in the future). Closes #16809.

2015-01-26 16:10 VZ, revision 78417

Don't leave too much blank space in wxDatePickerCtrl under XP. In our efforts to account for the longest possible string we made the control too wide by default which didn't look very good, so reduce the amount of space added to it, this still seems to be (just) enough for all the reasonable date formats (tested under Windows XP SP3 with default DPI).

2015-01-24 23:09 VZ, revision 78416

Clarify wxExpectModal<> use and implementation. The only change in this commit is the omission of the primary wxExpectModal<> template as it's not needed and it's enough to just forward declare it, otherwise the changes are to the comments only and try to better explain how this class should be used, i.e. that it's not required, although it may be convenient, to specialize it, and also how it is implemented, notably the need for the CRTP in wxExpectModalBase<>.

2015-01-24 23:09 VZ, revision 78415

Use C++ RTTI in dialog testing code if wxRTTI is not available. This allows to get the best possible description of the dialog: if its class uses wxRTTI macros, its user-readable name will be used, but otherwise we now fall back on possibly unreadable but still informative mangled C++ class name rather than showing just "wxDialog" which is not useful at all.

2015-01-24 23:08 VZ, revision 78414

Cosmetic change to wxTestingModalHook error message. Don't include the word "dialog" in it, by default the description is just the class name and so typically already includes "dialog" in it, e.g. we could have "Expected wxFileDialog dialog" which was redundant.

2015-01-24 23:08 VZ, revision 78413

Provide better description of the expected message boxes. While the example in the previous commit message, with two identical expectations, still requires a custom description to be have unambiguous failure messages, in other cases it's enough to show the expected message box buttons in the error to make it possible to immediately see which expectation failed, so include the information deduced from the expected button into the description.

2015-01-24 23:08 VZ, revision 78412

Allow providing descriptions for dialog tests expectations. This makes test failure errors much more intelligible, e.g. in the following case ... some code ... wxTEST_DIALOG(wxYield, wxExpectModal<wxMessageDialog>(wxID_OK)); ... some more code ... wxTEST_DIALOG(wxYield, wxExpectModal<wxMessageDialog>(wxID_OK)); it was previously impossible to distinguish the first test failure from the second one from just the failure description (it could be done by looking at the line numbers since the recent change however), but with ... wxTEST_DIALOG(wxYield, wxExpectModal<wxMessageDialog>(wxID_OK). Describe("first warning message box")); ... wxTEST_DIALOG(wxYield, wxExpectModal<wxMessageDialog>(wxID_OK). Describe("successful completion message box")); the failure becomes immediately clear.

2015-01-24 23:08 VZ, revision 78411

Allow predefining wxTEST_DIALOG_HOOK_CLASS before wx/testing.h inclusion. Although it already was (and remains) possible to #undef and re-#define wxTEST_DIALOG_HOOK_CLASS after including wx/testing.h, it should also be possible to just define it globally in the testing code before including anything else and not have to bother with the #undef part.

2015-01-24 23:08 VZ, revision 78410

Improve error reporting from wxTEST_DIALOG() macro. Give the location (i.e. file name, line number and the name of the function) at which this macro itself appears instead of the location of ReportFailure() method inside wxTestingModalHook which was quite useless as it was the same for all the tests.

2015-01-24 23:08 VZ, revision 78409

Add wxASSERT_MSG_AT() and wxFAIL_MSG_AT() macros. These macros are useful for functions called from other macros to allow pretending that an assert inside such function actually happens at the point in the sources where the macro itself appears.

2015-01-24 23:08 VZ, revision 78408

Define wxTrap() as a macro for gcc on Intel platforms too. It is more convenient to break into the debugger at the exact location of the assert instead of inside a nested wxTrap() function. This does the same thing for gcc/x86 as was done for MSVC in r73124. See #11184.

2015-01-24 23:08 VZ, revision 78407

Fix typo in a comment for NewCloseButton(). s/common/current/

2015-01-24 16:00 VS, revision 78406

Allow disabling SetProcessDPIAware() call Add Windows-specific wxMSWDisableSettingHighDPIAware() function then can be called before startup (i.e. wxEntry() call) to disable wxWidgets' handling of DPI awareness. This is useful for code embedded in non-wx applications as well as for purely wx application that are not HiDPI-ready (although the latter has the option of forcing dpiAware=false in the manifest). See also https://groups.google.com/d/msg/wx-dev/Z0VpgzCY34U/f1FfPqGDppMJ and #16116.

2015-01-22 18:32 AW, revision 78405

Use constant variables to store cached constants in wxPGGlobalVarsClass.

2015-01-22 17:24 VZ, revision 78404

Remove accidentally left over wxLogMessage() from wxGTK wxWebViewWebKit. This resulted in a message box being shown each time Find() was called and was clearly undesirable. Closes #16801.

2015-01-21 18:28 AW, revision 78403

Use polymorphism to differentiate behaviour of wxEnumProperty and wxEditEnumProperty. Override OnSetValue(), StringToValue(), ValidateValue() methods instead of using RTTI in conditional statements to check if wxEditEnumProperty object is actually handled.

2015-01-21 18:14 AW, revision 78402

Refactor propgrid sample (rounding numbers). Use wxRound function to round floating point numbers.

2015-01-21 18:11 AW, revision 78401

Refactor propgrid sample (attribute constants). Use attribute constants instead of strings when calling wxPGProperty::SetProperty and wxPGProperty::GetProperty in propgrid samples.

2015-01-21 18:06 AW, revision 78400

Refactor property attribute names in wxPGProperty::GetAttribute calls. Use attribute constants instead of strings in wxPGProperty and wxPGDefaultRenderer classes and in NumericValidation() function.

2015-01-21 17:59 AW, revision 78399

Refactor wxPGSpinCtrlEditor. Declare and use attribute constant instead of explicit string "MotionSpin".

2015-01-21 15:31 JS, revision 78398

Remove selection before container is deleted or it could cause a crash later.

2015-01-21 15:31 JS, revision 78397

Remove selection before container is deleted or it could cause a crash later.

2015-01-20 16:26 VS, revision 78396

Use wxNB_MULTILINE in wxPreferencesEditor The size of the dialog in wxPreferencesEditor's generic implementation is determined from notebook pages alone and doesn't account for label size, which may be significantly longer in some languages (German, Danish). If the labels don't fit into the window, some of the tabs are hidden behind scroll buttons that are easy to overlook. Improve usability by using wxNB_MULTILINE, which will use multiple rows of tabs in this situation. This is what e.g. Internet Explorer does in its preferences as well.

2015-01-20 16:26 VS, revision 78395

Use wxNB_MULTILINE in wxPreferencesEditor The size of the dialog in wxPreferencesEditor's generic implementation is determined from notebook pages alone and doesn't account for label size, which may be significantly longer in some languages (German, Danish). If the labels don't fit into the window, some of the tabs are hidden behind scroll buttons that are easy to overlook. Improve usability by using wxNB_MULTILINE, which will use multiple rows of tabs in this situation. This is what e.g. Internet Explorer does in its preferences as well.

2015-01-20 16:01 TIK, revision 78394

Fix memory leak introduced in r78183: wxMenuItemBase::SetAccel does not take ownership of the passed pointer nor keeps it for later use.

2015-01-20 16:00 TIK, revision 78393

Fix memory leak introduced in r78179: wxMenuItemBase::SetAccel does not take ownership of the passed pointer nor keeps it for later use.

2015-01-19 21:19 AW, revision 78392

Function wxPGProperty::HasFlag should return Boolean value.

2015-01-19 20:58 AW, revision 78391

Implement deprecated wxPGProperty::GetValueString function only in wxPG 1.4 compatibility mode. This function was marked as deprecated in 2008.

2015-01-19 18:22 AW, revision 78390

Fix a hack implemented in wxEnumProperty::ValueFromString_ and wxEnumProperty::ValueFromInt_ functions. wxEnumProperty code is refactored in order to fix a hack which purpose was (apparently) to bypass constness of these functions by caching determined indices in wxEnumProperty::ms_nextIndex static member variable for further processing. (Unclear concept of using this static member was referred in http://trac.wxwidgets.org/ticket/12779#comment:9) Now, determined index is returned to the caller and processed there if necessary and hence caching of this index is not necessary.

2015-01-19 13:18 VZ, revision 78389

Use logical operations instead of bit-wise ones for booleans. wxUniv "Windows" theme code wrongly used bitwise operations on boolean values, fix this. Closes #16796.

2015-01-19 04:05 MAR, revision 78388

remove wxMISSING_IMPLEMENTATION because wxQtDCImpl::DoBlit is implemented Thanks @seandepagnier

2015-01-19 04:03 MAR, revision 78387

Fix problem with scrollbar events in wxQT the local variable event shadowed the parameter which caused the incorrect value to be sent Thanks @seandepagnier

2015-01-19 04:02 MAR, revision 78386

Fix crash from possible NULL pointer in wxQT list ctrl Thanks @seandepagnier

2015-01-19 04:01 MAR, revision 78385

Fix problem with clipping region in wxqt. QPainter cannot set the clipping region when it is not active. Thanks @seandepagnier

2015-01-19 03:57 MAR, revision 78384

wxQT: move destroyed debug log into class method (remove global function to handle destroyed signal) This is needed for applications because the global function is not exported, yet it is used by the opengl library. An alternative is to add utils.cpp to the opengl library Thanks @seandepagnier

2015-01-19 03:44 MAR, revision 78383

wxQt: Fix compiler error for ambiguous call (when compiling without unicode support) Thanks @seandepagnier

2015-01-19 03:41 MAR, revision 78382

wxQT: Add guard to wxWindowQt for building without unicode support Thanks @seandepagnier

2015-01-19 03:39 MAR, revision 78381

wxQt: fix performance issue with font comparisons Thanks @seandepagnier

2015-01-19 03:38 MAR, revision 78380

Added wxUSE_XLOCALE ifdef guard to wxTimePickerGenericImp Allow to compile wxQT when configure with --disable-xlocal Thanks @seandepagnier

2015-01-19 03:31 MAR, revision 78379

Fix building for wxQT-android with sockets enabled The bionic library on android does not have gethostbyname_r even though it has gethostbyname_r. The configure script in wxwidgets assumes if it has one it has the other. This change does the right thing for android, but perhaps the script should instead test for both? Thanks @seandepagnier

2015-01-19 03:29 MAR, revision 78378

Fix Select on wxQT DC implementation Need to set the underlying qt painter up with the current pen, brush and font when a new object is selected Thanks @seandepagnier

2015-01-19 03:22 MAR, revision 78377

Specify needed header files more correctly (needed for wxqt-android) Thanks @seandepagnier

2015-01-19 03:18 MAR, revision 78376

Correct wxWindowQt::DoSetSize() for possible NULL member de-reference. Thanks David Register

2015-01-19 02:03 MAR, revision 78375

Remove duplicate declaration in wxRichTextCtrl buffer interface This is needed to compile wxPython Phoenix

2015-01-18 09:06 RD, revision 78374

another test commit, undoing the last one

2015-01-18 08:48 RD, revision 78373

This is just a test commit.

2015-01-16 03:39 VZ, revision 78372

Fix typo in wxSOCKET_NOWAIT_WRITE description in the manual. Don't contradict ourselves. Closes #16779.

2015-01-16 03:39 VZ, revision 78371

Fix checks for WXWIN_COMPATIBILITY_3_0: use #if, not #ifdef. The deprecated methods were always available as WXWIN_COMPATIBILITY_3_0 is always defined, we need to check its value and not its definedness. Closes #16782.

2015-01-13 18:05 JS, revision 78370

Bullet no longer gets the attributes from the first object in the list paragraph, so we can control it via paragraph attributes.

2015-01-13 17:41 AW, revision 78369

Fix using WXWIN_COMPATIBILITY_3_0 in conditional blocks in wxPG code. Check the value of WXWIN_COMPATIBILITY_3_0 instead of checking whether it is defined.

2015-01-12 21:37 AW, revision 78368

Preserve alpha channel flag when rescaling bitmap in wxPGProperty::SetValueImage (when wxUSE_IMAGE == 0). Rescaled bitmap must have the same alpha channel flag as the source bitmap flag in order to be properly displayed.

2015-01-12 21:32 AW, revision 78367

Let system decide about required depth of rescaled bitmap in wxPGProperty::SetValueImage. There is not necessary to fix the color depth - everything is determined internally when converting wxImage to wxBitmap.

2015-01-12 21:29 AW, revision 78366

Sanity check regarding DC in wxPropertyGrid::OnComboItemPaint Ensure that wxDC used by drawing functions in wxPropertyGrid::OnComboItemPaint is valid.

2015-01-12 21:23 AW, revision 78365

Don't attempt to draw element-specific bitmap when drawing wxPGChoices element inside the control field of wxEnumProperty with wxPGComboBox. The only bitmap which can be drawn in the control field is a "general" value bitmap (assigned to the property). Closes #16781

2015-01-11 23:49 VZ, revision 78364

Fix selection of items inserted in virtual generic wxDataViewCtrl. Call wxSelectionStore::OnItemsInserted() explicitly instead of just using our UpdateCount() to update the count of items managed by the selection. This needs to be done to ensure that the newly added items have the correction selection, i.e. are always unselected, as previously this wasn't the case: if wxSelectionStore was in the "selected by default" state as it happened e.g. after selecting all the items in the control, the new items also ended up being selected.

2015-01-11 23:49 VZ, revision 78363

Fix selection in virtual generic wxDataViewCtrl after deleting items. The number of items managed by selection was first decremented by our own UpdateCount() and then, again, by an explicit call to wxSelectionStore:: OnItemDelete(), which resulted in the selection ending up in an invalid state. Fix this by not calling UpdateCount(), and hence wxSelectionStore:: SetItemCount(), at all, just OnItemDelete() is enough.

2015-01-10 10:13 SC, revision 78362

removing overridden ProcessIdle, reverting that part of r75289

2015-01-09 04:30 VZ, revision 78361

Send deactivation events to MDI children frame in wxMSW too. For some reason, the code only forwarded activation events to the current MDI child, but not the deactivation ones. And even though this was literally always the case (the check for the event being the activation one is there since r9), it is clearly wrong as the focus restoring code in wxTopLevelWindow in wxMSW doesn't work if the focus hadn't been previously saved. This fix hopefully completes the changes started by r78340 and r78341 and ensures that the focus is always properly restored to the last focused window inside an MDI child.

2015-01-09 04:30 VZ, revision 78360

No changes, just fix a slightly misleading comment in wxMSW focus code. DefWindowProc() never preserves the focused window actually, whether we use WM_NEXTDLGCTL (which is only handled by DefDlgProc() anyhow) or not.

2015-01-09 04:30 VZ, revision 78359

Make specifying minimal size for "unknown" XRC controls work. At least since the changes of r44456 (see #8378), minimal size specified in the XRC for unknown controls didn't have any effect as it was set on wxUnknownControlContainer itself and was overridden by the subsequent call to SetSizerAndFit() which reset the minimal size to the best size of the control contained in it, meaning that it was impossible to make this contained control bigger by specifying min size greater than its best size in the XRC. Fix this by honouring both the min size of the container and of the control contained in it (and do the same thing for the max size for good measure). To avoid not totally obvious interaction of overriding GetMinSize() and DoGetBestClientSize() with sizer code, also position the child control manually instead of using a sizer for it, it's an overkill for such a simple case anyhow.

2015-01-09 04:30 VZ, revision 78358

Make generic wxDataViewCtrl initially usable from keyboard. This control doesn't react to the keyboard at all if it doesn't have a current row and as it doesn't have it initially, it means that there is no way to do anything with the control without clicking it with the mouse first. Fix this by giving it a current row, if possible, whenever it gains focus.

2015-01-09 04:29 VZ, revision 78357

Always invalidate wxStaticText best size after changing its label. wxST_NO_AUTORESIZE style only affects whether the control is actually resized when its text changes, but its best size should always change, so that if the window containing it is explicitly relaid out the size does change. Moreover, in wxMSW and wxOSX the best size was never invalidated at all when the label was ellipsized, so it was never updated for them, preventing, for example, comparing the best size with the current one to check if the text is effectively ellipsized (and so needs to be shown in a tooltip, for example). Fix this by calling InvalidateBestSize() unconditionally, this should make these ports behave in the same was as wxGTK already did.

2015-01-08 15:11 VZ, revision 78356

only flush a client dc if it was not inheriting the native CGContextRef from an outside paint context, fixes #16334

2015-01-06 21:20 VZ, revision 78355

Fix wxBitmap conversion to wxImage in 64-bit wxOSX builds. Don't assume that sizeof(long) == 4, this is just wrong. Closes #16770.

2015-01-06 21:08 VZ, revision 78354

Fix wxBitmap conversion to wxImage in 64-bit wxOSX builds. Don't assume that sizeof(long) == 4, this is just wrong. Closes #16770.

2015-01-06 08:12 MAR, revision 78353

Added new ctor for wxBitmap using wxCursor for wxQT (similar to wxGTK) This is the implementation that should had been included in r78348

2015-01-05 13:49 TIK, revision 78350

On wxMac, modal event loops avoid deleting pending objects. Hide the text control after editing a label in the generic tree control so it does not remain visible e.g. if the tree control is used in a dialog.

2015-01-05 13:48 TIK, revision 78349

On wxMac, modal event loops avoid deleting pending events. Hide the text control after editing a label in the generic tree control so it does not remain visible e.g. if the tree control is used in a dialog.

2015-01-04 04:51 MAR, revision 78348

Added new ctor for wxBitmap using wxCursor for wxQT (similar to wxGTK)

2015-01-04 03:49 MAR, revision 78347

Added missing ctor for wxBitmap using wxIcon for wxQT (taken from wxOSX)

2015-01-03 21:45 VZ, revision 78346

Fix wxFileDialog::GetFilterIndex() when opening files in wxOSX. Update m_filterIndex in the "opening" case, just as we already did in the "saving" one (see #13158 and r67550). Closes #16764.

2015-01-03 21:45 VZ, revision 78345

Fix wxFileDialog::GetFilterIndex() when opening files in wxOSX. Update m_filterIndex in the "opening" case, just as we already did in the "saving" one (see #13158 and r67550). Closes #16764.

2015-01-03 16:20 AW, revision 78344

Optimize wxPGChoices::Add methods. Remove unnecessary variables, limit the scope of variables and implement some sanity checks.

2015-01-03 16:10 AW, revision 78343

Optimize wxPGChoices::Set method. There is no need to check if referenced array with values is valid since "reference cannot be bound to dereferenced null pointer in well-defined C++ code". Moreover, conditional call of Add() methods(one with explicit parameter and one with default one) is not necessary.

2015-01-03 14:33 VZ, revision 78342

Fix the size of the "new" bitmap in the toolbar sample. It was broken by the changes of r78238 and was too small for the height in the header, resulting in an immediate crash on toolbar sample startup.

2015-01-03 02:07 VZ, revision 78341

Don't change MDI children order after showing a file dialog in wxMSW. Don't use the generic focus saving/restoring code for wxMDIParentFrame in wxMSW as it already saves and restores the active MDI child on its own and we should let it do it, as our code could change the active child when restoring focus if it hadn't been saved correctly previously. The fact that it is isn't saved is another bug, but even if it is fixed, we should let MSW MDI implementation handle activation as we can't do it any better -- but can do worse, as the bug described in #16635 shows. Closes #16635.

2015-01-03 02:07 VZ, revision 78340

Fix saving focus for MDI child frames in wxMSW. Use wxWindow::IsDescendant() instead of wxGetTopLevelParent() to determine whether the focused window is inside the TLW, as the former works correctly for any window, including wxMDIChildFrames, while the latter would return wxMDIParentFrame for them (as MDI children are not considered to be TLWs) and so saving the focus would always fail and the focus was always restored to the first child of wxMDIChildFrame after switching from it to another child frame and back, as could be seen by applying the simple patch: ---------------------------------- >8 -------------------------------------- diff --git a/samples/docview/view.cpp b/samples/docview/view.cpp index 9f20032..8386522 100644 --- a/samples/docview/view.cpp +++ b/samples/docview/view.cpp @@ -160,8 +160,9 @@ bool TextEditView::OnCreate(wxDocument *doc, long flags) wxFrame* frame = wxGetApp().CreateChildFrame(this, false); wxASSERT(frame == GetFrame()); m_text = new wxTextCtrl(frame, wxID_ANY, "", - wxDefaultPosition, wxDefaultSize, + wxPoint(5, 5), wxDefaultSize, wxTE_MULTILINE); + new wxButton(frame, wxID_ANY, "Button", wxPoint(5, 100)); frame->Show(); return true; ---------------------------------- >8 -------------------------------------- Notice that the bug usually stayed hidden because it didn't happen if wxMDIChildFrame contained a wxPanel (which also stores the last focus) inside it or if the focus switched away from the entire application instead of just going to another child and back, as in this case the last focus was stored in wxMDIParentFrame, for which the old code did work.

2015-01-03 02:07 VZ, revision 78339

Add include/wx/richtext/richtexttabspage.h to the MSBuild project. This seems like an occidental omission.

2015-01-03 02:07 VZ, revision 78338

Remove files not being compiled from richtext MSBuild project. Several sources in this project are actually not compiled at all, but are included from other files, so they don't appear in the master sources list. Update the project accordingly, for consistency with the earlier versions of MSVC. If these files should appear in it, they need to be added to RICHTEXT_HDR variable.

2015-01-03 02:07 VZ, revision 78337

Add appprogress.{h,cpp} to the files list. The wxMSW header was absent from both the bakefile and master file list, and the latter also lacked the other wxAppProgressIndicator-related files. Also regenerate the project file to contain the MSW header.

2015-01-03 02:07 VZ, revision 78336

No changes, just sort files alphabetically in the bakefiles files list. Keep MSW_SRC files list sorted, appprogress.cpp was added in a wrong place.

2015-01-03 00:49 VZ, revision 78334

German translations update from Wolfgang Stöggl .

2015-01-02 17:15 AW, revision 78333

Delete wxDC object when exiting from wxPropertyGrid::OnPaint

2015-01-02 15:26 VZ, revision 78332

Improve widgets sample UI consistency. Ensure that the various attributes (colours, font, border, ...) are preserved when a widget is recreated or the current page is changed. This is more convenient and also avoids discrepancies between the state of the menu items and the actual state of the widget. Closes #16576.

2015-01-01 00:36 RD, revision 78331

a commit to test Trac/SVN integration. Closes #16754

2014-12-31 23:25 RD, revision 78330

just another test commit

2014-12-31 23:20 RD, revision 78329

just a test commit

2014-12-28 21:06 AW, revision 78328

Pass outside wxPG a modified clone of wxEVT_TEXT event instead of hacking current event object. Using a clone of event (with PG id) instead of replacing id in the currently processed event coming from wxPGTextCtrlEditor seems to be less intrusive and safer action.

2014-12-27 15:24 VZ, revision 78327

Fix reading of not NUL-terminated strings using wxRegKey. Even though this is typically the case, some strings in Windows registry are not NUL-terminated, deal with them correctly by using the explicit length. Closes #16719.

2014-12-27 15:24 VZ, revision 78326

Revert "Add support for reading multi string values to wxRegKey." Reverts r78136 (see #15727) because the multi-string values in Windows registry are actually not "name=value" pairs at all but just NUL-separated strings and the API provided for reading them was inappropriate. Also see #16719.

2014-12-27 15:24 VZ, revision 78325

Fix flickering when resizing a frame with status bar in wxMSW. The flicker was only visible under Windows XP or when using a class theme and was due to mis-positioning the status bar initially in PositionStatusBar(). Fix this by adjusting its position by the toolbar offset before calling its SetSize(). Closes #16705.

2014-12-27 15:24 VZ, revision 78324

Make disabling submenus work in wxMSW. As submenu items don't have a valid ID, we need to address them by their position when calling EnableMenuItem() -- and for simplicity do it for all the items. Closes #16747.

2014-12-27 15:17 VZ, revision 78323

Make disabling submenus work in wxMSW. As submenu items don't have a valid ID, we need to address them by their position when calling EnableMenuItem() -- and for simplicity do it for all the items. Closes #16747.

2014-12-27 15:17 VZ, revision 78322

Fix handling of fast clicks in wxRibbonBar under MSW. Second click can result in a double click event instead of the usual simple click if it happens quickly enough after the first one, so handle double clicks in the same way as simple clicks instead of ignoring them. Closes #16551.

2014-12-27 12:30 AW, revision 78321

Do not actually reconnect PG event handlers when attempting to reconnect them to the same window. When in wxPropertyGridManager::ReconnectEventHandlers() new window ID is the same as old window ID then there is no need to do anything with handlers. An assertion warning is displayed in this case to notify about this unusual (and maybe unintended) situation.

2014-12-25 02:32 VZ, revision 78320

Fix removing tools from wxToolBar in wxOSX. Release the tool instead of retaining it (typo?) and also remove it from the toolbar view. See #16663.

Select page:

[] [1 2 3 4 238 471 705] []

Imprint