<?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/ogab/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/ogab/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/ogab/feature-requests/</id><updated>2004-12-09T16:05:02Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Check box whether to include vi-lib and openG-lib VIs</title><link href="https://sourceforge.net/p/ogab/feature-requests/6/" rel="alternate"/><published>2004-12-09T16:05:02Z</published><updated>2004-12-09T16:05:02Z</updated><author><name>Heiko Fettig</name><uri>https://sourceforge.net/u/hfettig/</uri></author><id>https://sourceforge.net260700417b6e60c810b11337450b5353ae64b2fc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice if there was a check box to choose&lt;br /&gt;
whether vi-lib or openG-lib VIs are included in the&lt;br /&gt;
build. They will be needed for .exe files but not&lt;br /&gt;
necessarily for .llb files.&lt;/p&gt;
&lt;p&gt;I guess you could work around it by adding a different&lt;br /&gt;
destination for them but the most convenient way would&lt;br /&gt;
be to ignore them by simply selecting a button.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Made it for LV6.1</title><link href="https://sourceforge.net/p/ogab/feature-requests/5/" rel="alternate"/><published>2003-02-26T15:21:35Z</published><updated>2003-02-26T15:21:35Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netaf4dbad650f4a5ca24d2c4c69dcff3787ae69d95</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Made it for LV6.1&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Pause before invoking the Installer</title><link href="https://sourceforge.net/p/ogab/feature-requests/4/" rel="alternate"/><published>2002-07-30T13:34:46Z</published><updated>2002-07-30T13:34:46Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net12c81395df8d5908b8dc06dbca1cc938b5bc1476</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Sometimes one needs to perfrom some tasks on files &lt;br /&gt;
after the application is built but before they are &lt;br /&gt;
bundled into installation files. Allow to pause the &lt;br /&gt;
installation process or to plug-in a VI that will perform &lt;br /&gt;
these tasks. The plug-in VI path could be put in the &lt;br /&gt;
settings file.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Quick Build</title><link href="https://sourceforge.net/p/ogab/feature-requests/3/" rel="alternate"/><published>2002-07-29T23:24:50Z</published><updated>2002-07-29T23:24:50Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.nete7ada6f033a3932d8f43fcde59642035bfa80364</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A Quick Build feature. From the tool menu, take the &lt;br /&gt;
current VI and build it into an executable. The tool can &lt;br /&gt;
also be launched from the Explorer.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Extract Internal LLB</title><link href="https://sourceforge.net/p/ogab/feature-requests/2/" rel="alternate"/><published>2002-07-27T17:43:23Z</published><updated>2002-07-27T17:43:23Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netbb75c9c67c44931aad356ebef9d4a790419341dd</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This is a feature that would exctract all VIs within an &lt;br /&gt;
EXE and place them within a new or existing LLB or &lt;br /&gt;
directory.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Run executable in LabVIEW development</title><link href="https://sourceforge.net/p/ogab/feature-requests/1/" rel="alternate"/><published>2002-07-24T23:35:21Z</published><updated>2002-07-24T23:35:21Z</updated><author><name>Jim Kring</name><uri>https://sourceforge.net/u/jkring/</uri></author><id>https://sourceforge.net9d143f62a0ad153151f40886c315bf5c388ef348</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This would be an open, probably from the menu, to open &lt;br /&gt;
all top-level VIs within an EXE inside the development &lt;br /&gt;
environment.  This could be done by opening references &lt;br /&gt;
to them and opening the front panels.  This would allow &lt;br /&gt;
dev-env debug tools to be used with VIs that have FP's &lt;br /&gt;
and diagrams.  It would be nice if there was some way &lt;br /&gt;
of adding this as a right-click option, in Windows, for &lt;br /&gt;
LabVIEW .exe's (probably not).&lt;/p&gt;
&lt;p&gt;*Note - It might be a good idea to add a submenu &lt;br /&gt;
beneath &amp;amp;quot;Tools&amp;amp;gt;&amp;amp;gt;OpenG Applicatioin Builder&amp;amp;quot; &lt;br /&gt;
called &amp;amp;quot;Tools&amp;amp;quot;, &amp;amp;quot;Run-Time and Dev. Env. Tools&amp;amp;quot;, or &amp;amp;quot;App &lt;br /&gt;
Debug Tools&amp;amp;quot;&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>