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 50 98 147 148 149 150 151 1040 1929 2818] []

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2013-07-06 13:59 VZ, revision 74406

Make TOOLKIT variable constant in MSW makefiles. This fixes duplicate lines defining rules for generic files for more than one port in the makefiles. Closes #14979.

2013-07-06 02:28 VZ, revision 74405

Fix potential buffer overflow in wxSTC DefaultFont() function. Use safe(r) wxStrlcpy() instead of strcpy() to copy the font name. Closes #15296.

2013-07-06 02:27 VZ, revision 74404

Fix test for Windows in the new wxExecute() unit test. TestOverlappedSyncExecute() doesn't currently pass under Windows and was supposed to not be executed there but was, in console test, as __WXMSW__ is not defined in this case, only __WINDOWS__ is (as there is no GUI toolkit in the console applications). See #10258.

2013-07-05 19:12 JS, revision 74363

Caret blink time and blink on/off are now also reflected in GTK+ widgets

2013-07-05 19:11 JS, revision 74362

Caret blink time and blink on/off are now also reflected in GTK+ widgets

2013-07-05 18:26 JS, revision 74361

Use wxRTC text colour if possible for caret

2013-07-05 18:25 JS, revision 74360

Use wxRTC text colour if possible for caret

2013-07-05 15:33 JS, revision 74359

Don't flash wxRTC caret if blink time is zero, and also take colour from window text colour to avoid invisibility.

2013-07-05 15:32 JS, revision 74358

Don't flash wxRTC caret if blink time is zero, and also take colour from window text colour to avoid invisibility.

2013-07-04 00:18 VZ, revision 74357

Prevent duplicate menu event processing in MDI windows. Record the object propagating the given event upwards in the event object itself and use it in wxMDIParentFrame to determine whether the event being handled is already coming from wxMDIChildFrame and avoid sending it back for processing it there again in this case. This is ugly and makes wx event processing even more complex but this is the only way I could find to ensure that (a) Both the child and the parent frames get the events from the toolbar (even though the toolbar parent is the parent frame and hence normally the child wouldn't get notified about them at all and so the forwarding at wxMDIParentFrame level is required to make this work). (b) The child gets the event only once, whether it comes from a toolbar (and hence indirectly via the parent frame) or from the child menu (and hence directly to the child, at least in wxMSW). This commit fixes the event propagation unit test case, at least under MSW and GTK. See #14314.

2013-07-04 00:18 VZ, revision 74356

Test handling of events from the toolbar in an MDI parent frame. These events must be received by the currently active child.

2013-07-04 00:17 VZ, revision 74355

Ensure that the MDI child is active in event propagation test. Call wxMDIChildFrame::Activate() explicitly as the behaviour was different under MSW (where the activation happened too late for the test) and GTK where the child did become active because of the hacks in place to ensure it.

2013-07-03 13:03 VZ, revision 74354

Make AsyncExecLoopExitEnum enum in the wxExecute() test public. This fixes VC6 build as the nested class couldn't access a private enum inside the enclosing class.

2013-07-03 05:12 PC, revision 74353

fix wxCHECK_MSG() return value

2013-07-03 02:33 VZ, revision 74352

Don't ignore child process output if it exits with -1 exit code. While this code is used by us if the program couldn't be launched at all, it doesn't mean that it didn't run as -1 could also be returned by the child process to indicate an error after outputting something, so we should still read its output in this case. Closes #15205.

2013-07-03 02:32 VZ, revision 74351

Run wxExecute() unit test in the GUI test suite too. The same code works differently in console and GUI applications, so build this test case as part of both of them. See #10258.

2013-07-03 02:32 VZ, revision 74350

Rewrite wxExecute() implementation under Unix. This commit changes wxExecute() to handle SIGCHLD to be notified about the child process termination instead of detecting when the file descriptor corresponding to the other end of a pipe opened in the parent process was closed in the child as this was not reliable and could (and did) result in not detecting the termination of the child processes that closed all their file descriptors before exiting. This commit also removes a lot of platform-specific code duplicating the generic event loop sources support and reuses it for wxExecute() purposes too. Final big change is that wxEndProcessData was merged into wxExecuteData and we don't have two similar but quite different classes any more but just one, which is used both to pass the information from wxExecute() to wxAppTraits methods and to store this information until the child termination. Closes #10258.

2013-07-03 02:31 VZ, revision 74349

Add a helper wxApp::GetValidTraits() method. This method always returns some valid traits, even if we don't have wxTheApp (which is possible in the console applications) or if its GetTraits() was overridden to return NULL (which shouldn't be, but still guard against this).

2013-07-03 02:31 VZ, revision 74348

Treat G_IO_HUP as read, not error, event because EOF is not exceptional. When EOF is reached on a file descriptor, call the handler OnReadWaiting() because this is not really different from getting to the EOF while reading data in the same function. Only call OnExceptionWaiting() for the real errors. See #10258.

2013-07-03 02:31 VZ, revision 74347

Make Unix wxAppConsole signal handling more flexible. Instead of hardcoding the call to WakeUpIdle() in the signal handler itself, just wake up the event loop when we catch a signal. This will still result in WakeUpIdle() being called, before the next event loop iteration, but it will also allow us to do other things on wakeup from signal as it will be done in the upcoming wxExecute() changes to support wxEXEC_NOEVENTS in console applications. See #10258.

2013-07-03 02:30 VZ, revision 74346

Change wxWakeUpPipe to be a wxEventLoopSourceHandler. No real changes but use wxEventLoopSource::AddSourceForFD() instead of wxFDIODispatcher::RegisterFD() for this pipe because this is the preferred way and because it will allow reusing this class for wxExecute() purposes later. See #10258.

2013-07-03 02:30 VZ, revision 74345

Include wx/evtloop.h from wx/evtloopsrc.h. This is necessary to ensure that wxUSE_EVENTLOOP_SOURCE which wraps the entire contents of this header is defined if it's included directly and not after already including wx/evtloop.h. See #10258.

2013-07-03 02:29 VZ, revision 74344

Include <fcntl.h> from a header using fcntl(). No real changes, just make the header self-containing instead of relying on the file including it to include <fcntl.h> itself.

2013-07-03 02:29 VZ, revision 74343

Add wxStreamTempInputBuffer::ReadAll() helper. This just reads everything remaining in the stream in a blocking way and will be used to get the data remaining in the stream buffers after the child process had been already closed (and hence can't write any more to it and there is no risk of deadlock). See #10258.

2013-07-03 02:29 VZ, revision 74342

Use CFSocket instead of CFFileDescriptor in wxCFEventLoopSource. Use OS X socket APIs for monitoring file descriptors. They are more flexible than CFFileDescriptor functions and can be used with any descriptors, not necessarily the socket ones. See #10258.

Select page:

[] [1 50 98 147 148 149 150 151 1040 1929 2818] []

Imprint