Author Topic: wxWidgets 2.6.3 vs. 2.6.4  (Read 6084 times)

Offline jmccay

  • Almost regular
  • **
  • Posts: 202
wxWidgets 2.6.3 vs. 2.6.4
« on: April 10, 2007, 12:57:56 am »
I was just at the wxWidgets website.  You can no longer get wxWidgets 2.6.3.  You can get wxWidgets 2.6.4.  The changes lists:

2.6.4
-----

All:

- wxSocket::_Read continues reading from socket after exhausting pushback buffer.
  Previously, only the buffer would be returned, even if more data was requested.
- Fixed wxDb::Open(wxDbConnectInf) when using connection string (Hellwolf Misty)
- Fixed crash in wxDb::Open() in Unicode build (Massimiliano Marretta)
- Fixed bug where wxDateTime::Now() would sometimes return an incorrect value
  the first time it was called.
- Improve wxLaunchDefaultBrowser() behaviour under GNOME/KDE

All (GUI):

- In wxScrolledWindow:DoGetBestSize, no longer adds difference between client and
  total size if we've just used the total size as the best size.
- Fixed problem with zoom setting in print preview.
- Fixed middle click events generation in generic wxTreeCtrl (Olly Betts)
- Backported wxImage::ConvertToGreyscale() from later versions

wxGTK:

- Support underlined fonts in wxTextCtrl.
- wxWindow and wxScrolledWindow now generate line, page and thumb-release scroll events.
- Make Update() work on native controls (Alex Bligh).
- Implemented SetLineSize and GetLineSize for wxSlider.

wxUniv:

- Implemented wxToggleButton (David Bjorkevik).

wxMac:

- Fixed non-detection of process termination on Intel Macs by
  polling for process termination in a separate thread.

wxMGL:

- Fixed NUM_LOCK having no effect.
- Fixed wxFileExists (affecting wxImage::LoadFile).
- Implement wxGetMouseState()

wxMotif:
- Implement wxGetMouseState()

wxX11:
- Implement wxGetMouseState()
- Various bugfixes and improvements for wxMediaCtrl

wxMSW:
- Drag and drop now works inside wxStaticBox.
- Implemented wxComboBox::SetEditable()
- Respect wxBU_EXACTFIT in wxToggleButton
- Fix display of bitmaps in disabled menu items
- Fix indentation of bitmaps in menu items
- Don't replace colours in toolbar bitmaps if they have more than 256 of them

Can we switch to 2.6.4 for standard build?  I am just curious since 2.6.3 is no longer available to download from the website as far as I can tell.
jmccay
OS: WinXP, Win98 SE, & sometimes Linux

a little light reading from the wxWidgets 2.6.2 readme: A detailed 2000-page reference manual is supplied in HTML, PDF and Windows Help form: see the docs hierarchy.

Offline TDragon

  • Lives here!
  • ****
  • Posts: 943
    • TDM-GCC
Re: wxWidgets 2.6.3 vs. 2.6.4
« Reply #1 on: April 10, 2007, 01:24:01 am »
I believe there remain some issues on Code::Blocks' side with incorrect icons; I'm not sure, but I think it was either Biplab or Tim S. (stahta01) that noticed this a little while after 2.6.4 was released. Let me see if I can find that thread...

Addendum:
Here it is. The easiest fix appears to be patching wxWidgets' wx.rc.

I used C::B for several days myself under 2.6.4 and this was the only issue I noticed. At any rate, I imagine killerbot would find it simpler just to stick with 2.6.3 for the nightlies until everything is ready for 2.8. For people who build C::B from source for themselves, a note about this in the Wiki is probably a good idea.
« Last Edit: April 10, 2007, 01:32:07 am by TDragon »
https://jmeubank.github.io/tdm-gcc/ - TDM-GCC compiler suite for Windows (GCC 9.2.0 2020-03-08, 32/64-bit, no extra DLLs)

Offline jmccay

  • Almost regular
  • **
  • Posts: 202
Re: wxWidgets 2.6.3 vs. 2.6.4
« Reply #2 on: April 10, 2007, 01:57:43 am »
Where in the wiki wold be the best place to put it?
jmccay
OS: WinXP, Win98 SE, & sometimes Linux

a little light reading from the wxWidgets 2.6.2 readme: A detailed 2000-page reference manual is supplied in HTML, PDF and Windows Help form: see the docs hierarchy.

Offline TDragon

  • Lives here!
  • ****
  • Posts: 943
    • TDM-GCC
Re: wxWidgets 2.6.3 vs. 2.6.4
« Reply #3 on: April 10, 2007, 02:14:07 am »
Where in the wiki wold be the best place to put it?
My best guess would be in "Installing Code::Blocks from source on Windows", under the wxWidgets subheading. A direct download link for wxWidgets 2.6.3-1 is still available there, so most people that are building C::B from source for the first time will still be able to obtain 2.6.3 easily. A note mentioning this 2.6.4-specific bug and the fix for it is probably all that's needed.
https://jmeubank.github.io/tdm-gcc/ - TDM-GCC compiler suite for Windows (GCC 9.2.0 2020-03-08, 32/64-bit, no extra DLLs)

Offline mike__t

  • Multiple posting newcomer
  • *
  • Posts: 11
Re: wxWidgets 2.6.3 vs. 2.6.4
« Reply #4 on: April 10, 2007, 05:09:49 am »
FYI, you can still download 2.6.3...the source forge download page allows you to select older releases.

Offline Biplab

  • Developer
  • Lives here!
  • *****
  • Posts: 1874
    • Biplab's Blog
Re: wxWidgets 2.6.3 vs. 2.6.4
« Reply #5 on: April 10, 2007, 02:50:19 pm »
- Improve wxLaunchDefaultBrowser() behaviour under GNOME/KDE

The implementation is rather crude. It's a partial backport of a better implementation existing in WX_28 series. It was backported to fix the following Code::Blocks related bug-
Quote
https://developer.berlios.de/bugs/?func=detailbug&bug_id=10628&group_id=5358

BTW, I'm curious about one point. Can you give me the link from where you got this changelog? Because in the official changes.txt file they didn't mentioned about wxLaunchDefaultBrowser(). :?

Regards,

Biplab
Be a part of the solution, not a part of the problem.

Offline jmccay

  • Almost regular
  • **
  • Posts: 202
Re: wxWidgets 2.6.3 vs. 2.6.4
« Reply #6 on: April 16, 2007, 01:15:56 am »
If I remember correctly, I got it from the CHANGES.txt file in the root directory of the wxWidgets 2.6.4 source code (the one with the code for all the platforms).  I just did a brief check of the text, and it mentions it.
jmccay
OS: WinXP, Win98 SE, & sometimes Linux

a little light reading from the wxWidgets 2.6.2 readme: A detailed 2000-page reference manual is supplied in HTML, PDF and Windows Help form: see the docs hierarchy.