Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. ATL / WTL / STL
  4. Using Japanese Resources

Using Japanese Resources

Scheduled Pinned Locked Moved ATL / WTL / STL
hardwaretoolsjsonhelpquestion
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    SanShou
    wrote on last edited by
    #1

    I am currently attempting to localize a dialog for Japanese. This dialog inherits off of CAxDialogImpl. The seemingly simple way to localize this was to set the _Module.hinstResource to our language DLL. This seems to find the dialog and seems to load it. It does call _DialogSplitHelper::SplitDialogTemplate which finds all the controls and builds the template. However when it proceeds to call DialogBoxIndirectParam it returns a -1. Called GetLastError and of course it returns "Operation Completed Successfully". Then I tried to modify the dialog to use our internal resources. I did that by overriding DoModal and creating a Modal Pump. This allows me to use our internal dialog creation tools that are designed to load from our Japanese language DLL and if that fails load from the embedded English resources. However the Japanese dialog fails to load, and then StartWindowProc asserts when trying to load the English dialog. This is because _Module.ExtractCreateWndData() returns a NULL. (NOTE: I do AddCreateWndData() in the DoModal call). Also if set the application to load English only, then this dialog still doesn't come up but does not assert in StartWindowProc. Anybody seen this before and solved it? Anybody have any articles on localizing CAxDialogImpl()? All help is helpful, and appreciated... Thanks, Brian If you start a fire for a man, he will be warm for a day. If you start that same man on fire, he will be warm for the rest of his life.

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups