Page 1 of 1

wxWidgets 2.5.5 released

Posted: Mon Apr 04, 2005 1:34 pm
by Julian
Hi,

We have released wxWidgets 2.5.5, the last development snapshot before
2.6.0, which will follow in less than two weeks.

Please see the Download page of the wxWidgets web site:

http://www.wxwidgets.org

As usual, please let us know of any problems.

Thanks,

Julian Smart
on behalf of the wxWidgets Team

Posted: Mon Apr 04, 2005 3:58 pm
by Avi
Wonderful. I will be testing some of my code with it, and will let you know if I encounter any big/small bugs. :)

Anything special fixed in this release? Any new features (classes)?

::downloading and will be reading the release notes as well:: :D

Posted: Mon Apr 04, 2005 4:02 pm
by Jorg
I was also curious. I always look at this one:

http://cvs.wxwidgets.org/viewcvs.cgi/wx ... cvs-markup

Regards,
- Jorgen

Posted: Mon Apr 04, 2005 4:05 pm
by ABX
Avi wrote:Anything special fixed in this release? Any new features (classes)?
Each release is tagged. You can read diff between tags easily using forms at web gate of cvs. See: http://cvs.wxwidgets.org/viewcvs.cgi/wx ... f_format=h

ABX

Posted: Mon Apr 04, 2005 4:16 pm
by Avi
I see, thank you. :!:

- Are you guys going to do a "new-features-freeze" now, before 2.6.0?
- Will 2.6.0 be simply 2.5.5 + bug fixes, or are there any major API changes planned (in specific areas)?
- How about standing in the timelines? was this release a bit early/late?
- Will 2.6.0 be included with Julian's wxWidgets book? (any more information regarding the book?)
- When will the wiki pages, Last Release and Next Release, be updated to contain the latest information regarding the releases?
- Looking at the "TODO: Before 2.5.5" in the current Next Release wiki page, I have the following question: did you guys finished fixing + doing all the items there? Are there any items that will go into the 2.6.0 release? After 2.6.0?

Sorry that I bombed you with questions... I just want other people to get this information too! :oops:

Thanks in advance,
Avi

Posted: Mon Apr 04, 2005 4:33 pm
by ABX
Avi wrote:- Are you guys going to do a "new-features-freeze" now, before 2.6.0?
Most probably.
Avi wrote:- Will 2.6.0 be simply 2.5.5 + bug fixes, or are there any major API changes planned (in specific areas)?
IMO, yes as long as fixing bugs will not force API change :-)
Avi wrote:- How about standing in the timelines? was this release a bit early/late?
IIRC 2.5.5 was planned at the end of March and was delayed mostly for wxMac.
Avi wrote:- Will 2.6.0 be included with Julian's wxWidgets book? (any more information regarding the book?)
Search for "book" on this page: http://lists.wxwidgets.org/cgi-bin/ezml ... :aas:60643 :-)
Avi wrote:- When will the wiki pages, Last Release and Next Release, be updated to contain the latest information regarding the releases?
As foreigner I will not say anything about modyfing english texts ;-)

ABX

Posted: Mon Apr 04, 2005 5:06 pm
by VonGodric
Okay I think I found a but -I have winxp+sp2 and mingw(3.4.2) built lib: "make -f makefile.gcc BUILD=release"

this code worked fine in 2.5.4

Code: Select all

    wxFileInputStream SyntaxIS( SyntaxFile );
    wxFileConfig Syntax(SyntaxIS);
"SyntaxFile" is a valid filename containg full path+filename. In 2.5.5 this crashes. Just pops up window's error message (Dr.Watson) and that's it

Von

Posted: Mon Apr 04, 2005 5:27 pm
by ABX
VonGodric wrote:

Code: Select all

    wxFileInputStream SyntaxIS( SyntaxFile );
    wxFileConfig Syntax(SyntaxIS);
Could you please be more specific which of the lines makes a crash for you?
VonGodric wrote:"SyntaxFile" is a valid filename containg full path+filename
So what it is exactly? Could you make this file available somewhere (if that's possible that it's content maked a problem)?

ABX

Posted: Mon Apr 04, 2005 5:41 pm
by VonGodric
Crash happens on the second line. SyntaxFile is a simple INI-format file that contains keywords (it's a part of the IDE i'm working on)

Code: Select all

void MyFrame::LoadkwFile( wxString SyntaxFile ) {
    
    wxFileInputStream SyntaxIS( SyntaxFile );
    wxFileConfig Syntax(SyntaxIS); //<- here.
    
    Syntax.SetPath("/1");
    Keyword[1]            = Syntax.Read("kw", "");

    Syntax.SetPath("/2");
    Keyword[2]            = Syntax.Read("kw", "");

    Syntax.SetPath("/3");
    Keyword[3]            = Syntax.Read("kw", "");

    Syntax.SetPath("/4");
    Keyword[4]            = Syntax.Read("kw", "");

    return;    
}
and that keyword file is smth like this:

Code: Select all

[1]
kw="kw1 kw2 kw3..."
[2]
kw="kw1 kw2 ..."
EDIT: But I don't think there's problem in my code couse with wxWidgets 2.5.4 it works perfectly. And I tryed to rebuild wxWidgets too, didn't help

Posted: Mon Apr 04, 2005 6:24 pm
by ABX
VonGodric wrote:Crash happens on the second line.(...) EDIT: But I don't think there's problem in my code couse with wxWidgets 2.5.4 it works perfectly. And I tryed to rebuild wxWidgets too, didn't help
It still can be something in your code (like opening and writing to the same file simulatnously). Using GCC 3.4.2 (of MinGW 3.2) I did as follow:

1. Created c:\test\test.ini as you quoted (sections [1] and [2] with 'kw')
2. Opened samples/minimal/minimal.cpp
3. Added:

Code: Select all

#include "wx/wfstream.h"
#include "wx/fileconf.h"
#include "wx/filename.h"
at the begining
4. Replaced last function in that file with:

Code: Select all

void MyFrame::OnAbout(wxCommandEvent& WXUNUSED(event))
{
    /* c:\test\test.ini */
    wxFileName filename(wxT("C"),
                        wxT("/test"),
                        wxT("test"),
                        wxT("ini"));
    wxString SyntaxFile(filename.GetFullPath());
    wxFileInputStream SyntaxIS( SyntaxFile ); 
    wxMessageBox(wxT("test"));
    wxFileConfig Syntax(SyntaxIS);
    Syntax.SetPath(wxT("/1"));
    wxString Keyword = Syntax.Read(wxT("kw"), wxT(""));
    wxMessageBox(Keyword);
}
I builded above with MSW and MSWUniv, Unicode and ANSI, Debug and release and it seems to work fine. Please check my code if it crashes for you. If not, try to modify it until it crashes.

Regards, ABX

Posted: Sat Apr 09, 2005 9:12 pm
by VonGodric
Sry :oops: it really must be my code or smth :( couse this worked just fine.