topic Re: Parking Place 15 library part - 2D display discrepancy in Libraries & objects

Parking Place 15 library part - 2D display discrepancy

Anonymous — Wed, 24 May 2023 09:49:45 GMT

Hi All

I believe there's a glaring omission with the library part "Parking Place 15", or something that is causing a discrepancy in the way that it displays in 3D vs 2D.

Problem is as follows:

I've setup a 3D document to use as a site plan - this is a view created from the 3D window looking directly down at the site

(as per this post: http://archicad-talk.graphisoft.com/viewtopic.php?printertopic=1&t=26467&postdays=0&postorder=asc&start=0&finish_rel=-10000. )

Then I placed the parking lines with numbering turned on. The numbering looks fine in the 2D plan window, but looks different in the 3D window.

This is because there's obviously a 2D and 3D representation of the object, but becuase there are no setting for the 3D text, this means that there is no way to edit the 3D appearance to match the 2D. So now I have to make a work around (i.e turn it off in 3D and re-draw it in the 3D document window as 2D elements)

Or am I missing something here?

Re: Parking Place 15 library part - 2D display discrepancy

Karl Ottenstein — Tue, 28 Feb 2012 17:57:45 GMT

Confirmed the bug that you found in this object. Will report it, but here's a fix:

In the 3D script, as shown in the attached screenshot, replace:

		add 2*sw,sw,0

with

		add tl,tb,0

to position the numbers at the same spot as in 2D (although they will be the same outline font). The existing code always placed the number 2 stripe-widths to the right of a stripe, and one stripe-width above the end of the stripe. The corrected code uses the user specified offset values to move the numbers.

One way to easily make the change in a new object is to place a Parking Place 15, select it, open its code via the menus or ctrl-shift-O (oh) / cmd-shift-O. After making the change, do a Save As into your embedded library.

Finally, select your existing, customized parking place objects (one at a time), open Object Settings, navigate to the Embedded library and (ctrl-alt / cmd-option) into the thumbnail for your modified object. Click OK. The corrected object will replace the placed object with all customization you had done earlier.

If there is another bug, please post here - I'll link this thread to the bug report.

Cheers,
Karl

Re: Parking Place 15 library part - 2D display discrepancy

Anonymous — Wed, 29 Feb 2012 07:35:56 GMT

Excellent! thanks Karl.

Re: Parking Place 15 library part - 2D display discrepancy

Anonymous — Wed, 29 Feb 2012 11:08:18 GMT

Hi
There's one more minor bug, aside from the font issue, is the text orientation. In 2D it can be set to be always readable or to align with the object. In 3D the text can only be aligned with the object which results in text being upside down or at an angle...

Re: Parking Place 15 library part - 2D display discrepancy

Anonymous — Tue, 18 Feb 2014 10:56:03 GMT

Further to this issue - the 2D rotation of text does not seem to work with the AC15 Parking library part - a user has to renumber a large series of parking numbers that were originally drawn as 2d lines and Text - I suggested they use the library part to speed things up, but now the orientation in plan does not seem to work. The options are Readable or Align with object. Presumably the 'Readable' option would show the text vertical regardless of the orientation of the object, but it doesn't seem to work. Or is something else overriding it?

Karl do you know of a GDL fix for this?

Re: Parking Place 15 library part - 2D display discrepancy

vfrontiers — Tue, 18 Feb 2014 14:43:16 GMT

While your at it... PLEASE include an "upgrade" to this object that merely adds a parameter for TOTAL SPACES...

I believe this is a huge omission in that if you want to count the TOTAL spaces on a site with many little snippets of parking, you really can't..

I know, you sequence the numbering, but during design, this fluctuates all over the place.. and editing a snippet at the beginning of the sequence, will cause havoc...

If there is a DERIVED PARAMETER that shows total spaces, this can be used in Interactive Scheduling to keep a current count...

And, while were providing this upgrade, please give us the option to Display
a. Total Spaces (as a dimension (sort of) or as a bullet number
b. Space numbering (as current object)
c. Both

My 2 pennies worth...!

Re: Parking Place 15 library part - 2D display discrepancy

sinceV6 — Tue, 18 Feb 2014 17:22:49 GMT

Hi.
I have been editing and changing that object's options over the years to fit my needs and likings. The version I use helps for rapid layout development. For the text alignment I made a few options: off(aligned with symbol), horizontal (regardless of object's rotation), vertical (90°) and -90° for special cases. The rotation of the 3D text would be weird. Rotation on plan is representative (or for reading purposes), but 3D would be linked to renderings and 3D documents, and I assume the numbering would always be aligned to the parking space. It has a parameter for schedules, but as noted, independent object renumbering is a real pain, so I made the ID usable as numbering starting point. It's faster.

The fixes are not that hard, but require a bit of GDL hassle. I don't know if I can post it, as it is a modified version of the original part of the AC library.

OR

if you have a large parking layout, or a site with many little snippets of parking, as Duane puts it, and you need to keep track and count, you can use this parking object I made, it's really complex, but helps A LOT:

http://archicad-talk.graphisoft.com/viewtopic.php?t=43722

Best regards.

Re: Parking Place 15 library part - 2D display discrepancy

vfrontiers — Tue, 18 Feb 2014 17:42:21 GMT

sinceV6 wrote:
....It has a parameter for schedules, but as noted, independent object renumbering is a real pain, so I made the ID usable as numbering starting point. It's faster.

.....

Best regards.

I had been using PARKING PLACE, which has not NUMBER OF SPACES parameter... So, snooping around, I found PARKING STALL which does... Not sure why there are two objects?

Re: Parking Place 15 library part - 2D display discrepancy

sinceV6 — Tue, 18 Feb 2014 18:18:23 GMT

vfrontiers wrote:
sinceV6 wrote:
....It has a parameter for schedules, but as noted, independent object renumbering is a real pain, so I made the ID usable as numbering starting point. It's faster.

.....

Best regards.
I had been using PARKING PLACE, which has not NUMBER OF SPACES parameter... So, snooping around, I found PARKING STALL which does... Not sure why there are two objects?

I meant the object I edited.

Still, in the object, that fix is relatively simple:

Create a new parameter to store the total (although this will be per object), integer type, variable name: totalCount
In the parameter script, just write:

PARAMETERS totalCount = inner_num

*inner_num is a variable calculated in the beginning of the master script.

You can then use this parameter in schedules.
Best regards.

Re: Parking Place 15 library part - 2D display discrepancy

vfrontiers — Tue, 18 Feb 2014 18:30:13 GMT

Got it V6...

And yes, I have done that every release since 11... That's the ugh part...

Re: Parking Place 15 library part - 2D display discrepancy

sinceV6 — Tue, 18 Feb 2014 19:04:42 GMT

I did it just a couple of times... I then decided to keep it as a separate object, and update/upgrade/fix that. It has evolved well to what I need; it may not have what has been added in later updates, but it doesn't brake or change with new releases; and if I need something, I just add it.

Cheers!

Re: Parking Place 15 library part - 2D display discrepancy

Laszlo Nagy — Wed, 19 Feb 2014 13:36:59 GMT

sinceV6 wrote:
The fixes are not that hard, but require a bit of GDL hassle. I don't know if I can post it, as it is a modified version of the original part of the AC library.

I asked the guys at GS about this.
All ArchiCAD default library objects are saved with the "CC BY-ND v3.0" licence, which is a No-distribution licence, meaning that modified copies of these objects may not be distributed. Atteching them to a post here or putting them on BIMComponents.com would be considered distribution.
In case of macro objects the case is slightly different: you can call them and use them in your objects so it is allowed to distribute objects created with the use of GS-created macro objects.

Re: Parking Place 15 library part - 2D display discrepancy

vfrontiers — Wed, 19 Feb 2014 15:18:13 GMT

laszlonagy wrote:
sinceV6 wrote:
The fixes are not that hard, but require a bit of GDL hassle. I don't know if I can post it, as it is a modified version of the original part of the AC library.
I asked the guys at GS about this.
All ArchiCAD default library objects are saved with the "CC BY-ND v3.0" licence, which is a No-distribution licence, meaning that modified copies of these objects may not be distributed. Atteching them to a post here or putting them on BIMComponents.com would be considered distribution.
In case of macro objects the case is slightly different: you can call them and use them in your objects so it is allowed to distribute objects created with the use of GS-created macro objects.

Did you ask the same guys if they'd mind upgrading the Parking Space object to give us a counter?

Re: Parking Place 15 library part - 2D display discrepancy

Laszlo Nagy — Wed, 19 Feb 2014 15:20:45 GMT

No, that is another guy.
But I will report it to them as a wish.

Re: Parking Place 15 library part - 2D display discrepancy

sinceV6 — Wed, 19 Feb 2014 16:02:01 GMT

Yeah... I remember reading that somewhere a long time ago. While I understand the license, in this case -and others- the "ND" part it's kind of a pity IMHO. Simple fixes as this one help other people carry on with current work, and GS takes some time to fix these simple things.

On the other hand, I can see the chaos if everyone started to modify and post edited versions of the objects in the library. 3 or 4 people working on the same object with different outcomes for different needs... that's 3 or 4 unofficial library parts that started the same, but might end in something entirely different.

In any case, you can see posts around the forum that include the code and changes needed to fix things like these. Is there any real difference? Just my thoughts.

Cheers!