I think both blend and shell are enormously powerful - if they fail, there is often a reason

I'd like to see a big red circle where a given function is failing - so that I know where I should focus

Jol

Yes, you're right. I do not see any contradictions here. VC/Shark is difficult to learn. I have been using it for about 10 years and it is still full of surprises for me. Often surprises end with crash.

I would like that the software worked for me. Not vice versa.

What can be done:
1. More understandable tools with more tool tips.
2. More convenient Data Entry tools. Maybe slider, numeric range etc...
3. Preview function. Maybe real-time changes of geometry. Maybe control points.
4. Forced blending of edges(or another function). VC/Shark has something similar(Feature Interaction, Retain Features etc...) but somewhat more radical is needed.

It's not normal when any edge stops workflow and it takes hours to find a solution to this problem.

As for Shell Feature, it's always strange for me to see "no solution for a vertex:bla-bla-bla". As one famous theater director said:"I don't believe."

Hello,

Do you have an example you can post a file or a sample file.

Thanks
Jason

Hello

Sure I understand,. Can you make a sample file up and post it.

Regards

Jason

Ok,

Can you submit the file to the bugreporter so the specific of the condition can be traced?

http://www.punchcadlabs.com/page10/page10.php

Thanks
Jason

curious if you got the file I sent a few days ago ??

As programming languages, shells typically have very limited features: their main power is from calling external commands.

However, there are a few features that are quite powerful and less commonly found or less well-known in other languages:

Streams, pipes, and redirection
Process management
Traps
These are particularly useful on multicore systems, as the processes can often run in parallel.

Streams
Streams allow one to operate on arbitrarily large data (codata) without needing to read it all in at once, progressively reading input or writing output; the most basic streams are standard input and standard output. Most simply this is done by operating on text data one line at a time. Pipes allow one to connect an output stream of one program to an input stream of another, allowing concurrent processing of data. Many of the standard Unix commands operate on streams, particularly for text processing, and are designed for use in pipes – these are sometimes known as filters. A standard idiom for shell scripts is to build a pipeline, connecting these to quickly build sophisticated and relatively efficient programs.

In addition to anonymous pipes, named pipes (aka FIFOs) allow complex interprocess communication (IPC)