Author Topic: compile wxWidgets with or without unicode  (Read 4225 times)

sethjackson

  • Guest
compile wxWidgets with or without unicode
« on: September 23, 2005, 02:59:25 am »
Ok so I have compiled wxWidgets 2.6.2 no that is not a typo  :). Anyways I compiled the wx dlls as non-unicode. Should I compile them as unicode? I know C::B was just recently converted to unicode. I thought I might mess around with C::B and I just wondered if I needed to have the unicode version of wx.
« Last Edit: September 23, 2005, 03:27:06 am by sethjackson »

Offline grv575

  • Official tester
  • Regular
  • ***
  • Posts: 381
Re: compile wxWidgets with or without unicode
« Reply #1 on: September 23, 2005, 04:00:42 am »
Either should work.  You'll need recent sources for unicode CB, and well if you download bleeding-edge cvs then there might be a couple of places here and there from time to time which need to be unicodified.  But both ansi and unicode are looking solid so your pick really.

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: compile wxWidgets with or without unicode
« Reply #2 on: September 23, 2005, 04:12:01 am »
w00t 2.6.2! :D what's the release notes?

Offline mmkider

  • Almost regular
  • **
  • Posts: 150
Re: compile wxWidgets with or without unicode
« Reply #3 on: September 23, 2005, 05:28:42 am »
2.6.2
-----

All:

- Fixed wxScopeGuard to work with VC++, documented it.
- Fixed proxy handling in wxURL.
- Added wxEVT_MEDIA_LOADED event for wxMediaCtrl.
- Added new methods to wxMediaCtrl (wxURI version of Load, ShowPlayerControls).
- Added wxZipFSHandler::Cleanup() (Stas Sergeev).
- Added wxImage::RotateHue() and RGB <-> HSV conversions (John Anderson).
- Fixed compilation with IBM xlC compiler.
- wxABI_VERSION, see 'Backward Compatibility' topic overview in the manual.
- Added wxLongLong::ToDouble().
- Added wxDateTime::[Make]FromTimezone(), fixed several TZ-related bugs.
- Fixed bug in wxStreamBuffer::Read(wxStreamBuffer *) (Paul Cornett).
- Fixed wxListbook and wxChoicebook internal layout.

All (GUI):

- Added wxStaticText::Wrap()
- wxChoice and wxComboBox::GetSelection() now returns completed selection,
  added a new GetCurrentSelection() function having the old behaviour.
- Added wxXmlResource::Unload().
- Possibility of modeless wxWizard dialog (with presentation in sample).
- Fixed a rare crash due to malformed HTML in wxHTML (Xavier Nodet).
- Ctrl+mouse wheel changes zoom factor in print preview (Zbigniew Zag鏎ski).
- Cross-compile now supported for wxGTK, wxX11 and wxMotif.
- Cygwin compilation of wxX11, wxGTK and wxMotif now supported.
- Now reads "help" parameter for all windows (context help text).
- wxWizard adapts to PDA-sized screens.
- Unicode fixes for IPC and a new IPC sample (Jurgen Doornik).

wxMSW:

- wxMSW now builds with (beta of) MSVC 8 (a.k.a. 2005).
- Separators are now correctly shown in the toolbars under Windows XP.
- Fixed multiline tooltips handling.
- Fixed wxSlider::GetSelEnd() (Atilim Cetin).
- Fixed accelerators of menu items added to already attached submenus.
- Position of wxEVT_MOUSEWHEEL events is now in client, not screen, coordinates.
- Handle absence of wxListCtrl column image better (Zbigniew Zag鏎ski).
- Fixed asynchronous playback of large sound files in wxSound.
- Added wxDynamicLibrary::GetSymbolAorW().
- Fixed default size of wxStaticText controls with border being too small.
- Fixed bugs with wxStatusBar positioning (with or withour sizers) (Jamie Gadd).
- Mouse move events are now generated for all static controls (Jamie Gadd).
- Fixed nested static box display and splitter sash on some themes (Jamie Gadd).
- Made wxJoystick::GetProductName() more useful (John Ratliff).
- Native spline drawing implementation (Wlodzimierz ABX Skiba).

wxGTK:

- ShowFullScreen() shows the window if it was still hidden (rpedroso).
- Implemented wxTopLevelWindow::RequestUserAttention() (Mart Raudsepp).
- Base library is now binary compatible when built with wxGTK and wxMotif.
- wxTextCtrl::XYToPosition, PositionToXY and GetLineLength calls are now
  instantaneous in case of GTK 2.x multi-line controls (Mart Raudsepp).
- Added support for left, centre and right text alignment attributes under
  GTK+2 multi-line text controls (Mart Raudsepp).
- Various wxFont improvements for GTK 2.x builds (Mart Raudsepp).
- Changed order of child deletion in window destructor and
  removed focus handlers to avoid spurious events (David Surovell).
- Fixed domain socket handling.

wxMac:

- First implementation of native HIToolbar support.
- Added text control context menu (ported from wxMSW).
- More CoreGraphics implementation improvements.
- Various text control bug fixes.
- Automatic menu management improved.
- Fixed crash when wxRadioButton is deleted from a group of radio buttons,
  due to dangling cycle pointers.
- Native spline drawing implementation for CoreGraphics (Robert J. Lang).
- Made wxDialog::IsModal meaning the same as other ports (true only when
  showing modally).

wxOS2

- Adjustments for building with Open Watcom C++.

wxUniv:

- Window creation now honours wxVSCROLL.
- Standalone scrollbars generate events of correct type (Jochen Roemmler).

wxMotif:

- Base library is now binary compatible when built with wxGTK and wxMotif.
- wxMotif can now display Japanese text under Japanese locale.
- Fixed button size in common dialogs.
- Made wxFileDialog translatable.
- All top level windows should now have a border unless the wxNO_BORDER
  flag has been specified.
- Improved wxNotebook support for sizers. It requires the wxNotebook to
  be created with a "sensible" initial width.
- Made wxDialog::IsModal meaning the same as other ports (true only when
  showing modally).

wxMGL:

- Fixed crash on exit.
- Fixed drawing problems when windows are resized.

wxX11:

- Various wxFont improvements for unicode builds (Mart Raudsepp).

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: compile wxWidgets with or without unicode
« Reply #4 on: September 23, 2005, 06:10:31 am »
Thanks! :-)

sethjackson

  • Guest
Re: compile wxWidgets with or without unicode
« Reply #5 on: September 23, 2005, 02:04:53 pm »
Either should work.  You'll need recent sources for unicode CB, and well if you download bleeding-edge cvs then there might be a couple of places here and there from time to time which need to be unicodified.  But both ansi and unicode are looking solid so your pick really.


Thanks grv575.  :D