<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Apps]]></title><description><![CDATA[Everything about the development of apps]]></description><link>https://forum.samson-connect.net/category/23</link><generator>RSS for Node</generator><lastBuildDate>Tue, 29 Sep 2026 18:57:13 GMT</lastBuildDate><atom:link href="https://forum.samson-connect.net/category/23.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 06 May 2021 02:35:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Newly Generated Apps Not Appearing]]></title><description><![CDATA[Great! Thanks for the reply.
Please do not hesitate if you have more questions.
]]></description><link>https://forum.samson-connect.net/topic/186/newly-generated-apps-not-appearing</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/186/newly-generated-apps-not-appearing</guid><dc:creator><![CDATA[DmitriyMarin]]></dc:creator><pubDate>Thu, 06 May 2021 02:35:28 GMT</pubDate></item><item><title><![CDATA[SB_ELEMENT_VERSION_HASH Warnings]]></title><description><![CDATA[It does! Thanks a lot.
]]></description><link>https://forum.samson-connect.net/topic/128/sb_element_version_hash-warnings</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/128/sb_element_version_hash-warnings</guid><dc:creator><![CDATA[Elisa]]></dc:creator><pubDate>Thu, 05 Dec 2019 14:07:53 GMT</pubDate></item><item><title><![CDATA[Changelog for developers]]></title><description><![CDATA[That is great!! Looking forward to it!
]]></description><link>https://forum.samson-connect.net/topic/110/changelog-for-developers</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/110/changelog-for-developers</guid><dc:creator><![CDATA[Elisa]]></dc:creator><pubDate>Tue, 25 Jun 2019 07:08:42 GMT</pubDate></item><item><title><![CDATA[Publishing an element (segmentation fault while packing)]]></title><description><![CDATA[@oneangstrom
Yes. Firstly Debug, then Release.
]]></description><link>https://forum.samson-connect.net/topic/108/publishing-an-element-segmentation-fault-while-packing</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/108/publishing-an-element-segmentation-fault-while-packing</guid><dc:creator><![CDATA[Andrii]]></dc:creator><pubDate>Mon, 17 Jun 2019 16:12:51 GMT</pubDate></item><item><title><![CDATA[Publishing an element questions (license + co-development)]]></title><description><![CDATA[Dear all,
Thanks for the answers. it was very helpful, we would probably then choose BSD-3 to make sure we stay compatible with SAMSON.
Best regards,
Elisa
]]></description><link>https://forum.samson-connect.net/topic/100/publishing-an-element-questions-license-co-development</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/100/publishing-an-element-questions-license-co-development</guid><dc:creator><![CDATA[Elisa]]></dc:creator><pubDate>Mon, 18 Feb 2019 16:45:31 GMT</pubDate></item><item><title><![CDATA[Editor names not showing in GUI]]></title><description><![CDATA[Thanks!! Solved!
]]></description><link>https://forum.samson-connect.net/topic/93/editor-names-not-showing-in-gui</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/93/editor-names-not-showing-in-gui</guid><dc:creator><![CDATA[Elisa]]></dc:creator><pubDate>Mon, 11 Feb 2019 14:25:58 GMT</pubDate></item><item><title><![CDATA[Receiving signal when creating new Document]]></title><description><![CDATA[Thank you both, I will use the timer as a workaround for now.
Seems 0.8.0 is going to have a lot of interesting changes :)
]]></description><link>https://forum.samson-connect.net/topic/80/receiving-signal-when-creating-new-document</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/80/receiving-signal-when-creating-new-document</guid><dc:creator><![CDATA[Elisa]]></dc:creator><pubDate>Wed, 02 Jan 2019 11:36:36 GMT</pubDate></item><item><title><![CDATA[No Button to Launch Python Script console]]></title><description><![CDATA[Hi @Max
For the Python Scripting, it is necessary to specify in the OS environment variables the path to the Python executable.
If you are using Windows and Python installed by Anaconda, then you will need to append to the Path environment variable the paths to your installation of Anaconda, like that (depends on where Anaconda is installed): C:\Anaconda3;C:\Anaconda3\Scripts;
On Windows, it might be necessary to restart your system after that. All the rest should be detected automatically during the launch of SAMSON.
Also, to be able to use Python Scripting in SAMSON you will need the next Python packages installed: jupyter, qtconsole, numpy. These packages should be installed automatically if you installed Python using the Anaconda installer. You can verify your installation (https://docs.anaconda.com/anaconda/install/verify-install) and check whether the necessary packages were installed. If they are not installed (which is the case for installation using the Miniconda installer), you can install them via:
conda install jupyter qtconsole numpy
You can check the installation instructions for Python Scripting here: https://documentation.samson-connect.net/scripting-guide/python-script-installation/
Please, let us know if you still experience problems.
]]></description><link>https://forum.samson-connect.net/topic/62/no-button-to-launch-python-script-console</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/62/no-button-to-launch-python-script-console</guid><dc:creator><![CDATA[DmitriyMarin]]></dc:creator><pubDate>Thu, 27 Sep 2018 21:15:57 GMT</pubDate></item><item><title><![CDATA[Custom projection matrix for the SBDDocumentCamera]]></title><description><![CDATA[First of all I have to thank you for the quick response. Funnily, I thought of using const_cast on the matrix pointer beforehand but considered it as too "hacky".
There should be several possibilites how one could introduce this into the API:

Each camera gets a state that determines whether it implements a symmetric or asymmetric projection including two methods that query and set the state. Then, an additonal method (possibly like SetPlanesAsymmetric(float left, float right, float top, float bottom)) could be used to transfer the wanted plane values to SAMSON. This approach would leave the old API intact, if the symmetric projection is the standard state.
Derive a class like SBDAsymmetricDocumentCamera from the currently available SBDDocumentCamera, overriding all methods concerning the projection matrix. This is probably the least favourable alternative, although the old API would still be valid.
The camera gets two additional methods SetValuesSymmetric(float aspect, float fovy, float zNear, float zFar) and SetValuesAsymmetric(float left, float right, float top, float bottom, float zNear, float zFar). Then, the GetProjectionMatrix() and GetProjectionMatrixTranspose() methods would have to be changed to take an additional boolean input parameter determining which kind of matrix is wanted. This would break the old API and I am not sure how this would propagate to the convenience display methods like SAMSON::displayCylinders(...).

Unfortunately I do not know which of these possibilities (and I probably missed some additional ones) would fit best into your way of writing SAMSON.
Best,
Karsten
]]></description><link>https://forum.samson-connect.net/topic/52/custom-projection-matrix-for-the-sbddocumentcamera</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/52/custom-projection-matrix-for-the-sbddocumentcamera</guid><dc:creator><![CDATA[Karsten]]></dc:creator><pubDate>Tue, 22 May 2018 11:18:26 GMT</pubDate></item><item><title><![CDATA[Get Children of Node]]></title><description><![CDATA[yes you are right both ways work fine.
I had a bug I was unaware of in a different position.
thx!
]]></description><link>https://forum.samson-connect.net/topic/50/get-children-of-node</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/50/get-children-of-node</guid><dc:creator><![CDATA[Maximilian]]></dc:creator><pubDate>Sun, 29 Apr 2018 16:50:06 GMT</pubDate></item><item><title><![CDATA[In-code camera duplication]]></title><description><![CDATA[Hi @Karsten ,
For every node, you create you need to invoke create function, and then if you want it to appear in the DataGraph this node needs to be added to a parent node:
auto camcopy = SAMSON::getActiveCamera()-&gt;clone();     // clone the camera
camcopy-&gt;create();                                     // create the node
document-&gt;addChild(camcopy);                           // add the created camera into the active document
/*
... some modifications of the camcopy
*/
SAMSON::getActiveDocument()-&gt;setActiveCamera(camcopy); // set the active camera

]]></description><link>https://forum.samson-connect.net/topic/48/in-code-camera-duplication</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/48/in-code-camera-duplication</guid><dc:creator><![CDATA[DmitriyMarin]]></dc:creator><pubDate>Tue, 24 Apr 2018 14:29:56 GMT</pubDate></item><item><title><![CDATA[DLL dependencies of an Element]]></title><description><![CDATA[From here you can solve your issue related to the dll file, what you need to do is check missing Burutter.dll and copy the setting and save the dll file setting in your PC then you are able to replying of dll files.
]]></description><link>https://forum.samson-connect.net/topic/45/dll-dependencies-of-an-element</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/45/dll-dependencies-of-an-element</guid><dc:creator><![CDATA[khushbu]]></dc:creator><pubDate>Thu, 19 Apr 2018 12:07:38 GMT</pubDate></item><item><title><![CDATA[Conversion from radian to degree does not work]]></title><description><![CDATA[Thanks.
It helps.
SBQuantity::radian radianValue(1.5);
SBQuantity::degree degreeValue = radianValue * SBConstant::RadToDeg;

]]></description><link>https://forum.samson-connect.net/topic/43/conversion-from-radian-to-degree-does-not-work</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/43/conversion-from-radian-to-degree-does-not-work</guid><dc:creator><![CDATA[Khoa]]></dc:creator><pubDate>Sun, 15 Apr 2018 15:16:07 GMT</pubDate></item><item><title><![CDATA[Get list of loaded Elements]]></title><link>https://forum.samson-connect.net/topic/33/get-list-of-loaded-elements</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/33/get-list-of-loaded-elements</guid><pubDate>Mon, 26 Feb 2018 16:59:25 GMT</pubDate></item><item><title><![CDATA[Default settings in GUIs]]></title><description><![CDATA[Not instead, in addition: having, at the installation of the App, a list of pre-saved settings, with still the possibility to save and load your own settings.
-- for example, with the Crystal Creator App, having the 'diamond settings',  the 'SiGe settings', or for ARPS, some classical configurations of Ef and Er : the '10x speed up settings', '5x speed up settings' ... --
]]></description><link>https://forum.samson-connect.net/topic/26/default-settings-in-guis</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/26/default-settings-in-guis</guid><dc:creator><![CDATA[Francois]]></dc:creator><pubDate>Fri, 16 Feb 2018 09:18:13 GMT</pubDate></item><item><title><![CDATA[Temperature color schemes]]></title><description><![CDATA[Sorry, should have mentioned that. Great!
]]></description><link>https://forum.samson-connect.net/topic/21/temperature-color-schemes</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/21/temperature-color-schemes</guid><dc:creator><![CDATA[Stephane]]></dc:creator><pubDate>Thu, 30 Nov 2017 13:25:13 GMT</pubDate></item><item><title><![CDATA[How do you notify an app that the active document is closed ?]]></title><description><![CDATA[Hi Clement,
To listen to the document closed signal I connect my nodes to a custom signal like this:
SB_FOR(SBNode* node, atomIndexer) node-&gt;connectBaseSignalToSlot(this, SB_SLOT(&amp;SENormalModesAnalysisApp::onBaseEvent));

Then, in my onBaseEvent function I catch the  NodeEraseBegin event which corresponds to the signal emitted when the document is closed or the nodes erased.
void SENormalModesAnalysisApp::onBaseEvent(SBBaseEvent* event) {

if (event-&gt;getType() == SBBaseEvent::NodeEraseBegin) {

//disconnet the connected nodes		
SB_FOR(SBNode* node, atomIndexer)
{node-&gt;disconnectBaseSignalFromSlot(this, SB_SLOT(&amp;SENormalModesAnalysisApp::onBaseEvent));
}

//....//

}

Remember to disconnect the connected nodes.
Hope I answered your question,
Yassine
]]></description><link>https://forum.samson-connect.net/topic/16/how-do-you-notify-an-app-that-the-active-document-is-closed</link><guid isPermaLink="true">https://forum.samson-connect.net/topic/16/how-do-you-notify-an-app-that-the-active-document-is-closed</guid><dc:creator><![CDATA[Yassine]]></dc:creator><pubDate>Thu, 09 Nov 2017 11:02:53 GMT</pubDate></item></channel></rss>