Jump to content

DomC

Member
 View Profile  See their activity

  • Posts

    585

  • Joined

  • Last visited

 Content Type 

Everything posted by DomC

  1. DomC
    "C:\\Temp\\Output.csv" would work also I would strongly recommend, always create path strings with the path module. So it is as proof as it can be and this works also cross-platform: import os path = os.path.join('C:', 'Temp', 'Output.csv') # or even more propper path = os.path.join('C', os.sep, 'Temp', 'Output.csv')
  2. DomC
    Excellent job, and 5 stars for the genuine execution! Thanks for sharing
  3. DomC
    I would say maybe a rookie error: #allowed >> produces no errors caching is off vs.SetPref(412, True) # turn off caching #don't do that >> seems to breaks the vs modul or ignore newer methods vs.SetPref(412, False) # turn off caching #allowed >> produces no errors caching is on #vs.SetPref(412, True) # turn off caching
  4. DomC
    Must be specific an issue of my vso 🤔 I will STF (Search Till Found)
  5. DomC
    Hello I have a Vectorscript tool (not Event driven 2024). This tool rund a python module. The tool is working so far. code of the tool PROCEDURE ClickCallback; VAR x1, y1 : REAL; path : STRING; BEGIN SetCursor(LgCrossC); GetPt(x1, y1); PythonExecute('import dev.tool.mod.poly2PIO'); END; RUN( ClickCallback ); the module poly2PIO runs this code: import vs import os #vs.SetPref(412, True) #turn off caching #vs.Message(str(dir(vs))) with open(os.path.expanduser('~') +'/file_vst.txt', "w", encoding='utf-8') as f: f.write('\r'.join(dir(vs))) # error here isOnLine undefined method isOnLine = vs.PtOnLine((0,0), (-10, 0), (10, 0), 0.00001) everything and also vs.PtOnLine() is working. If i use that tool. But then, if i run run another vso (Event Enabled path object) it seems that the vst does not have the same vs-function anymore as before. Also if i use a standard vso (Script Based like the Rolling Stairs) the vs class in my vst do not contains the same methods anymore. import vs #from datetime import datetime import json import math import copy #import uuid import os import base64 import time #import urllib.request import code.common.controler as controler #vs.SetPref(412, False) # turn off caching with open(os.path.expanduser('~') +'/file_vso.txt', "w", encoding='utf-8') as f: f.write('\r'.join(dir(vs))) The functions in the vst does not work anymore. Also other vst's have the same issues now. The special thin i do is, that i run a pascal script and call a python after i click in the drawing. For further debug i write a text file with dir(vs) which lists all methods of the vs class. If i then compare the two files, i can see, that the dump written from file_vst.txt has much less methods available (left) as the file dumped from the vso? Somebody knows if this is a normal limitation or if it is worth for further diving in? I think not many devs wrapps a pascal around a python script so maybe this is a normal limitation that the methods freezed on a specific version or it is just a bug? It looks some-like, that methods after 2014 are not included now for my vst. Anybody knows what could going on? Here a screenshot from the method list compared with diff Merge
  6. DomC
    Maybe you make something like this and skip the certificate update? Maybe it is not necessery to import certifi on windows and the request will work without certifi? And then skip the ssl context part.
  7. DomC
    Marionette is a Programming-Tool. In such tools wer are in a place to have the force to produce wonderful artwork or unwanted behaviors (crashes?) and comparative we are mostly alone with our artworks. And thanksfully there are forums like this other people can help for bringing those projects to success. I took a look a the Marionette Control-Point and agree, there is some space for improvement: 1. Fixing Axis I think @Gregi wantet to fix one axis. This is not possible because the position of the control-point comes from the Mouse not from a value inside the script. This value is just a default value. To change the control point by script itself is theoretically possible to manipulate the Record of the Marionette Node where the position of the point is stored but it would be very hard (Because also the position of the PIO is involved). So this is not a bug it works the way the feature is designed. 2. Moving 3D Point in Standard View. If I am in a standard view (front right etc.). Lets say from right and I move the point in z-Direction, the x value from the point snaps on the working plane and the x-value gets 0. Which can maybe produces issues in the script inside the PlugIn. So working plane should be used or unwanted values have to be intercepted inside the script (which is always the most costly part). So if the script crash because the width of the pio change to 0 it is not a bug in the code of the 3D modification point. It is just an unhandled error. Error can be handled on different places. In shoft: OK, I can see, that the reshape behaviour of this modi-point can be improved and i will report this as an enhancement Request. 3. Position of the 3D Point outside of PIO geometry. If the Modification Point is the most outside object in a PlugIn. And not geometry is there, the position of the Point somehow is calculated wrong relatively to the object. So in our test with Extrudes etc. it always works as expected. But If the extrude is smaller than the bbox of the modipoint and the 0-point it somehow Fails. I think, this is definitely a bug. I will report. 4. Position of the 3D Point with layer elevation I think this is already known but I try to give it an impact. Generally, there are not much additional layers of error-handling between marionette and the Script Engine. I think the more "idiot-proof" something is made the weaker it is. Not 100% the truth (It could be possible to have both). But this is the way I am still pleased even if my script crashes 😁
  8. DomC
    This may also help
  9. DomC
    OK, the part of the code which I will not paste is the part how you update your certificates by the script on mac computers to make python accept them to communicate over TLS (SSL) (https instead of http). caution should be exercised.
  10. DomC
    The forum allows me not to paste some code ... I think maybe for security reasons. Or your testing api request: import urllib.request import json api_url = "https://jsonplaceholder.typicode.com/todos/1" result_string = '' with urllib.request.urlopen(api_url) as f: result = json.loads(f.read().decode('utf-8')) vs.AlrtDialog(str(result)) An other real example with a http request url, if you can't get https to work import urllib.request import json import math #dezimalgrad in minuten und Sekunden umwandeln (copy paste aus dem Netz) def deg_to_dms(deg, type='lat'): deg = float(deg) decimals, number = math.modf(deg) d = int(number) m = int(decimals * 60) s = (deg - d - m / 60) * 3600.00 compass = { 'lat': ('N','S'), 'lon': ('E','W') } compass_str = compass[type][0 if d >= 0 else 1] return '{}º{}\'{:.2f}"{}'.format(abs(d), abs(m), abs(s), compass_str) h = vs.FSActLayer() x = 2600000 y = 1200000 z = 500 #Nimmt Position von aktiviertem Hilspunkt, Objekt oder Symbol sonst Bern Sternwarte als Vorgabewert if h != vs.Handle(0): x,y,z = vs.GetLocus3D(h) #vs.AlrtDialog(str(vs.GeogCoordToVWN(x, y))) vs.AlrtDialog(str(vs.VWCoordToGeog(x, y))) xPt, yPt, zPt = vs.PtDialog3D('LV95 Koordikante zu WGS84', x, y, z) #Abfragestring auf dem Geportal direkt im Internet url = "http://geodesy.geo.admin.ch/reframe/lv95towgs84?easting="+str(xPt)+"&northing="+str(yPt)+"&altitude="+str(zPt)+"&format=json" result_string = '' with urllib.request.urlopen(url) as f: result = json.loads(f.read().decode('utf-8')) #Antwort vom Geoportal interpretieren und umwandeln in json result_string = str(result['easting']) + '\r' + str(result['northing']) + '\r' + str(result['altitude'])+'\r\r'\ 'Grad: ' result_string += '\r' result_string += 'Grad Minuten Sekunden: \r' + deg_to_dms(result['easting'], 'lat') +' ' + deg_to_dms(result['easting'], 'lon') vs.AlrtDialog(str(result_string))
  11. DomC
    Maybe not necessarely. urllib is a standard library and also should do the job. Give a usable feedback or your request:
  12. DomC
    Oh, this is an old code and not very nice one. Without testing: 1. The vs.GetType should replaced by: vs.GetTypeN(res) 2. The node returns not the Symbol Name. That means the node itself insert the Symbol. In fact it looks, like the output just returns the last inserted symbol. Which means the node should insert the symbols in the number of rows and should do the job but not returning the resulting symbol handles. With that node, you can't use the output useful disconnect symbol node and print debug node.
  13. DomC
    Agree with Letti I would vote for the smart solution using the function node without wrapping.
  14. DomC
    Edit: Added a New Version 1.0.2. where the script tries to convert non-valid cell numbers to numbers. The script tries to convert every cell so I hope this has no other negative effect. However the the existing Example is Version 2023 and works also on my Windows System with Swiss-German and German Keyboard Layout (Switzerland uses Decimal seperator ".", Germany uses ",").
  15. DomC
    Seems like this is the case here. On windows OS, some Input Fields convert to comma decimal separator. Der Input darf keine Kommas als Dezimaltrennzeichen haben. Das scheint aber hier auf Windows der Fall zu sein wie schon im ersten Kommentar erwähnt.
  16. DomC
  17. DomC
    omg By this occasion I see the Movie here by movie-time 1.0.5. We can see, the Model of the Start-Picture of Vectorworks 2023! How time is running😁
  18. DomC
    Hi It should still work in 2023 from my view. Which one you try to use? With the Worksheet input there could be an issue, if part numbers are no numbers and if values are seperated with comma instead points. I made a short test with input by layer and worksheet v2 both are working here. The others are old versions for 2019 or 2020. Sorry, the Versioning is not clear. v2 is newer than 1.0.1
  19. DomC
    Hi A possible workaround I once used is: 1. I had a big library document with much of Elements. Importing, reading informations, delete/purge would be time-consuming. 2. On the library document running a script after every change. The Script dumps the needed informations to a file which contains the metha-data from the library file 3. Or alternatively dump to a text object inside a symbol (I think does not work with too much data because of text size limitation maybe) and just import that index symbol to read source data 4. If the process should be automated there could be used a custom "save" command which dumps the data automatically before saving the file import json def update_library(): log_info = [] log_info_sym = [] counter_sym = 0 counter_xg = 0 listID, numItems = vs.BuildResourceList(16, 0, '') # Symbols dumps = {} SymbolLibraryDump = None for i in range(1, numItems + 1): counter_sym += 1 res_name = vs.GetNameFromResourceList(listID, i) sym_h = vs.GetResourceFromList(listID, i) if sym_h != vs.Handle(0): t = vs.GetTypeN(sym_h) found_cabinet = functions.get_XG_Cabinet_h_in_symbol(sym_h) if found_cabinet: dump = functions.attach_infos(sym_h, found_cabinet) dumps[res_name] = dump counter_xg += 1 log_info_sym.append(f"{res_name} {dump}") else: pass # log_info.append('kein Korpusmöbel gefunden') if 'SymbolBibliothekDump' in res_name: SymbolLibraryDump = sym_h else: vs.AlrtDialog(str(res_name)) if SymbolLibraryDump: vs.DelObject(SymbolLibraryDump) log_info.append('Daten an Symbole anghängen:') log_info.append(f"{counter_sym} Symbole im Dokument-Zubehör") log_info.append(f"{counter_xg} Symbole mit KM im Dokument-Zubehör") log_info = log_info + log_info_sym field_value = json.dumps(dumps, indent=1) vs.BeginSym('SymbolBibliothekDump' + vs.Date(2, 2)) vs.CreateText(field_value) vs.EndSym() log_info.append('Dump Symbol generiert (index zum auslesen aus anderen Dateien)') log_info = rename_symbols(log_info) return log_info
  20. DomC
    I think asking ChatGPT can be helpful but it is not faster than searching the forum. But for sure, it is good entertainment: lol
  21. DomC

    Version 1.0.1

    44 downloads

    This Marionette uses a Web-Dialog to create color schemes. The created colors can be imported as colors and textures directly in Vectorworks. Instruction: 1. Run the Network 2. configure colors 3. Don't forget to click "save" 4. close Web Dialog, the Vectorworks fetches the created colors and creates a preview with rectangles. Hint: right click > Wrap Marionette Network > right click > convert to menu command
  22. DomC

    Version 0.0.9

    40 downloads

    This Marionette can be interesting for Laser and cutting jobs. But Mainly it is Study how to use the Vectorworks Web-Dialog to access a Web-Application. The Date is send and reveived over (REST) API. The Exchanged Data is an SVG which is parsed over JSON Formats. Used Engine for Nesting is www.svgnest.com Follow this 9 steps to use the Script. Looking complexe but it is so easy! It is just a detailed Documentation of all steps This Marionette Network is sending all shapes on a layer (or by custom criteria) to a Web-App which contains a SVGnest installation and a custom API for Vectorworks 1. Draw a BIN on which you want to NEST the other shapes. Place it topleft of the BIN on your Origin 2. Tested with Layer Scale 1:50, 1:20 mm and BINs of ca. 1-2 meters. It works with all Units, sizes and scales but the very first Preview may be very small, cropped or too big. 3. No Holes in polys are supported directly (you can have but nothing would be placed inside) But if you draw a smaller shape inside another it is taken as a hole. 4. If ready run the Marionette (You will have to cancel by not saving the result or cancel in the dialog after the nesting process) 5. If you have multiple CPU cores it will go much faster. It uses one worker for every core. 6. Click on your BIN, choose the settings button (twice). If you define an offset between the parts reduce the curve-tolerance smaller than one. 0.5 as Example or lower if you see any issues. 7. Press START and wait till parts are placed on the BIN. The Process will calculate infinite and try to optimize the result till you click STOP. 8. Press SAVE, wait a sec and then just exit the VW WebBrowser by close or press the Button Bottom right to close. 9. Choose Option to move your original shapes on the BIN(s) or a copy Known Limitations: - Some shapes are not converted correctly to SVG maybe. Which is not a big accident because the Application do not import some geometry it keep the original geometry. - Complex geometry could take (too) long to nest. - I take took no control on the nesting process which is processes the NESTING the process is powered by https://svgnest.com Notes: You can also use an alternative way: 1. Export DXF to inkscape and export SVG 2. Or directly export SVG by https://forum.vectorworks.net/index.php?/topic/78280-export-to-svg-menu-command/ (The exported SVG from the Marionette is not directly accessable and also the quality and compatibility is just fitted to that one usecase so quality of the Marionette SVG is maybe low compared to the above professional Export-PlugIn) 3. Import it to SVGnest.com or use their new project DeepNest As I mentioned. Primary a study how connect to an even bigger world out from a Marionette. BTW such a connection can be a task nearly as big as the nesting-part itself.
  23. DomC
    Hi After specific Manipulation there is a need of ResetObject. Some commands included the proper Reset of the Result some not. In my Script you can see, that if you remove the reset of the parent object, the visible geometry is different from what you get if you edit the path extrude and exit it (same effect as resetting). If for your example it is not needed (because you do other actions with the result which may reset the objects itself) you can delete it. Beside that, it would not have a big speed impact because in a script every reset is added together if you reset 10 times it will reset just once anyway. "Punktkörper" is called "Mesh". Not sure I understand this question. You mean the result of your solid boolean operation is a mesh? Normally this is not the case at all. The Result of using solid boolean node should be a generic solid not a mesh. Even if you use a mesh in a solid operation the result is normally converted to a solid not a mesh.
  24. DomC
    vs.ResetObject() actually regenerates the pio and change the geometry after with vs.SetRField() parameters are changed and I tried also 1167. The specific thing here is, that the cabinet contains also plugins (Custom Parts) which maybe are not reseted as expected and the additional relations of fittings interact with the parts and not directly with the cabinet maybe. I will give accessing the sub-pios of the cabinet and if that not will not be of use i will wait for another solution. Already I am in contact with the genius devs from extragroup but there are always some other more important tasks to address so I wondered if i could bypass this limitation on the script-side.
  25. DomC
    Thank you for that feedback Hippocode and JBenghiat. Of course you are absolutely right. I should have been more specific about what I'm trying to do in the first place. I have a script that reshapes interiorcad cabinets together with custom parts and milling pios which are attached to that objects. Unfortunately, applying a vs.ResetObject() to these objects disconnect their connections to the fittings and other associated elements. The PIO itself runs a code, that is able (if nothing went wrong) to keep that relations. So there are some options: 1. The developper of that PIOs implements an API which can be triggered by vs.ResetObject() 2. I find a way to fire the right events to that PIO so that it is forced to regenerate (It also has a button to update) 3. It is maybe a bug in the vs.ResetObject() #1 is maybe the best option but if it can be controlled by the script itself it would be seen prefered. Here what the script does. It is open source and addresses a very often mentioned requirement from customers.
×
×
  • Create New...