View name or ID request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-17 06:59 AM
In theory, this is fairly easy, however to do this I need to find a way to reference a saved view name or id. Looking through the GDL manual it does not appear that to be a request that can be used for this but I am hoping I am wrong. Does anyone know of a method? Can this be done?
Thanks
AC 19 6006 & AC 20
Mac OS 10.11.5
15" Retina MacBook Pro 2.6
27" iMac Retina 5K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-19 09:38 AM
There's no direct support for creating view dependent displacement - but I think I have a workaround in v13. You define a view class parameter in your library global object. This can be anything but I advise you to pair it with positive integer numbers starting from 1. This way you can request this value in your stamp objects and use it as an index in a coordinate array.
Something like this is on my mind:
dummy = LIBRARYGLOBAL(yourobject, yourIntParamName, iViewClass) ... hotspot2 0, 0, ..., xOffsets[iViewClass], ... hotspot2 -1, 0, ..., xOffsets[iViewClass], ... hotspot2 xOffsets[iViewClass], yOffsets[iViewClass], ..., xOffsets[iViewClass], ... hotspot2 0, 0, ..., yOffsets[iViewClass], ... hotspot2 0, -1, ..., yOffsets[iViewClass], ... hotspot2 xOffsets[iViewClass], yOffsets[iViewClass], ..., yOffsets[iViewClass], ...There is one important thing though. You have to communicate the difference between the two kind of dragging of zone stamps to your users. The 'built-in' drag moves the stamp in all views and the 'editable-hotspot-based' drag moves the stamp in the active view category only. It's easy to mess up but can be used with some extra care.
Regards,
Zsolt
ArchiCAD Development - GDL Team
AC13, AC14 and upwards...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-19 09:55 AM
That is pretty much the same idea I had for 13 but as Erich said they are still on 12!
13's new model view options for library parts will open up so many options for exactly this sort of stuff.
I'm looking forward to getting in and having a serious play with it all!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-20 05:14 AM
That is great to hear, that will work quite well, at least once we are able upgrade. Thanks for the feedback it gives us something to look forward to.
Until then I will just have to make do with the work around.
AC 19 6006 & AC 20
Mac OS 10.11.5
15" Retina MacBook Pro 2.6
27" iMac Retina 5K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-28 07:53 AM
Instead of moving the zone marker you LABEL the zone. The label can extract any information of the zone. It is placed on a layer, so you can use layer combinations. To avoid double markers you can turn off the zone-marker with the MVOC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-28 10:30 PM
I think this not possible- the zone is some kind of label itself
Neither requesting "ASSOCLP_PARVALUE" works on zones.
Master wrote:
Instead of moving the zone marker you LABEL the zone. The label can extract any information of the zone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-28 10:40 PM
(I was creating a new label, so I got a bit carried away )
REQUEST ("Zone_relations", "", category_name, code, name, number)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-28 10:52 PM
Yes those are the extractable infos and only works inside the zone.
Would be fine if could be placed outside the room.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-28 11:12 PM
But . . . you can place a hotspot-object with only a hotspot or so inside the zone, let that put the zone information in a parameter and then label that hotspot-object. That label requests that particular parameter of the hotspot-object.
A bit far-fetched but it might work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-10-29 03:21 AM
That's my work around anyway!
- « Previous
-
- 1
- 2
- Next »
- « Previous
-
- 1
- 2
- Next »