<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/solid/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/solid/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/solid/feature-requests/</id><updated>2001-06-08T11:10:25Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>disabling / enabling Objects</title><link href="https://sourceforge.net/p/solid/feature-requests/1/" rel="alternate"/><published>2001-06-08T11:10:25Z</published><updated>2001-06-08T11:10:25Z</updated><author><name>Olivier Michel</name><uri>https://sourceforge.net/u/omichel/</uri></author><id>https://sourceforge.netae43a50606b385b817306986817555310ae68e45</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It could be very handy to be able to temporary disable&lt;br /&gt;
or enable all the computing and callbacks associated&lt;br /&gt;
with an object.&lt;/p&gt;
&lt;p&gt;This would be much more handy than deleting the object&lt;br /&gt;
and having to recreate it from scratch afterward (with&lt;br /&gt;
a complex shape and numerous callbacks).&lt;/p&gt;
&lt;p&gt;This could be implemented the following way:&lt;/p&gt;
&lt;p&gt;dtDisableObject(object); // disable all the computing&lt;br /&gt;
and associated callbacks for this object&lt;br /&gt;
// do some computations&lt;br /&gt;
dtTest(); // without the object&lt;br /&gt;
dtEnableObject(object); // restore the computing and&lt;br /&gt;
associated callbacks for this object&lt;br /&gt;
dtTest(); // with the object&lt;/p&gt;
&lt;p&gt;Of course, these functions also need to be inserted in&lt;br /&gt;
the API documentation of solid.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>