Yes there is a fix that Neil came up with - his notes:

Resolved the locale problem by moving it from dApp's __init__ to uiApp's OnInit, because wx3 requires using wx.Locale which can't be initialized until after the app is set up. This should resolve the problem on osx and windows

I'll send a new copy.

Johnf


On 02/03/2015 03:45 AM, Werner wrote:
Hi,

I am doing a bit of work on my app again to try to get it working with Phoenix. With the report designer I see this error:

File "d:\devMine\twcbv5\twcbsrc\controllers\fDaboDesign.py", line 231, in <module>
  main()
File "d:\devMine\twcbv5\twcbsrc\controllers\fDaboDesign.py", line 158, in main
  app.Icon = uiutils.getImageResource('twcb-64.png', True, True)
File "d:\devMine\twcbv5\twcbsrc\libui\uiutils.py", line 212, in getImageResource
  bmpTmp = wx.Image(imgFile, wx.BITMAP_TYPE_ANY)

wx._core.wxAssertionError: C++ assertion "strcmp(setlocale(LC_ALL, NULL), "C") == 0" failed at ..\..\src\common\intl.cpp(1449) in wxLocale::GetInfo(): You probably called setlocale() directly instead of using wxLocale and now there is a mismatch between C/C++ and Windows locale. Things are going to break, please only change locale by creating wxLocale objects to avoid this!

I think this is caused by a relative recent change in wxWidget.

John did you by any chance find a solution for this in your work?

Werner
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]



--- StripMime Report -- processed MIME parts ---
multipart/alternative
 text/plain (text body -- kept)
 text/html
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]

Reply via email to