Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. dumpcpp generated code / COM /qutlook Example stops working since 5.11.x (MinGW)
Forum Updated to NodeBB v4.3 + New Features

dumpcpp generated code / COM /qutlook Example stops working since 5.11.x (MinGW)

Scheduled Pinned Locked Moved Solved General and Desktop
3 Posts 2 Posters 540 Views 2 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.
  • _ Offline
    _ Offline
    _Rayman_
    wrote on last edited by _Rayman_
    #1

    Since upgrading from QT 5.10.x to 5.11.x (MinGW 5.3.0, Windows 10) my COM based application stopped working.

    I figured out that the same effect occours on the QT qutlook example.

    1.) The dumpcpp generated code in file MSOULT.h won't compile: error: use of enum 'MsoFeatureInstall' without previous declaration

    I could fix it, as described in this thread: https://www.qtcentre.org/threads/8811 and given this old thread this seems to be a long running issue.

    2.) During runtime, the qutlook example stops with SIGSEV in file msoutl.h, line 61186 = QVariant qax_result = property("Items");

    inline Outlook::_Items* MAPIFolder::Items() const
    {
        Outlook::_Items* qax_pointer = 0;
        qRegisterMetaType<Outlook::_Items*>("_Items*", &qax_pointer);
        qRegisterMetaType<Outlook::_Items>("_Items", qax_pointer);
        QVariant qax_result = property("Items");
        if (!qax_result.constData()) return 0;
        Q_ASSERT(qax_result.isValid());
        return *(Outlook::_Items**)qax_result.constData();
    }
    

    Accessing a COM object's property returning a QVariant is exactly the same position where SIGSEV occurs in my own project. Going back to QT 5.10.x or earlier versions everything is fine here. So something must have changed in QT 5.11.x that causes this ..?

    1 Reply Last reply
    0
    • _ Offline
      _ Offline
      _Rayman_
      wrote on last edited by
      #2

      Just a follow up:

      Using Qt 5.12.0 beta with MinGW 7.3 the qutlook example as well as my own code works again!

      Pablo J. RoginaP 1 Reply Last reply
      0
      • _ _Rayman_

        Just a follow up:

        Using Qt 5.12.0 beta with MinGW 7.3 the qutlook example as well as my own code works again!

        Pablo J. RoginaP Offline
        Pablo J. RoginaP Offline
        Pablo J. Rogina
        wrote on last edited by
        #3

        @_Rayman_ great that you have a workaround/solution. Please don't forget to mark your post as solved!! Thanks.

        Upvote the answer(s) that helped you solve the issue
        Use "Topic Tools" button to mark your post as Solved
        Add screenshots via postimage.org
        Don't ask support requests via chat/PM. Please use the forum so others can benefit from the solution in the future

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved