Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About SLFY

  • Rank

Personal Information

  • Location
    Evergreen, CO

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ha! Well only one of the ships was in the fog. If I would have ever given it a thought, I would have realized that amount of data that would be required for a large 4K screen would be massive. Duh. Guess the moron who's big screen TV is a 10 year old 32" should keep his mouth shut on resolution. So I now see why you feel the monitor size is important for full use of the 4K - thanks. However, my point still stands. My newest monitor is a 17" 4K (laptop)...and now that I have used it for a while, when I go to replace my other 2K monitors they will be replaced with 4K regardless of the size I feel I can afford / have room for. In my mind there is a definite benefit to the resolution when I am working - not night and day, but a benefit.
  2. I hope we aren't two ships passing in the fog here..but I don't understand how a larger monitor helps with making use of the 4K resolution. The pixels per inch does not change regardless of how many inches big the screen is. Any 4K monitor is going to show a resolution that is higher than you can functionally work. Again the advantage is the detail you can SEE in the 4K monitor. If I could take a 4K resolution screen shot of my 4K screen, and opened it on a 2K screen, in such a way that all the pixel were showing, it would take up roughly twice as much screen in both directions.
  3. Hmmm. Windows scaling doesn't change my screen's resolution - it is still 4K. The scaling just changes the number of the pixels used for text, icons, etc. and, i believe that those things need to be of a certain size to be usable, regardless of screen resolution. And so does the size of objects you are snapping to. When I zoom out, I see more detail on my 4K monitor than I do on my other monitors - I don't lose line weight nearly as quickly, etc. So the 4K helps me visually...BUT...I can't use much of that resolution to actually work. And so perhaps that is what you mean by "working area" - and I would agree that functionally, the 4K monitor does not help my actual work flow a whole lot. I still need to zoom in to make the area I am working on large enough to accurately click and snap - and the amount of screen required to do that didn't change much regardless of the screen resolution - it has more to do with user interface accuracy. And in fact, I was at first regretting spending the money for the higher resolution monitor, because I thought I would be able to have more on my 17in "desktop". But, as I mentioned, I have gotten very used to the resolution, and I miss it when I am working on my larger older monitors, because details don't look as crisp and clean, etc. Is my 4K twice as clear as a 2K monitor. No. Is it more clear. Yes. Am I glad I have the 4K screen 6 months in. Yes. The closest analogy that comes to my mind is getting a new eye glass prescription after a year or two of growing older. I can still see fine with the old prescription, but...
  4. I run VW often on a 17" 4K Windows 10 laptop. I have the Windows display scaling set to 225%. Most everything works great and I am getting used to it to the point that I miss the resolution on my desktop monitor. The general display scaling setting is really just changing the size of the text and icons on the screen. I still get a benefit in the 4K resolution in the drawings I am working on. The only real issue I have with vectorworks is the size of the radio buttons in the object info pallet - they are very small and somewhat tedious to hit on the 4k monitor, and I have not found a way to scale them up without over scaling everything, but I have gotten used to it. Other applications vary. Some - mostly older software I have not upgraded - are not "resolution aware". I occasionally use an Adobe CS4 suite, for example. The photo I am working on looks great on the screen, but the tool pallets and menus were initially very, very, VERY small. But, I have found a work around in the program specific windows settings for almost everything where I needed to adjust the scaling different than what windows was doing. The only issues I have now are...I guess you would call them "sub programs" or other windows that open up within a program. Some of those windows open up and are not resolution aware, even though the main application is, which results in weirdness, or "teeny tiny-ness". But this is usually just things like help windows, message windows, etc. so not a real big deal. S
  5. I have found what appear to be a couple changes in the publish dialog that are, so far, just annoying - but I am wondering if there is a better way around them that I am missing? I publish PDF's in black and white, but I work in color. Two things have changed with the publish dialog in the 2020 version of VW... 1) when I add sheets to the publish side (while working in color) it shows them as ready to publish in color, like it always has. However, I used to be able to click on the first sheet in the list, hold shift and click on the last sheet, and change them all to B/W with another click - 3 clicks no matter how many pages. Now, I have to click on each sheet's color setting, then click on a little drop down menu to select B/W. Usually 3 clicks per sheet. A time consuming process when there are more than a few pages to be published. The obvious work around is to change the preferences to display black and white before going to publish (I have a scripted "document context menu" short cut), I just have to remember to do this before opening the publish dialog. I am wondering if there is a different way to do this...or? 2) I have always exported generated model images, and then re-imported those images onto my sheet layers. Doing this, not only saves a lot of model regeneration time as I work and add or change things, and other advantages, but it also always USED to allow me to publish a PDF with a B/W sheet border and other drawings, but a full color model image. My client could look at the full color version on their monitor, their printer converted the images to grayscale, or if they print in color, the dimensioned drawings would still be in black and white as they prefer. It has served me well for years and years. In the 2020 version, however, when I publish in B/W those imported color images are changed to gray scale in the PDF. So, unless I am wrong, I now have to publish the model image pages in Color...which means all my annotations, sheet border, other drawings, etc. are in color. When my client goes to print, those colors go to grayscale. So, now the border and other drawings and dimensions look very different, even hard to read depending on the color I use, especially when compared to the other sheets in the PDF. The only option I have come up with, is to modify my sheet border from colors to all black and white...which I can do, just an announce. But that doesn't allow me to put a color image on the same sheet with a black and white line drawing. So if I want to add a color model image, it has to be on its own sheet. I REALLY don't want to change all my classes to black, or even change the properties of the drawings on the same sheet as the model to be black... Am I just missing something here? A simple example of what I find I can no longer do, is below. A bit of a side note - 20 years ago when I worked in AutoCAD, the publish set up would allow me to set the print preferences for each class (Actually AutoCAD layer). This allowed me to print the entire drawing in black and white, but, say, print dimensions in color - different colors for different dimension classes (layers), regardless of what I used for color when drawing. This allowed the viewers to quickly determine the dimensions of different types of objects in the same drawing. Using something like the example below, I used to show door dimensions in one color for one cabinet maker, and box dimensions in another color for another cabinet maker. I added this to the VW wish list a couple times 12 or 15 years ago. I forgot about it because this client went to a black and white laser printer when their plotter died. But, it would solve both of my problems here. All I would need is a class for imported images, or even viewports, set to print/publish in color, and I could set all other classes to print/publish in B/W. There would be no need to change the setting of each page in the publish dialog each time, no unexpected grayscale images...There are only a couple of "tools" AutoCAD had that I have always missed in Vectorworks. That is one, and one I have never found a good work around for it. Vecrtorworks Designer 2020 Windows 10 Thanks, Sean
  6. This may have been posted before, I am not sure of the best way to word it. It would be really helpful if the script error window included the script name in the title bar. Obviously when you are creating a script, you know which script has the error. However, when a new version of Vectorworks comes out, and functions have been deprecated, etc., I will import an existing file to the new version, and I will get the script error window showing me what is no longer valid and where it is in the script... That is to say - short of taking the time to edit it on the spot using the edit button. I would just like to take note and fix it when I have time. Thanks, Sean
  7. Sorry Orso, I quickly read part of your reply in an email that popped up on my phone just as I was about to hit send on the example scripts. I didn't refresh the web page to read it before submitting, because I was afraid I would lose what I had ready to post. I only added that first line to my post. In that quick, small screen email scan, I read the comma between the two functions in that sentence as you including both as handling dimensions. Later I read your reply more completely. I took your recommendation and changed the function name, and decided to leave it in my scripts to include as needed. Rather than 0, I set the default - fail / error value to something very odd - I used 6.66mm - with a note to remind me. This way something will be drawn, but to the wrong size, if I ever use the Function in a script with a unit typo. Knowing how I think (or don't, obviously), nothing showing up is much harder for me to troubleshoot than figuring out why it is the wrong size. I also added a message to notify me of the error, but I use enough messages in some scripts that it may well be over written before I notice it. Sorry. But the added documentation for Labels was the intent of my post - and I still think a little more space should be provided to address the rules of using them - where they are to be declared, do not declare labels not being used, and that separate labels can be used in subroutines and perhaps an example that shows that. Again, in hindsight, this seems obvious, but until I saw an example of it, I don't think it would have occurred to me as a possibility. I still don't have any clue why I need to include a Label declaration in the user defined function within my long script, when I don't in others. This has me a little worried going forward with the evolution of this script and wondering if it is a different issue that I am unaware of still. Will a new vectoworks version expose the issue? Will I have trouble breaking it up into sub routines that I can use in other scripts as I plan? Cross those bridges if they ever come up I guess. For now it works. Sorry again Orso and thanks for your help, Sean
  8. Just saw the reply you gave as I was sending in my example. Good point. I will rename the user defined Function Str2Dim - so that I can include it when needed without messing with the original. Thanks, Sean
  9. Hi Again Orso, Again, I am the novice here, BUT...I believe you are wrong about the Str2Num Function that is built in to Vectorworks. If I include unit marks in the string, I get no result. If I add the user defined Function from the devoloper page above, it works as I need. Here is a screen capture of the Parameters of a test script I created, which includes the needed unit marks in the strings: This Script, using the built-in Vectorscript Str2Num Function results in nothing being drawn, regardless of which input choice I select: This Script, with the added user defined Str2Num Function works as expected: On the other hand, I have not been able to repeat my issue with the compiler registering errors on my GOTO Labels. I can add a label and a IF THEN GOTO _ to this script, but not the user defined Function and I get no compiling errors. So, my comment that "if you have labels in the main script you also HAVE to have them in any sub routines, etc. appears to be false...except in the case of my much longer script...so I guess I will go back to banging my head if I have other issues when I finalize that tool. Thanks again, Sean
  10. Thanks Orso. On the developer website it stated that Str2Num will not handle units, and this version of the function will...as I am adding both imperial and metric dimension choices to my dialog box, I need to be able to carry the units through. I haven't gotten to the point I have checked if that will in fact work in the existing str2num function. When I originally developed this vectorscript tool, I used the "dimension" input because I didn't want to try and figure out how to make a "string" input conversion work for both imperial and metric...I work in, and need to use both regularly, and in the same drawing file. As for using LABELs...this is syntax that may not be neat and eligant, but it is very simple for me to understand and follow and that goes back to my 30year old basic fortran training. I understand the potential problem of where you are going to...but it is very easy to follow the go-to statements through the script and find an issue. Follow the bouncing ball so to speak...might be time consuming on large scripts but simple to understand for my non programmer mind. I have never had errors in my compiled script that I wasn't able to diagnose pretty easily. And understand that I consider myself a novice but I have created twenty or thirty "tools" in vectorscript that I use on a daily basis. Some are 12years old and have grown as I add functionality. Perhaps 6 are 1000 to 2000+ lines of code, including this one. I do use "case of" when it makes sense, but, off hand, I can't begin to image how to do what I have some of these tools doing without using at least some LABELs. Some of my "inputs" will require going through 3/4s of the script, others may only go through the first 1/8th but then jump ahead to use the middle 1/8th and again for the last bit, etc. So my suggestion stands for the User Guide, if not reinforced. Please add the extra information, or more accurately, complete the information on how to use Labels. Reinforce the encouragement to use other methods if you like. Thanks Orso, Sean
  11. I will preface this by saying that to the extent I can write scripts, I am self taught. I had one Fortran class in college in the mid 80's. There is very little information about LABELS in the Vectorscript user guide that I could find, short of what it states in the GOTO statement section. And it is not easy to find info online for Labels in Pascal...not that there is much info needed: must be declared, where / how to declare them, do not declare labels not being used, AND a couple other little tidbits... I just spent HOURS learning that if the main procedure script uses Labels, then user any user defined functions / sub-routines ALSO HAVE TO USE LABELS...even if it is just 1 label for 1 statement. If I am mistaken please let me know, so that I can go bang my head on a wall again. ---- I am modifying a relatively large (for me) script and added a user defined function to replace the Str2Num function as suggested on the developer page http://developer.vectorworks.net/index.php/VS:Str2Num. I was changing the input from a dimension type to a popup (showing / limiting options to the dimensions available) ...and needed to be able to get the input back into dimension form. The script compiled fine before adding the user defined Str2Num function...however, after adding it, I continually got errors regarding the LABEL associated with every GOTO statement in my script. After much before mentioned head banging, experimenting and googling. I found an old website for pascal that gave a little more information about Labels - stating "Line labels defined within a procedure are exclusive to that procedure", and it gave an example showing Labels in the main and sub sections . This information didn't solve my problem, but it did eventually ring the very small bell my head...."Do I need to add a label to the user defined function?" No idea WHY this would be necessary but I have tried everything else. So: FUNCTION Str2Num(str :STRING) :REAL; Label 1; Var num : Real; BEGIN 1: Str2Num := 0; IF ValidNumStr(str, num) THEN Str2Num := num; END; And it compiles without any errors regarding the Labels in the main procedure. So not only do I think there should be a blurb about the possibility of adding separate labels to sub routines / procedures/ user defined functions within a main procedure or $INCLUDE files, it should state that you HAVE to use labels in those sub routines if you use them in the main procedure. Again, if I am wrong please let me know, and where I screwed up. Now I will have to see if it actually works. ūüėČ Sean
  12. Hmmm- maybe this is a Windows version thing? or is it a 2018 version issue? I have not upgraded to 2019 yet. The only way I have found to move through is to click on "next" or "prev"...takes a while to get to pages, say, 28 thru 32 this way.
  13. I realize I can get to the title block manager through an individual page, but I can't go to the next or previous page from there. So it is always a question...which will be quicker...open the title block up for each individual page I need to adjust, or click through ALL the pages in the title block manager, until I get to the ones I need. Being able to go to the title block manager from an open page AND then click to the next/previous from there would be great. At a minimum, being able to select or enter a page number to jump to after opening the Title block manager would be helpful. Both would be ideal.
  14. Thanks Kevin, I did go ahead and submit the offset issue as a bug as well, though I assume the fact that you submitted it would be more than enough to ensure it gets the needed attention. Thanks again, Sean
  15. This first part is just an FYI for anyone working with the ellipse tool...I learned a simple a geometry lesson / offset tool function lesson, the hard way. Vectoworks has an ellipse tool which works well. However, an "offset" shape of that ellipse is another ellipse that is your specified offset at the North, South, East, West coordinates ONLY. The curves will not maintain that offset as they travel along the curve. I believe the amount of the variance depends on the shape of the oval. The project is a custom conference table with inlaid veneers. I created templates to create the relatively simple shape templates on a CNC. This is a 190" x 80" oval. There is a solid wood boarder around the oval that is 4" wide. We found...only after running the CNC...that the offset at, say, the South East point, is about 3 3/4" not 4". I found I need to break the ellipse down to a polyline to get the offset consistent around the curves. I don't work with ellipses much, and since CAD came along I haven't had to draw one by hand. So it never occurred to me that the ellipse's curves would vary since the proportion ratio is changing. PERHAPS THIS IS SOMETHING THAT SHOULD BE TAKEN INTO ACCOUNT IN THE OFFSET TOOL? It seems to me that if you want another ellipse "X" amount bigger or smaller, the ellipse tool will do that nicely. But if you want an OFFSET shape, it will no longer be an ellipse. The other problem that occurred with these files is rather peculiar. For the smaller inside oval I created two simple shapes to be be run on the CNC again, for templates to use in the hand work. One is a rectangle with a 1/2 ellipse clip removed from it, the other is the same ellipse used to take the clip...simply an inside and outside shape. Upon exporting these to DXF files, there are a couple of anomalies that occurred to the shape...a slight taper to the end of some of the lines going into the next vertex. I regenerated the shapes and re exported with the same results. Odd, but even more so since there appears to be no "vertex points" at those transitions from straight to something other than straight...not in vectorworks...AND not in AutoCAD where the odd shape shows up. AutoCAD "regen" does not make them disappear as you might expect if it was a screen drawing resolution issue. What does get them to go away in AutoCAD is to explode them from shapes into component lines...then the lines show up as straight lines all the way to the correct vertex. I didn't think much of this, until the CNC operator pulled the file into his toolpath program. This program not only read the tapered lines, but connected them across the rectangle - resulting in a very odd shape. Again this started as a simple rectangle, with a 1/2 ellipse clipped out of the middle of one edge. I have attached the VWX and DXF files in case someone has a clue what happened...was it a CAD monkey error or an export issue. If anyone has answers or tips on this export issue, please let me know. The answer here was to to do the simple drawing in AutoCAD from the start. Who knows when it will crop up again, however. Thanks. Sean Vectorworks Designer 2018 Conf Table Center Oval Templates.dxf Conf Table Center Oval Templates.vwx


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...