topic Re: Curved ramp 12 bug in Libraries & objects

Curved ramp 12 bug

Anonymous — Wed, 22 Apr 2009 07:23:33 GMT

Greetings folks,
I've noticed that mentioned library part has bug under 2D representation options.
There are 3 types of 2D representation:
- COMPLETE,
- HORIZONTAL CUT,
- DASHED OVER HORIZONTAL CUT

Whatever you choose, AC will always display last one (dashed over horizontal cut), with cut line on app. 100cm above ground.
Is there anyone who could help me with this? I would REALLY like to remove this line in some drawings.

Thanks!

Re: Curved ramp 12 bug

David Maudlin — Wed, 22 Apr 2009 12:02:52 GMT

Luka:

For the library part Curved Ramp 02 12, no problem here. Maybe you should post the library part's settings.

David

Re: Curved ramp 12 bug

Anonymous — Thu, 23 Apr 2009 07:08:47 GMT

Ok. Tell me what kind of settings You need. One more thing: on my computer, it's called Curved Ramp 12 (there is no "02 12" mark). I've tried on three PC's, one of them have latest library updates from Graphisoft and still nothing.

Re: Curved ramp 12 bug

Anonymous — Thu, 23 Apr 2009 09:45:35 GMT

Yes, there is a mistake in the Curved Ramp 12 INT.
Line 15 of Parameter Script. Search for this portion of code.

!if GLOB_MODPAR_NAME = "symbolType2d" then
!	if symbolType2d = `Dashed over Horizontal Cut` then parameters symbolType2d_m = 1
!	if symbolType2d = `Horizontal Cut`             then parameters symbolType2d_m = 2
!	if symbolType2d = `Complete`                   then parameters symbolType2d_m = 3
!	parameters symbolType2d_m = symbolType2d_m
!else
!	if symbolType2d_m = 1 then symbolType2d = `Dashed over Horizontal Cut`
!	if symbolType2d_m = 2 then symbolType2d = `Horizontal Cut`
!	if symbolType2d_m = 3 then symbolType2d = `Complete`
!	parameters symbolType2d = symbolType2d
!endif

Replace with this one.

if GLOB_MODPAR_NAME = "symbolType2d" then
	if symbolType2d = `Dashed over Horizontal Cut` then symbolType2d_m = 1
	if symbolType2d = `Horizontal Cut`             then symbolType2d_m = 2
	if symbolType2d = `Complete`                   then symbolType2d_m = 3
endif

if GLOB_MODPAR_NAME = "symbolType2d_m" then
	if symbolType2d_m = 1 then symbolType2d = `Dashed over Horizontal Cut`
	if symbolType2d_m = 2 then symbolType2d = `Horizontal Cut`
	if symbolType2d_m = 3 then symbolType2d = `Complete`
endif

parameters symbolType2d = symbolType2d, symbolType2d_m = symbolType2d_m

Done.

Re: Curved ramp 12 bug

Anonymous — Thu, 23 Apr 2009 10:01:13 GMT

Thanks a lot!
I've changed this and now it works fine.

One more question, if you don't mind:
Is there a way to put change original curved ramp 12 (part of AC library)?
Because, now I have 2 gdl objects (original and new one). Is there a way to overwrite one in library?

Re: Curved ramp 12 bug

rocorona — Thu, 23 Apr 2009 10:04:39 GMT

If you don't want to alter the existing library you can save it with another name.

- Place the original object and select it
- File > Library and Objects > Open Object...
- Click on the Parameter Script button, on the left
- Do the changes and Save as.

Re: Curved ramp 12 bug

Anonymous — Thu, 23 Apr 2009 11:30:35 GMT

My mistake... bad explanation.
I would like to alter existing library part (such is this curved ramp) and to place changed object into standard library. Not to save it in another folder or as external gdl.

Re: Curved ramp 12 bug

rocorona — Thu, 23 Apr 2009 12:11:25 GMT

To modify the original library you need to "extract" it from the container file (*.lcf).
There is a command in the File menu/Library and Objects.
Modify the object then "reconstruct" the container. (File/Library and Objects/Create container).

Re: Curved ramp 12 bug

Anonymous — Thu, 23 Apr 2009 19:53:31 GMT

leziljebovic wrote:
Thanks a lot!
I've changed this and now it works fine.

After beta testers, GS should ask for gamma testers, to check library parts. It could be a full time job. 🙂

Re: Curved ramp 12 bug

Erich — Fri, 24 Apr 2009 02:12:36 GMT

Of course if you alter the part and add it to the GS library, be sure to keep a duplicate around somewhere outside of the library just in case the next update does not fix the ramp. The updates will overwrite the library and any changes you have made.

Re: Curved ramp 12 bug

Karl Ottenstein — Fri, 24 Apr 2009 02:35:37 GMT

I'm just shaking my head over this one. (I shake my head a lot.)

Not only the sloppy bug in the INT script, but on looking at the US script, it has a stupid English-German translation inside rather than doing something smarter as in the INT script.

The INT UI looks nicer in my opinion, see attached screenshot - INT on left and US on right. It does exhibit a pet peeve I've had for many versions - complained during betas with no result: there is lots of space to make the data entry fields larger, but for some reason GS likes to make them so small that in the metric case, a digit is being chopped off here - and in Imperial, we frequently cannot see the foot or inch symbol or, like metric, critical digits. Also, look at the ramp material field in the INT case at left - you cannot read the name of the material at all. No reason at all that this field cannot be quite wide. I see this issue with material UI fields all over the library. It is a quick fix, but GS does not seem to care.)

I really do not understand why this ramp object is not the same for every user, regardless of country...

Karl

Re: Curved ramp 12 bug

Karl Ottenstein — Fri, 24 Apr 2009 02:36:32 GMT

...and here is the INT ramp profile tab UI, vs the ramp profile UI which is at the bottom of the single US panel in the previous screenshot. Here, again, look at the UI's material entry field. Looks like a heck of a lot of blank screen space to the right so that the button could be wide enough to read off the material name without clicking on it! Drives me crazy.

Karl

Re: Curved ramp 12 bug

Anonymous — Fri, 24 Apr 2009 08:20:48 GMT

..Jebiga...

Re: Curved ramp 12 bug

Anonymous — Fri, 24 Apr 2009 19:12:10 GMT

Karl wrote:
...and here is the INT ramp profile tab UI, vs the ramp profile UI which is at the bottom of the single US panel in the previous screenshot. Here, again, look at the UI's material entry field. Looks like a heck of a lot of blank screen space to the right so that the button could be wide enough to read off the material name without clicking on it! Drives me crazy.

Karl

Karl, do you mean delta testers, for UI re-looking? 😉
IMHO, even the INT part looks ugly. One can do better.

Re: Curved ramp 12 bug

Anonymous — Wed, 29 Jul 2009 15:54:22 GMT

well i was also using it and I think another problem shows if the angle of the curve is less than 45 degrees, the 2D representation shows a full circle no matter what. I think it is a bug.

Re: Curved ramp 12 bug

David Maudlin — Thu, 30 Jul 2009 15:53:09 GMT

whatever:

I just played with this object a little bit, and found the problem you described, then set the Ascent Length to a smaller, appropriate length, and the 2D symbol displayed correctly. Also, the 3D model of the part was irrational with the too long Ascent Length. You may need to make sure that the parameters are set to appropriate values for such a short ramp.

David

Re: Curved ramp 12 bug

Anonymous — Sat, 01 Aug 2009 20:56:47 GMT

David wrote:
whatever:

I just played with this object a little bit, and found the problem you described, then set the Ascent Length to a smaller, appropriate length, and the 2D symbol displayed correctly. Also, the 3D model of the part was irrational with the too long Ascent Length. You may need to make sure that the parameters are set to appropriate values for such a short ramp.

David

Thanx david, but actually Ascent was turned off, and actually you can tell its a bug looking at the parameters where it mentions the slop angle ( grayed one ) , the value is negative!

I usually model the ramps using the mesh-SEO-mesh trick, but I was trying to show a new user different options, but it looks like doing it the old manual - non intelligent way is still the only way .

Re: Curved ramp 12 bug

David Maudlin — Sun, 02 Aug 2009 14:40:23 GMT

whatever:

With your settings, does the ramp look OK in 3D?

Could you post a screen shot of the Parameters > Ramp part of the dialog box (including the Height) so we can see your parameters? This may help us or the person at Graphisoft responsible for this object understand the issues.

David