Jump to content

SLFY

Member
  • Content Count

    56
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SLFY

  • Rank
    Apprentice

Personal Information

  • Location
    Evergreen, CO

Recent Profile Visitors

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

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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.
  7. 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.
  8. 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
  9. 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
  10. SLFY

    2017 Crashes, laggy, screen refresh

    Probably no real useful information. I just want to add another frustrated voice to the crowd in my small effort to speed up the SP3 release. I will say that I get different weirdness and lags in different files . What I don't see is any difference when I switch from using my Intel i7 laptop to my AMD FX8350/GTX 550ti GPU desktop. The same issues happen in the same files - occasional long lags, no screen update until a zoom in or out, layer to layer viewport crops getting ignored as I zoom in, certain objects partially disappearing most of the time. I have monitored resources while working and while weirdness happens - I haven't seen the GPU go above 30% load, or 40% memory usage. Similar for the CPU. I work in multiple, relatively small files compared to an architectural file, say, and am in and out of different files many times a day. Some few seem to behave normally, whether new 2017 files, or updated 2016 files. At least one behaved better after purging unused....everything. The worst behaving file is a very small project - all 2d - and the file has been purged - again the same issues happen on either Windows computer. I have had ZERO actual crashes since switching over from 2016 to 2017 SP2 ... so I don't believe any error logs have made out to the fixers...probably not a good thing. Good luck engineers...and please hurry. Learned a little more. This issue with drawing layer to drawing layer view ports (crop gets ignored at some zoom levels) is only an issue when the viewport was created in VW 2016. New view ports (created in VW2017) in the same file behave normally,
  11. SLFY

    Plug-in script edits not saved

    That is true. I thought I would put them were it would be easy to find them when its time to upgrade something. However, I had the same problem on my previous computer when I had my plug-ins in the app data folder...never spent the time to try and discover the problem then, but I now assume it was the same...but it may be that they got set to read only somehow as well. Its all good now. Thanks, Sean
  12. SLFY

    Plug-in script edits not saved

    Thanks Hippothamus, While my plug-in files were not read only, your reply led me to the answer. For reasons I do not understand, I needed to set VW to be run as administrator. (I am the only user on this computer and I am the administrator - why, windows, do I need to let you know I want the program to run with the my privileges?) Anyway - that solved the problem. Thanks a ton. Sean
  13. This is probably a simple question. I have quite a few plug-in scripts I have written - most very simple - that I use daily. Most were created in VW 2012. While using 2013, I had a notion to make a small change to one script, and tried several times. It showed it compiled successfully. Put after closing the script editor, nothing was changed. I had tried restarting vectorworks after doing the edit, etc. but it never saved. It wasn't worth a lot more head scratching so I forgot about it. Now I have updated to 2014, and there have been changes. In particular, a menu script I wrote and have used daily for a couple years updates my worksheets, sets the drawing date and then opens up the Export PDF Batch window. After some confusion, I realized the "publish" command has completely replaced the Export PDF batch. So I go to change the script and the same issue - no warnings but no save - happens. So, my question is Why? is the issue due to the fact the scripts where written in an older version? I have no protection or encryption set. Before I go to the trouble to try and create a new, almost duplicate plug-in and adjust my workspace, I thought I would ask the experts. Thanks, Sean
  14. Never mind, Not sure what fixed it - maybe updating the new install to service pack 2. All the playing and restarting I did before didn't. But, its acting like I would expect now.
  15. Is there a way to turn Selection highlighting ON but not have it completely block out any symbol I select? An open box would be fine, if an outline of the symbol object is not possible. But a solid box to represent the selected symbol makes any accurate moving and snapping of the symbol nearly impossible. Just upgraded to 2014. Don't remember how I had my settings in 2013 and before, but I don't remember having this issue ever. Perhaps I have always had the selection highlighting off. That it is how it will have stay now in any case, unless someone lets me know there is a way to change it. Thanks, Sean

 

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.

√ó