<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: QTGUI in add -ons ? in Archicad C++ API</title>
    <link>https://community.graphisoft.com/t5/Archicad-C-API/QTGUI-in-add-ons/m-p/166324#M6745</link>
    <description>&lt;BLOCKQUOTE&gt;nixonjan wrote:&lt;BR /&gt;Is it possible to use f.e  QDialog  in add- on  development ?&lt;/BLOCKQUOTE&gt;

I don't know of anyone who ever tried that. This question raises the same issues as MFC on Windows.&lt;BR /&gt;
&lt;BR /&gt;
The basic rule is (as Ralph said): Do only modal dialogs.&lt;BR /&gt;
&lt;BR /&gt;
You'll also be restricted in functionality, like using attribute popups.&lt;BR /&gt;
&lt;BR /&gt;
Best,&lt;BR /&gt;
&lt;BR /&gt;
Akos</description>
    <pubDate>Wed, 23 Sep 2009 15:10:13 GMT</pubDate>
    <dc:creator>Akos Somorjai</dc:creator>
    <dc:date>2009-09-23T15:10:13Z</dc:date>
    <item>
      <title>QTGUI in add -ons ?</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/QTGUI-in-add-ons/m-p/166322#M6743</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;Is it possible to use f.e QDialog in add- on development ?&lt;/DIV&gt;</description>
      <pubDate>Thu, 03 Aug 2023 11:41:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/QTGUI-in-add-ons/m-p/166322#M6743</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-08-03T11:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: QTGUI in add -ons ?</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/QTGUI-in-add-ons/m-p/166323#M6744</link>
      <description>&lt;BLOCKQUOTE&gt;nixonjan wrote:&lt;BR /&gt;Is it possible to use f.e  QDialog  in add- on  development ?&lt;/BLOCKQUOTE&gt;
I can't give you a definitive answer, but it is likely to be problematic. It may work if you restrict your use of 3rd party GUI components to the scope of a single call to your add-on, i.e. don't try to create modeless elements that hang around between calls.&lt;BR /&gt;
&lt;BR /&gt;
For the sake of consistency and compatibility, I recommend sticking with the GUI functionality provided by GS.</description>
      <pubDate>Tue, 04 Aug 2009 10:30:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/QTGUI-in-add-ons/m-p/166323#M6744</guid>
      <dc:creator>Ralph Wessel</dc:creator>
      <dc:date>2009-08-04T10:30:21Z</dc:date>
    </item>
    <item>
      <title>Re: QTGUI in add -ons ?</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/QTGUI-in-add-ons/m-p/166324#M6745</link>
      <description>&lt;BLOCKQUOTE&gt;nixonjan wrote:&lt;BR /&gt;Is it possible to use f.e  QDialog  in add- on  development ?&lt;/BLOCKQUOTE&gt;

I don't know of anyone who ever tried that. This question raises the same issues as MFC on Windows.&lt;BR /&gt;
&lt;BR /&gt;
The basic rule is (as Ralph said): Do only modal dialogs.&lt;BR /&gt;
&lt;BR /&gt;
You'll also be restricted in functionality, like using attribute popups.&lt;BR /&gt;
&lt;BR /&gt;
Best,&lt;BR /&gt;
&lt;BR /&gt;
Akos</description>
      <pubDate>Wed, 23 Sep 2009 15:10:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/QTGUI-in-add-ons/m-p/166324#M6745</guid>
      <dc:creator>Akos Somorjai</dc:creator>
      <dc:date>2009-09-23T15:10:13Z</dc:date>
    </item>
  </channel>
</rss>

