<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><category>pcsoft.us.windev</category><copyright>Copyright 2026, PC SOFT</copyright><lastBuildDate>29 May 2015 14:12:00 Z</lastBuildDate><pubDate>29 May 2015 10:28:00 Z</pubDate><description>I have an exe (menu) calling N other components (application modules). If the name of the first window of 2 or more components is the same, the OpenChild / Open called from the menu.exe opens always the same module/component, even if I use the component prefix in the opening.&#13;
&#13;
Example. Menu.exe includes componentA and componentB. The first window of each component is named WIN_Search. So in menu I have 2 buttons:&#13;
button1 - on click do OpenChild(componentA.WIN_search)&#13;
button2 - on click do OpenChild(componentB.WIN_search)&#13;
&#13;
At runtime, If I click on button1 it opens ComponentA but if I close that and next I click on button2 it still opens ComponentA. Viceversa, if I click on button2 it opens ComponentB but if I close that and next I click on button1 it still opens ComponentB.&#13;
It's very weird... Am I missing something?</description><ttl>30</ttl><generator>WEBDEV</generator><language>en_US</language><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components/read.awp</link><title>Absurd behaviours of components</title><managingEditor>moderateur@pcsoft.fr (El moderador)</managingEditor><webMaster>webmaster@pcsoft.fr (El webmaster)</webMaster><item><author>guest</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components-52398/read.awp</comments><pubDate>29 May 2015 14:12:00 Z</pubDate><description>The only solution is giving different names to entry forms of different components...&#13;
&#13;
Then the following specification in Ope…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components-52398/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components-52398/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components/read.awp">Absurd behaviours of components</source><title>Re: Absurd behaviours of components</title></item><item><author>guest</author><category>pcsoft.us.windev</category><comments>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components-52394/read.awp</comments><pubDate>29 May 2015 11:06:00 Z</pubDate><description>I discovered that if I set "isolated / independent context" in compoents' configuration the behaviour is ok. But I can't do it o…</description><guid isPermaLink="true">https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components-52394/read.awp</guid><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components-52394/read.awp</link><source url="https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/52393-absurd-behaviours-components/read.awp">Absurd behaviours of components</source><title>Re: Absurd behaviours of components</title></item></channel></rss>
