News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Modified & Improved wxWidgets Project Wizard

Started by Biplab, December 23, 2006, 08:11:48 PM

Previous topic - Next topic

rjmyst3

Quote from: Biplab on February 26, 2007, 05:40:26 PM
I'm using Feb 17, 2007 build (3.0.20 beta 3) which produces v1.5 project files. So do I need to update the project files or wxFB will convert it once opened? :)

wxFB will convert them.

You can expect a new build today - hopefully within the hour.  8)
[url="http://wxformbuilder.org"]http://wxformbuilder.org[/url]

Biplab

An important update has been applied to the wizard. I found that the generated apps are not closing properly if they are closed by pressing the Close(x) button. This update fixes that issue.

Changes:

  • EVT_CLOSE has been added in all templates to ensure proper exit.

Committed in revision 3645. :)




Quote from: rjmyst3 on February 26, 2007, 05:46:15 PM
wxFB will convert them.

You can expect a new build today - hopefully within the hour.  8)

That's great.  :)
Be a part of the solution, not a part of the problem.

Biplab

Latest change:

  • OpenWatcom support has been added.

Known Issue:

  • PCH support is not currently available for OpenWatcom. This will be added later.

Tested with OpenWatcom 1.6, wxMSW-2.9.0-CVS-(Debug & Release-DLL-Unicode-Monolithic) wxWidgets Lib. :)
Be a part of the solution, not a part of the problem.

basurapr

Quote from: ascxaxsvcbsxbbqvcxqsbcvxs on February 07, 2007, 12:34:15 PM

1) I installed CB version 3565 on XP
2) I installed wxWidgets 2.8.0 and compiled it with gcc with unicode => OK
3) use of the wizard to generate a basic application with unicode => compile and execute OK with gcc
4) Then without modifying any CB option anywhere, i just add the special letter é to the title of the windows:

original line, generated by the wizard
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Template"));
modified line, for beginning to test the unicode support
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Templateé"));

no other modification except this character => i got the compile message "Illegal byte sequence".

5) If i suppress this character => compile OK
6) I've now tried several times with last build 3577 => same problem, but the error message is now
"converting to execution character set: Invalid argument"


I was having the same problem,

First goto the menu "Project->Build Options" then click your project name. Inside of your global project settings select "Compiler Settings" then click "Other Options" tab, now in that multiline text control write this:

-finput-charset=iso-8859-1

That will fix the problem compiling the standard Latin characters available in the ascci table: á é í ó ú ñ Ñ É and others I does not remember. :)

ascxaxsvcbsxbbqvcxqsbcvxs

#199
Quote from: basurapr on March 11, 2007, 04:12:18 AM
Quote from: ascxaxsvcbsxbbqvcxqsbcvxs on February 07, 2007, 12:34:15 PM

1) I installed CB version 3565 on XP
2) I installed wxWidgets 2.8.0 and compiled it with gcc with unicode => OK
3) use of the wizard to generate a basic application with unicode => compile and execute OK with gcc
4) Then without modifying any CB option anywhere, i just add the special letter é to the title of the windows:

original line, generated by the wizard
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Template"));
modified line, for beginning to test the unicode support
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Templateé"));

no other modification except this character => i got the compile message "Illegal byte sequence".

5) If i suppress this character => compile OK
6) I've now tried several times with last build 3577 => same problem, but the error message is now
"converting to execution character set: Invalid argument"


I was having the same problem,

First goto the menu "Project->Build Options" then click your project name. Inside of your global project settings select "Compiler Settings" then click "Other Options" tab, now in that multiline text control write this:

-finput-charset=iso-8859-1

That will fix the problem compiling the standard Latin characters available in the ascci table: á é í ó ú ñ Ñ É and others I does not remember. :)

Tested it: thank you it works  :lol:
Someone here said before that these characters were supported natively, so i was confused. Nevermind, thank you very much!
I wonder, why such an important option have to be put manually in the "other options" tab? :shock: If you use Unicode, this option is mandatory!

Biplab

#200
Hi All,

Digging out this old post. ;)

A major change has been applied. The change will affect Additional Libraries addition page. Earlier wizard used to have Two pages, but now it will have only one page.

The single page will look like-


Please check the libraries you want to add to your project.

Another interesting addition is, wizard will now add additional dependencies of few advanced libraries (e.g., wxXrc depends upon wxXml).

Now it will be possible to add an additional target to an existing project.

A major portion of the wizard has been modified. So there could be some bugs. I've fixed bugs which I found.

The update will be available in the next nightly.

Please post bugs if you find them.

Regards,

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

oliver1974

#201
..Digging out this old thread....

Quote

-finput-charset=iso-8859-1
(...)
I wonder, why such an important option have to be put manually in the "other options" tab? If you use Unicode, this option is mandatory!

Yes, indeed... Is there no way to make this more obvious? (Or is there a solution already
and I didn't see it?)

It took me hours to find this one out.....


00061205

Quote from: basurapr on March 11, 2007, 04:12:18 AM
Quote from: ascxaxsvcbsxbbqvcxqsbcvxs on February 07, 2007, 12:34:15 PM

1) I installed CB version 3565 on XP
2) I installed wxWidgets 2.8.0 and compiled it with gcc with unicode => OK
3) use of the wizard to generate a basic application with unicode => compile and execute OK with gcc
4) Then without modifying any CB option anywhere, i just add the special letter é to the title of the windows:

original line, generated by the wizard
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Template"));
modified line, for beginning to test the unicode support
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Templateé"));

no other modification except this character => i got the compile message "Illegal byte sequence".

5) If i suppress this character => compile OK
6) I've now tried several times with last build 3577 => same problem, but the error message is now
"converting to execution character set: Invalid argument"


I was having the same problem,

First goto the menu "Project->Build Options" then click your project name. Inside of your global project settings select "Compiler Settings" then click "Other Options" tab, now in that multiline text control write this:

-finput-charset=iso-8859-1

That will fix the problem compiling the standard Latin characters available in the ascci table: á é í ó ú ñ Ñ É and others I does not remember. :)

There is another method to solve this problem which don't need to add "-finput-charset=iso-8859-1" in Other options.
1.Convert your source files which contain the utf-8 characters (eg.á é í ó ú ñ Ñ É 中文) into utf-8 format.
2.Compile the project again in C::B. (Press F9)

tip:Convert method.
1.open editplus.
2.file->open
3.choose source files
4.change the Encoding choose list to UTF-8 (at the bottom of the dialog box) and click open button.
5.file->Save all
now your source files become utf-8 format.

vfdff

#203
Removed non english content !

Only english postings are allowed.

In the future the post might be silently removed and/or your account locked !!!

Sorry !

Jens