JMR

For a large worksheet, changing the sorting order is difficult. There is no way to reorganise the order other than removing sorting and then doing it again. Some kind of editable stack would be great, think of what one can do with sheet layers, for example. Also the ability so remove/add sorting/summing etc. from several columns at once would be great.

The publish command always wants to publish to the last used directory, no matter which project is open or active. However, the projects always reside in their own directories, and switching to another project means the publishing directory has to be manually changed. This causes rather much unnecessary navigation. I'm not aware of any setting in this regard.

Thanks for the feedback to you both. Indeed it seems the 5900x and 5950x are no shows at the stores...one can order them but they don't give any info as to when it will arrive. I guess I have to wait a few months and see if the situation improves.

Some kind of stack that could be sorted manually would be great. Something like you can do with sheets and layers in the navigation palette. A separate window where you could change the sorting order by dragging. The same goes for worksheet criteria, actually. If you have a large worksheet with many sorting columns, it's a pain to change something in the middle, everything has to be removed first. Also the sorting sequence number is unreadable on a 4K display, and doesn't zoom.

Hi all, Time to replace the old workhorse at the home office. Any reason NOT to go with a Ryzen? Works fine with VW? Does anyone know what is the current status with promised multi-threading improvements in VW? Any views much appreciated, thanks.

We are still in 2020 sp6...since last May we haven't run across this issue. Maybe something that crawled back to 2021?

GetSpaceNameForObj does that, no? Only one has to be very careful with z values of objects and spaces, so that everything is included.

The file link still works, at least for me? If not let me know.

There is some discussion about a similar issue here, perhaps these are technologically related issues...? https://forum.vectorworks.net/index.php?/topic/70078-data-tags-moving-or-losing-connection/#comment-347987

A couple of things maybe worth trying: -Try publishing to PDF/A and check the DPI setting (max. 200 or 300) in the publish dialog, too. Sometimes exporting to PDF/A alone greatly reduces the file size. -Viewport class overrides can really bloat the PDF file size. Not sure why though. In general, PDF file size is something that really requires attention from the VW programmers. While there are Dropbox etc. to enable downloading of large files, council e-permit systems have a file size limit, usually 25 of 50MB. These files need to be in certain format as well, usually PDF/A. External helper programs like those mentioned above are great, but they may disappear from the web any moment or stop functioning - not an ideal solution. In some other thread there was discussion about VW not flattening the PDF at export, maybe on option for this would help.

Ok thanks, now it's working! Is there a way to round the calculation down to the closest integer? That way I could calculate the loss percentage as well. Eg. the second row from the bottom is as follows currently: Divs in L #datataghelper#.#FullLength# / #ΔX##m_1_0# The meter and .1 accuracy is to get rid of too many decimals. data tag sample.vwx

Unfortunately no effect on the end result...

Helper record is set to "integer"...is this correct?

Thank you. I got it working for a second, then it disappeared and can't get it to work...enclosed is a sample file, in case you'd want to take a look? The definition reads: #ΔX#x#ΔY# circumference #PERIM# area #AREA##sq m_0_1# #datataghelper#.#FullLength# / #ΔX# #datataghelper#.#FullWidth# / #ΔY# What I see data-tag test.vwx

Ok thanks. I do have VSS so I guess it's time to update very soon. I'm designing a facade with fibre-concrete sheets that come in size 1200x3000mm. Ideally, the most economic divisions are therefore eg. 300,400,600 and 300,500, 600,1000 etc. I'm trying to use the data tag as a tool to quickly check and demonstrate to the client if the desired sheet can be economically cut out from a 1200x300 full-size sheet. This has to do with finding the optimal solution when it comes to looks and waste/cutting. "#ΔX# / 3000" kind of works but it returns 0.33 for a 1000mm etc, not so easily demonstrated to a client.