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. C / C++ / MFC
  4. Input Needed on Property Pages in External DLLs

Input Needed on Property Pages in External DLLs

Scheduled Pinned Locked Moved C / C++ / MFC
helpc++comsysadminjson
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.
  • M Offline
    M Offline
    Mattias G
    wrote on last edited by
    #1

    I'm working on an application that processes several kinds of file formats. The parsing and processing of the format take place in external plug-in libraries, implemented as DLLs. The parsers and processors are COM objects, implementing a few simple custom interfaces. The problem is this: When importing files into the application we use a wizard with three pages (Select File->Define Settings->Finish). The first page of the wizard finds the correct external library to use for the file provided by the user, and then the library should create the second page with settings that apply to this file format only. This is where I get stuck. One option would be to let the libraries add the page with something like this: HRESULT GetPropertyPage(PROPSHEETPAGE** ppPage); However, the server application is implemented in MFC, and CPropertySheet doesn't play very well with the PROPSHEETPAGE struct. As far as I can see, there's no way to construct a CPropertyPage around a PROPSHEETPAGE. This solution would require that the first and last pages are implemented without MFC (not a major problem, but inconvenient). Another option would be to venture into the world of IPropertyPage and other pre-defined interfaces. I have absolutely no idea on what to choose here, any input would be appreciated. Thanks

    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