Jump to content

Richard T

Member
  • Posts

    119
  • Joined

  • Last visited

Posts posted by Richard T

  1. Tamsin, thanks for tips on database - I agree that it would be far superior for the FM database to be tightly integrated with VW. As for the rest, yes you missed the point - we're talking about editing the graphics of a plant once it's been created - it's horrendously difficult.

  2. I know you can do that - but we use the same base graphic for different plants of different sizes. I just can't understand how we're expected to be able to work with something where the graphical representation on the screen is completely different in size to the actual objects on screen as demonstrated by selecting them.

  3. Why is it so hard to edit the 2d graphics of defined plants? Say for example a tree is defined with a spread of 4000mm. The tree was created from a symbol that had a diameter of 1000mm. When I go to edit the 2d graphics of the plant and select all the objects, they are at the size of the original symbol, even though it looks like I should be editing the full size plant. In this example, the objects for editing are 1/4 the size of what I expect.

    Thus, if there is any fill/gradients, any editing becomes very painful, hit and miss, almost impossible, because you can't see what you're doing with any accuracy.

    Conversely, if the original symbol is larger than the created plant, editing the plant you have graphics that are larger than what the display shows, and they're "invisible" so editing is extremely difficult.

    Is this what everybody else is seeing? Or is it something odd going on with my system?

  4. There's definitely a problem with some hardscape objects/definitions. Take the attached screen captures for example.

    It's a simple Hardscape, of type Paving/Grid, with Pattern Size set to 400. The second image shows what happens when I move the locus point for the hardscape into the corner - I get these weird angled lines coming out of nowhere. Other times, I get the first row/column of the grid becoming blank. It would be nice if someone from NNA could confirm if this is a bug.

  5. Max, from memory (it's a couple of months since I looked at it) one of the biggest problems is that using Standards, you can only create one sheet of a particular type, which is an issue when you need to create several sheets of a particular type to cover the total site. There were some other things too but I can't remember what they were offhand.

    Erich - you're right, but in this context, we want to create an office standard, which is a customisation of the VW standards, so it works :)

  6. There needs to be an option for including the headings/categories as part of the general note, or as the General Note title, so you can have different general note objects for different things.

  7. Why, when creating a hardscape object from a polyline, do the attributes of the object change? The attached images show the attributes of the polyline prior, and the attributes of the hardscape object immediately after creation.

    Why the change? Both objects belong to the same class, and the class concerned is not set to "Use at creation", and the class is even set to No Fill, so how can the hardscape fill have a "By class" fill colour, when the class doesn't have one defined? It seems to have taken on the "By class" pen colour instead. Can someone please explain?

  8. I admit I didn't realise you could do it in the floating data bar. However I'm all for doing things in the least number of steps possible, and simply too. With the current method, to modify the height of a rectangle by 400mm takes as a minimum 7 steps:

    1. Click on corner of rectangle

    2. Move mouse away from corner to get the data bar

    3. Tab twice to the height field

    4. Press "End" on the keyboard to get to the end of the field

    5. Type "-400"

    6. Press "Enter"

    7. Click with mouse to accept changes

    It just seems like a lot of unnecessary fluffing around to me when it could be done simpler. Maybe I'm just spoiled coming from a system where the same operation would be just 4 steps:

    1. Click on corner

    2. Move mouse

    3. Type "400"

    4. Click mouse and all is done

    I'll certainly have to remember to use more math in fields, but I still think an 'L' field for editing rectangles would be very useful.

×
×
  • Create New...