<?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: Custom element settings panels in Archicad C++ API</title>
    <link>https://community.graphisoft.com/t5/Archicad-C-API/Custom-element-settings-panels/m-p/75481#M7784</link>
    <description>&lt;BLOCKQUOTE&gt;Skywalker wrote:&lt;BR /&gt;...there are all header files for VBElemDialog?!&lt;/BLOCKQUOTE&gt;
I hope I understand your question, but the header files for VBElemDialog are in the API Dev Kit at Support/Modules/VBElemDialogs.&lt;BR /&gt;
&lt;BR /&gt;
However, the fundamental problem with this module is that there is &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;no&lt;E&gt;&lt;/E&gt; documentation for it yet. If you run into problems (which is likely without guidlelines) you will be stuck. My advice is to steer clear of undocumented APIs.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Skywalker wrote:&lt;BR /&gt;While working with &lt;B&gt;panel test&lt;/B&gt; example, i've got trouble. Infobox with custom panel works, but:&lt;BR /&gt;
1) defaults for the element are not changed while using eyedropper&lt;/BLOCKQUOTE&gt;
This works OK for me.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Skywalker wrote:&lt;BR /&gt;2) when I add menu in my addon, customm panel is dissapearing when calling this menu&lt;/BLOCKQUOTE&gt;
Yes, I've seen the same. I don't know if this is a bug in the example code or a flaw in the API. As I said above, documentation may be the key to the problem - without it, there is no way to know for certain. This problem completely disables the Wall tool settings dialog and the Materials dialog, and often crashes ArchiCAD too. &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_sad.gif" style="display : inline;" /&gt;&lt;BR /&gt;
I'm wasn't keen to explore this issue further until GS fully supported these modules in the API.</description>
    <pubDate>Tue, 29 Jun 2004 10:17:38 GMT</pubDate>
    <dc:creator>Ralph Wessel</dc:creator>
    <dc:date>2004-06-29T10:17:38Z</dc:date>
    <item>
      <title>Custom element settings panels</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Custom-element-settings-panels/m-p/75480#M7783</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;While working with &lt;STRONG&gt;panel test&lt;/STRONG&gt; example, i've got trouble.&lt;BR /&gt;Infobox with custom panel works, but:&lt;BR /&gt;1) defaults for the element are not changed while using eyedropper&lt;BR /&gt;2) when I add menu in my addon, customm panel is dissapearing when calling this menu&lt;BR /&gt;P.S. Hey, grahisoft wizards, there are all header files for VBElemDialog?!&lt;BR /&gt;&lt;BR /&gt;Are there anya ideas?&lt;/DIV&gt;</description>
      <pubDate>Mon, 07 Aug 2023 10:20:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Custom-element-settings-panels/m-p/75480#M7783</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-08-07T10:20:28Z</dc:date>
    </item>
    <item>
      <title>Re: Custom element settings panels</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Custom-element-settings-panels/m-p/75481#M7784</link>
      <description>&lt;BLOCKQUOTE&gt;Skywalker wrote:&lt;BR /&gt;...there are all header files for VBElemDialog?!&lt;/BLOCKQUOTE&gt;
I hope I understand your question, but the header files for VBElemDialog are in the API Dev Kit at Support/Modules/VBElemDialogs.&lt;BR /&gt;
&lt;BR /&gt;
However, the fundamental problem with this module is that there is &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;no&lt;E&gt;&lt;/E&gt; documentation for it yet. If you run into problems (which is likely without guidlelines) you will be stuck. My advice is to steer clear of undocumented APIs.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Skywalker wrote:&lt;BR /&gt;While working with &lt;B&gt;panel test&lt;/B&gt; example, i've got trouble. Infobox with custom panel works, but:&lt;BR /&gt;
1) defaults for the element are not changed while using eyedropper&lt;/BLOCKQUOTE&gt;
This works OK for me.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Skywalker wrote:&lt;BR /&gt;2) when I add menu in my addon, customm panel is dissapearing when calling this menu&lt;/BLOCKQUOTE&gt;
Yes, I've seen the same. I don't know if this is a bug in the example code or a flaw in the API. As I said above, documentation may be the key to the problem - without it, there is no way to know for certain. This problem completely disables the Wall tool settings dialog and the Materials dialog, and often crashes ArchiCAD too. &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_sad.gif" style="display : inline;" /&gt;&lt;BR /&gt;
I'm wasn't keen to explore this issue further until GS fully supported these modules in the API.</description>
      <pubDate>Tue, 29 Jun 2004 10:17:38 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Custom-element-settings-panels/m-p/75481#M7784</guid>
      <dc:creator>Ralph Wessel</dc:creator>
      <dc:date>2004-06-29T10:17:38Z</dc:date>
    </item>
    <item>
      <title>Re: Custom element settings panels</title>
      <link>https://community.graphisoft.com/t5/Archicad-C-API/Custom-element-settings-panels/m-p/75482#M7785</link>
      <description>Thanks:&lt;BR /&gt;
1) It's my bug  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_rolleyes.gif" style="display : inline;" /&gt; &lt;BR /&gt;
2) I mean that not all header files mentioned in those headers are present (example: "WindowTypes.hpp" )</description>
      <pubDate>Tue, 29 Jun 2004 19:30:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-C-API/Custom-element-settings-panels/m-p/75482#M7785</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2004-06-29T19:30:32Z</dc:date>
    </item>
  </channel>
</rss>

