<?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: Extending REQUEST Floor_plan_option in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174222#M19573</link>
    <description>&lt;BLOCKQUOTE&gt;derekjackson wrote:&lt;BR /&gt;Hi,&lt;BR /&gt;
   I've been tasked with creating an object that responds to different styles of plan. For example, in a simple GA plan, the object just needs to be represented by a simple outline, but in a presentation quality plan, it needs to use full colour, extra detail, etc.&lt;/BLOCKQUOTE&gt;

The easiest thing to do in this case is to link your object behavior to scale changes using the global variable "GLOB_SCALE".  You can this way link different  scales to different detailing levels. For example 1:200 and up simple outline, 1:100 symbolic representation, 1:50 and under detailed and colour</description>
    <pubDate>Sat, 17 Jul 2010 12:10:54 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2010-07-17T12:10:54Z</dc:date>
    <item>
      <title>Extending REQUEST Floor_plan_option</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174220#M19571</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Hi,&lt;BR /&gt;
   I've been tasked with creating an object that responds to different styles of plan. For example, in a simple GA plan, the object just needs to be represented by a simple outline, but in a presentation quality plan, it needs to use full colour, extra detail, etc.&lt;BR /&gt;
&lt;BR /&gt;
My first thought was to create a parameter in the object that allows the user to pick the style, but this won't do the job (for various reasons). What we're after is a way of automating it, based on a preset standard. Our IT guru has suggested relating it to the Model View options - we'll create two preset Model Views, and when the user changes this, all objects change as a result.&lt;BR /&gt;
&lt;BR /&gt;
So... Is there a way of extending the REQUEST Floor_Plan_Option command? It seems to be limited to floor plans and ceiling plans (0 or 1). &lt;BR /&gt;
&lt;BR /&gt;
My code is below - it never seems to draw the line: &lt;PRE&gt;n = REQUEST("Floor_Plan_Option", "", modelview)

IF (modelview = 0) THEN
	RECT2 0,0, 1,1
ENDIF

IF (modelview = 1) THEN
	CIRCLE2 0,0, 1
ENDIF

IF (modelview = 2) THEN
	LINE2 0,0, 1,1
ENDIF&lt;/PRE&gt;

&lt;BR /&gt;
If not, is there any other Request or global variable that I haven't come across that would do the job perhaps?&lt;BR /&gt;
&lt;BR /&gt;
Any ideas welcome... &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_smile.gif" style="display : inline;" /&gt;&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 16 Jul 2010 15:03:38 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174220#M19571</guid>
      <dc:creator>derekjackson</dc:creator>
      <dc:date>2010-07-16T15:03:38Z</dc:date>
    </item>
    <item>
      <title>Re: Extending REQUEST Floor_plan_option</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174221#M19572</link>
      <description>What version are you using? Because AC13 has the ability to create a so called &lt;A href="http://www.graphisoft.com/ftp/techsupport/documentation/developer_docs/BasicLibraryDoc/13/LibDevGuide/TechnicalStandards.html#library_globals" target="_blank"&gt;LibraryGlobal&lt;/A&gt;</description>
      <pubDate>Fri, 16 Jul 2010 19:39:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174221#M19572</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-07-16T19:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: Extending REQUEST Floor_plan_option</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174222#M19573</link>
      <description>&lt;BLOCKQUOTE&gt;derekjackson wrote:&lt;BR /&gt;Hi,&lt;BR /&gt;
   I've been tasked with creating an object that responds to different styles of plan. For example, in a simple GA plan, the object just needs to be represented by a simple outline, but in a presentation quality plan, it needs to use full colour, extra detail, etc.&lt;/BLOCKQUOTE&gt;

The easiest thing to do in this case is to link your object behavior to scale changes using the global variable "GLOB_SCALE".  You can this way link different  scales to different detailing levels. For example 1:200 and up simple outline, 1:100 symbolic representation, 1:50 and under detailed and colour</description>
      <pubDate>Sat, 17 Jul 2010 12:10:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174222#M19573</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-07-17T12:10:54Z</dc:date>
    </item>
    <item>
      <title>Re: Extending REQUEST Floor_plan_option</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174223#M19574</link>
      <description>We're still in AC12, unfortunately.&lt;BR /&gt;
&lt;BR /&gt;
Linking to scale won't work, as we tend to work on a range on building sizes so all scales are used for normal work. Although I suppose we could predefine similar scales, for example '1:100 Technical', '1:100 Graphic', '1:50 Technical', '1:50 Graphic', etc. Would this work, or does GLOB_SCALE only look at the actual number (ie 100 or 50 in these cases), so it wouldn't be able to tell the difference between Technical or Graphic?&lt;BR /&gt;
&lt;BR /&gt;
Any other ideas? We basically need a way for the architects to be able to change a setting as they output the drawing, that then affects the object - basically, we can't rely on the fact that people can change parameters in the object itself, as they won't bother when in a hurry...</description>
      <pubDate>Mon, 19 Jul 2010 10:29:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174223#M19574</guid>
      <dc:creator>derekjackson</dc:creator>
      <dc:date>2010-07-19T10:29:46Z</dc:date>
    </item>
    <item>
      <title>Re: Extending REQUEST Floor_plan_option</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174224#M19575</link>
      <description>&lt;BLOCKQUOTE&gt;derekjackson wrote:&lt;BR /&gt;Although I suppose we could predefine similar scales, for example '1:100 Technical', '1:100 Graphic', '1:50 Technical', '1:50 Graphic', etc. Would this work, or does GLOB_SCALE only look at the actual number (ie 100 or 50 in these cases), so it wouldn't be able to tell the difference between Technical or Graphic?&lt;/BLOCKQUOTE&gt;

Derek:&lt;BR /&gt;
&lt;BR /&gt;
This won't work, &lt;FONT color="blue"&gt;GLOB_SCALE&lt;/FONT&gt; only returns the scale as a number with no additional variables. The &lt;FONT color="blue"&gt;LibraryGlobal&lt;/FONT&gt; tied to MVOs was created to deal with this issue, in version 12 (and earlier) you only have &lt;FONT color="blue"&gt;Floor_Plan_Option&lt;/FONT&gt; to use.&lt;BR /&gt;
&lt;BR /&gt;
David</description>
      <pubDate>Mon, 19 Jul 2010 10:45:11 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Extending-REQUEST-Floor-plan-option/m-p/174224#M19575</guid>
      <dc:creator>David Maudlin</dc:creator>
      <dc:date>2010-07-19T10:45:11Z</dc:date>
    </item>
  </channel>
</rss>

