Jump to content

line-weight

Member
  • Posts

    3,647
  • Joined

  • Last visited

Posts posted by line-weight

  1. 35 minutes ago, grant_PD said:

    It would seem like the best thing (I didn't say the fastest thing) would be for VW to allow for a "General Notes Style" where you get to dictate the formatting. 

     

    Although that would be useful in the long term, the General Notes object first needs to have the simple option of turning off the list numbering. Until that's possible, being able to style it wouldn't help.

     

    ...Unless you meant a style for callout objects? Yes it would be good to style callout objects.

     

    At present I "style" callout objects using dedicated classes which lets me set things like arrowheads. But it doesn't control all aspects.

     

     

    • Like 1
  2. 24 minutes ago, grant_PD said:

    So playing with the callout tool, I can turn off the bubble, and turn off the leader and the arrow, which just gives me the text.  So I guess you could have a bunch of these callouts laid out for your notes, but you wouldn't get your asterisks unless you manually entered them, or had them as part of the note.  There is a setting to make the first 21 characters of the note be the description, that might help you find them...

     

    It would seem like the best thing (I didn't say the fastest thing) would be for VW to allow for a "General Notes Style" where you get to dictate the formatting. 

     

    Yes, it seems that a neutered callout object is an option.

     

    This wouldn't put multiple notes into a tidy list like the general notes object can.

     

    (I don't want the asterisks there - they are only there to replace the numbering I don't want, using a method less cumbersome than the type of thing @Jeff Prince describes)

    • Like 2
  3. 1 hour ago, bcd said:

    This sounds like a job for the Title Block

     

    You can add data on a per Sheet

    Edit the Title Block Style

    Sheet Data>Manage Sheet Data>Add a new field

    Title Block>Edit Title Block Layout place some text and in the OIP convert it to Data Type>Link Value, Parameter>Sheet Data, your newly created field.

     

    Then via the Title Block manager you can select which Sheet Layers you want to display this text and edit it to suit.

     

    However, having the Title Block Manager speak to the Notes Database to enter that text would be the business.

     

    I'd not thought of the Title Block as a strategy.

     

    Is this going to be able to cope with say 50 different "general notes" that I might want in a variety of combinations depending on the sheet?

     

    I think it would also mean I'd have to put the notes in a fixed location that was the same on all sheets. That would mean that I couldn't place a general note in such a way that it applied to only one viewport on a sheet with multiple viewports.

  4. 2 hours ago, Tom W. said:

    I'm not sure how much milage there is in trying to generate reports from the Notes Database... But then I haven't used it for a few years + even then only lightly.

    In actual fact, for current purposes I don't even necessarily need to pull items from the notes database into a report. It would do just to have a basic manually drawn table, but I would want to drop some text blocks into it (using items from the notes database) that would update in the same way callouts do.

     

    But it seems like the only options for doing that are hacky versions of a callout object or general notes object. That is unless there's something I'm missing.

  5. 1 hour ago, Tom W. said:

    If the info in the callouts is info about objects then I think you are better attaching that info to the objects themselves rather than writing it up in the Notes Database. Then, as well as being able to return that info in whatever combination you want + in whatever graphical style you want in Data Tags, you can also use it to generate reports/schedules + to create Data Visualisations.

     

    However, when the notes are more general + aren't related to specific objects then it makes sense for that info to be stored somewhere else + this is why I've asked in the past for the Notes Database to be accessible from Data Tags. I don't want to use the Callout Tool for these notes because I want to use the same tool with the same graphical appearance for all my callouts/tags. But because I can't access the Notes Database from a Data Tag I have instead been storing my 'general notes' in a Record Format which I can then call on from a Data Tag but it is literally just a very long list in a pop-up + the Notes Database would be a preferable way of storing the info.

     

    The other important thing to say is that under some circumstances it can be very hard to get your Data Tag to 'see' the object you are attempting to tag (section VPs for example) which makes a mockery of the whole functionality. In these circumstances it's quicker + easier to just use a note that comes from a list than data attached to the object.

     

    So I think there are benefits to using Callouts + the Notes Database + benefits to using Record info + Data Tags but the best arrangement would be if both functionalities were combined + you didn't have to choose one or the other...

     

    I'm not sure how much milage there is in trying to generate reports from the Notes Database... But then I haven't used it for a few years + even then only lightly.

    Thanks.

     

    I guess I am kind of the other way round from you ... I have got myself invested in the notes database approach and don't really want to start mixing up with data tags for similar reasons of graphic consistency (and sticking with what I know already).

     

    I think you are quite right that there are (at least) two kinds of notes, ones that are associated with a specific object and ones that are more general, and currently VW doesn't seem to make it easy to deal with both types in the same system.

     

    I think actually there are more kinds than that... There are notes that are specific to one object, notes that are specific to a type of object, notes that might apply to multiple objects, notes that are just to do with reading the drawings, and so on. The notes database isn't currently sophisticated enough to cope with all this in a tidy way. I can see why you might want to use record formats because then you can have multiple fields and (presumably) choose which ones you want to be used for a data tag.

     

     

  6. Well, my workaround above sort-of works but is not great.

     

    I'm realising that I'd like to expand this to a more general question, which is whether there is any other reliable way to extract data from the "notes database" other than via a callout object or a general notes object.

     

    For example, can I get the info into a worksheet?

     

    Say I have a bunch of fixtures & fittings and each has a spec including product reference and so on. The same fitting might appear on multiple drawings - plans, internal elevations and so on, and it's straightforward for me to point to it with a calllout, and have that callout display the spec info pulled from the notes database. And if I change the spec of that fitting, then all the callouts that point to it, on multiple drawing sheets, can update accordingly.

     

    But if I then want to make a schedule of fittings, formatted as a table, can I do that with a worksheet where I can pull in the relevant specification text for each fitting? So, if I update the text in the notes database, it'll update across all callouts but also in that table?

     

    I seem to recall other threads where I think @Tom W. has said he uses data tags instead of the notes database. Have I reached the point here where I realise the reason for that - or am I missing something basic?

  7. @Kristin Bailey thank you for replying on this thread.

     

    I've submitted feedback via the "was this page helpful" link a couple of times.

     

    On one occasion I got a reply which was great - on the other, I heard nothing back. I don't know if that suggests things don't always get delivered to your team (this was at least a year ago I think).

     

    Also, in the thread I linked to above, I made some comments about how the process of leaving feedback about help pages could be made a lot easier - here's a link to the specific post:

     

    https://forum.vectorworks.net/index.php?/topic/104945-please-stop-telling-us-to-re-report-problems-via-black-hole-webforms/&do=findComment&comment=458101

     

    I do quite often come across things that I think are missing from, or could be improved, in the help pages but I have to say that much of the time I just don't have the energy to provide the feedback because of:

    1) the tedium & time needed to go through that feedback form

    2) a lack of confidence that my message will actually get read or acted upon, due to my previous experience of only sometimes getting a response.

     

    I'm sure you don't want to encourage so much feedback that you get swamped with it ... but addressing those two factors, I think, would make it more likely that people with constructive comments pass them on to you.

     

    As @E|FA 's linked thread above suggests - a proper ticketing system would make a big difference. Just getting a confirmation that something's been submitted, and a way of tracking it, helps give confidence that something is happening even if there's not an immediate reply.

     

     

     

    • Like 3
  8. 22 minutes ago, EAlexander said:

    Can't you just make a piece of text and convert it into a symbol? Than it would update globally. 

     

    Yes - I guess I could do that.

     

    However - the "general note" tool has the following useful abilities:

    - can pull the text from the notes database

    - can put multiple notes in a tidy list with a heading, preformatted

     

    It's just frustrating that I can't opt out of the numbering/lettering.

     

    At the moment I'm trying a workaround where I choose "note description from database" from that dropdown and for all the notes that I want to appear in my general notes list, I make the note description just an asterix.

     

    This gives me a general notes list like this:

     

    Screenshot2024-02-22at12_14_23.jpg.88710f734b6e1ed69f0b0a352de5b9c6.jpg

     

    And that's ok (ish) but it makes the notes rather awkward to manage because they can't have meaningful descriptions - I have to select each one in the list of stars to see what text it contains:

     

    Screenshot2024-02-22at12_14_43.jpg.5430805d1b6e2e80c736aa83ac05c130.jpg

  9. I make fairly wide use of the notes database & callouts, sometimes using keynote legends and sometimes not. This has its many annoyances but basically works for any callout note that I might want to repeat across multiple viewports. I can update the text and it'll update across all instances.

     

    But what about more general notes - that is, not attached to a callout and not attached to a particular viewport.

     

    For example I often want to put a note on a drawing sheet that says something like "Refer to window schedule on sheet XXX for full window details".

     

    I might want to have that note on several drawing sheets, and in the future I might want to change the wording, and have that wording update in all instances.

     

    There is the "general notes" tool but it wants to format the notes like this:

     

    Screenshot2024-02-22at11_02_03.jpg.3e52916f4e0f1b7c402eca6e48e9b027.jpg

    I don't want that "1." there.

     

    In the settings I can choose from this list:

     

    Screenshot2024-02-22at11_00_54.jpg.f823d42da837c523b01897aeb4b98129.jpg

     

    But I don't want any of these. It doesn't give me the option to have only the note text.

     

    Is there any way around this - a way just to have the note text?

     

    (Why don't I want the notes numbered? Firstly because it might cause confusion when there's also a keynote legend on the sheet. Secondly because it uses up page space needlessly. Thirdly because often I'll only want to have one note in that "general notes" object, and it then looks odd if it's numbered.)

     

  10. The way I deal with this, is that I rarely create a "new" class, instead duplicating & renaming an existing class which has similar visibilities as I want for the new one. This is hardly an ideal method and I still have to quite often edit saved views settings. If there's a better way of doing it I'd be interested to hear too.

     

    Commonly when I make a new class I'll want it to appear in some saved views/viewports but not others, so simply being able to make new classes visible everywhere wouldn't solve the problem.

    • Like 1
  11. 6 minutes ago, rDesign said:

    Personally, I typically put my 2D linework in a the annotations of a SL Section Viewport. 

     

    Same here.

    I don't bother with the VW "interior elevation" tool.

     

    I just make a regular section. Crop out the bits that aren't needed for the internal elevations. Draw as much as possible in 3D and only add final touches in 2D. The more you draw in 3D, the more automatic updates can be in all viewports, if you change the design.

     

    I'd not explode or flatten viewports because then you have to star again if you change anything in the model.

     

    The main thing I'm not entirely happy with, using my current method for interior elevations, is that I have to crop them to funny shapes manually. And sometimes the edges of those crops can be a little messy.

     

     

    • Like 2
  12. Yes, I see, the same happens for me.

     

    Mention of the custom selection command has prompted me to try something that I've not tried before - to see if I can specify that objects of a certain type, within the annotation space of a particular viewport, can be selected. There's a criteria "location" which lets me choose a viewport. When I do this, the chosen objects appear to be "seen" (they are counted in the dialogue box), but as you describe, aren't actually selected when I run the command. And this seems to be the case even with the relevant class turned on in the sheet layer view (as well as in the viewport).

     

     

  13. On 2/18/2024 at 3:05 PM, Tom W. said:

    I have just figured something out that has bothered me for a while which I think is related to this thread. Frequently when I copy a VP to create a new one + want to get rid of the duplicated Data Tags inside the annotations VW won't let me use the Select Similar tool to select those Data Tags. I have realised that the reason for this is that although the class those tags are in is visible for the VP (obviously) it also needs to be visible for the Sheet Layer: so whilst I can see the tags in the VP + can select them with the Selection tool, if I want to select them with the Select Similar tool I need to make their class visible in the Navigation palette as well. Is this expected behaviour? I thought the class visibilities as set out in the Navigation palette had no bearing on objects inside a viewport's annotations - like @Andy Broomell says. 

     

    Is this caused by something to do with the data tag objects, or something to do with the "select similar" function, do you think?

     

    (I don't really use either so haven't noticed this myself)

     

     

  14. There's quite a variety in how real-world sliding door systems deal with that corner junction. Some have a rather chunky frame member on one or both of the parts that meet; others are more focused on ending up with as slim a frame as possible. And there are bifold options too.

     

    If there were a dedicated door type with VW for this, for it to be useful it would be important that whoever designed it take a close look at how the various systems actually look.

     

    Several times I've ended up modelling these doors and their corner connections from scratch, in order to visualise what it will actually look like, for the benefit both of me and of clients. Sometimes I've modelled two systems so that they can be compared ... and a decision can be made about whether it's worth spending the extra money for the less clunky option.

     

    A decent parametric tool would save hours of work in those situations - but only if it was flexible enough to reasonably accurately approximate real-world door systems.

    • Like 1
  15. I'd like to know too - I often find it hard to find stuff.

     

    Have you realised if you clock on the magnifying glass in the search bar you get this, which can help narrow things down a bit?

     

     

     

    Screenshot2024-02-13at17_09_14.thumb.jpg.e303f322004937b02bc4b55beb1fcabd.jpg

     

    I sometimes use "search by author" when I'm trying to find a thread that I'm sure I posted at some point in the distant past!

  16. 3 hours ago, Tom W. said:

     

    Do you have Architect or Design Suite? Mine went up from £834 inc VAT last year to £906 inc VAT this year... This was after it being pretty much flat the previous three years. Seems like everyone is paying something different. 

     

    Architect. The £702 is including VAT.

    Price was £648 (including VAT) in 2022 and 2023. Previous to that, it varied quite a bit because I didn't always renew annually so it depended on various offers.

     

    Of course what we "get" for the price now, since the new model came in, is a different thing because it doesn't really have any resale value, and there's no option to say "no thanks at the moment" when it's renewal time unless you want costs to go up substantially thereafter.

     

     

  17. On 1/15/2024 at 6:58 PM, leecalisti said:

    @zoomer I hear you, as I've had a SS perpetual license since 2010 or whenever they started them.   Mine went up from $550 or so to $750 or so - I don't like it.

     

    Sounds like they have been giving you a better deal than us here in the UK - they want £702 this year (about an 8% increase on last year).

     

    £702 is $886 if google is to be believed.

     

    I'd prefer they reduced our fee to yours, rather than increasing yours to match ours, of course.

     

    Perhaps my comparison of costs is not actually like for like, because of tax or something.

    • Like 2
  18. It took me the best part of a day to initially get my head around it in VW2023.

     

    Certainly made my brain feel old and limited too. However...once I finally got it working on a real project file, it was rather satisfying (those horrible window reveals showing all the wall layers exposed, that we've had to live with in VW for years, finally gone).

     

    I found this thread rather useful to read, while I was trying to understand things. It seems like many people come up against the same issues when making their first steps:

     

     

    • Like 1
×
×
  • Create New...