to control which part is allowed to connect to other parts and how. We will first look at the basics of defining rules, and then how to use the rule generator to create them automatically. Finally we will look at how to use connection types to allow more control on the final aggregation.
Video topics:
- Rules introduction: 00:27
- Rules basics: 4:25
- Using the rules generator: 13:22
- Using rule types: 16:58
Download the tutorial files here: https://bit.ly/wasp101_003
Watch the full playlist: https://www.youtube.com/playlist?list=PLCn3-_9Z4-E5A0EFluiMldlEbDufMiN1g
---
Download Wasp at: https://www.food4rhino.com/app/wasp
Wasp Newsletter: https://mailchi.mp/e0ccee5c4e32/wasp_newsletter
Source Code: https://github.com/ar0551/Wasp…
It seems the sender in your app and the UDP receiver in GH have are sharing the same port. I would chose two ports, one for each application. GH will listen for messages sent to its port from your app, and your app will listen to messages on its port sent by GH. You would give the UDP sender in GH the port for your app, and when you send messages from your app, they should be sending to the port given to the UDP Receiver in GH.
The (7), (14), and (8) deal with the bit size arrangement of the data to be sent. ASCII Text is a 7 bit character encoding http://msdn.microsoft.com/en-us/library/system.text.encoding.ascii(v=VS.90).aspx, in the background the stream of doubles is working in an 8-bit array. This is a part of gHowl we have also been meaning to revamp in order to make sending of more specific data types a possibility. Hopefully we can tackle it in the next revision.
…
IF the platform is "unsuitable" (or there's others more suitable) then disproportional amount of effort is obviously required for the same sort of result (or "similar"). And well ... er ... if the design goal is solid modelling ... chances are that a surface modeller MAY classify as unsuitable (but may not depending on the case).
Given the opportunity: Personal data: strictly AEC sector, AECOSim/Microstation (25 years, main BIM/General CAD purpose app) + various vertical Bentley Systems AEC apps + Generative Components (~10 years, main Parametric app) + CATIA/NX (20 years, main MCAD app) + Quest3D (~10 years, main VR app) + ... + you name it.
UGLY news: I run a practice > this means that I'm used in evaluating/addressing problems having TEAMS in mind, budget, alternatives, deadlines, clients, study guarantees, claims, clauses ... > this means that I'm often very bad/off-topic if an one man show task requires some opinion/solution/workflow.
Anyway ...
... with regard your issue I'll provide an indicative approach after this w/e ... but chances are that would be carried over exclusively without native components.
best, Peter
…
Please mail me the file that is causing problems so I can debug it.
Regarding your quad-core, Rhino and Grasshopper are not multi-threaded applications. (Very few apps actually are). Therefore I can only use 1 of your cores which equals about 25% of a quad-core machine.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 4:07am on November 10, 2009