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

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2014-04-10 17:57 PC, revision 76308

fix invisible multi-line wxTextCtrl selection when custom foreground/background color is used with GTK3 closes #16176

2014-04-09 06:41 PC, revision 76307

fix invisible wxTextCtrl selection when custom foreground/background color is used with GTK3 closes #16176

2014-04-08 23:38 VZ, revision 76306

Nepalese translations update from Him Prasad Gautam.

2014-04-08 23:38 VZ, revision 76305

Don't set wxINTERPOLATION_GOOD quality by default in wxGDIPlusContext. This is inconsistent with wxOSX and also doesn't play well with the existence of wxINTERPOLATION_DEFAULT which is different from wxINTERPOLATION_GOOD. See #14134.

2014-04-08 23:31 VZ, revision 76304

Document unexpected default wxGraphicsContext interpolation quality. In 3.0, keep wxINTERPOLATION_GOOD as the default value instead of wxINTERPOLATION_DEFAULT for compatibility, but at least mention this and warn about the changes in 3.1. See #14134.

2014-04-08 23:23 VZ, revision 76303

Fix mouse events after calling WarpPointer() under OS X. See #16169.

2014-04-08 11:14 SC, revision 76302

fixes #16169

2014-04-07 22:34 VZ, revision 76301

Remove "default" clause from enums in wxGDIPlusContext code. This will allow the compiler to give us a warning if more elements are added to the enum later but not added to the switch. Also add error checking to Graphics::SetSmoothingMode() call.

2014-04-07 22:34 VZ, revision 76300

Fix mismatch between GDI+ and wxGraphicsContext interpolation quality. Use wxGDIPlusContext own method instead of using GDI+ method directly when setting the interpolation mode in wxGDIPlusContext initialization code to ensure that m_interpolation field matches the real interpolation mode used.

2014-04-07 22:34 VZ, revision 76299

Initialize wxGraphicsContext::m_interpolation field. This member wwas never initialized, resulting in erratic behaviour of SetInterpolationQuality() which compared its parameter with m_interpolation.

2014-04-07 22:29 VZ, revision 76298

Fix mismatch between GDI+ and wxGraphicsContext interpolation quality. Use wxGDIPlusContext own method instead of using GDI+ method directly when setting the interpolation mode in wxGDIPlusContext initialization code to ensure that m_interpolation field matches the real interpolation mode used.

2014-04-07 22:29 VZ, revision 76297

Initialize wxGraphicsContext::m_interpolation field. This member wwas never initialized, resulting in erratic behaviour of SetInterpolationQuality() which compared its parameter with m_interpolation.

2014-04-07 19:16 PC, revision 76296

update comment for wxBG_STYLE_TRANSPARENT

2014-04-07 19:15 PC, revision 76295

fix transparent window example wxBG_STYLE_TRANSPARENT can only be set before window creation. closes #16161

2014-04-07 18:23 JS, revision 76294

Object position calculation correction

2014-04-06 21:33 PC, revision 76293

avoid warnings about double-to-float conversion

2014-04-06 21:30 PC, revision 76292

avoid warning about shadowed variable

2014-04-06 21:28 PC, revision 76291

cast to proper type to avoid warning

2014-04-06 21:27 PC, revision 76290

remove unused macro definition

2014-04-06 21:27 PC, revision 76289

avoid warning about unreachable code

2014-04-05 19:13 PC, revision 76288

avoid double-to-float conversion warnings in headers

2014-04-05 12:44 VZ, revision 76287

Don't use %i format specifier for size_t values. In 64 bit build, size_t can be 64 bits while %i expects a 32 bit value. Fix this by just avoiding the unnecessary use of size_t, the number of entries in the index is not going to be greater than 2^32. Closes #16163.

2014-04-05 12:44 VZ, revision 76286

Fix warning about %lu being used with an int in 32 bit wxOSX build. NSUInteger is unsigned long in 64 bit builds, but unsigned int in 32 bits, so case it to long explicitly to avoid warnings about using it with %lu format specifier.

2014-04-05 12:44 VZ, revision 76285

Don't use %i format specifier for size_t values. In 64 bit build, size_t can be 64 bits while %i expects a 32 bit value. Fix this by just avoiding the unnecessary use of size_t, the number of entries in the index is not going to be greater than 2^32. Closes #16163.

2014-04-05 12:44 VZ, revision 76284

Fix warning about %lu being used with an int in 32 bit wxOSX build. NSUInteger is unsigned long in 64 bit builds, but unsigned int in 32 bits, so case it to long explicitly to avoid warnings about using it with %lu format specifier.