> On Apr 12, 2017, at 4:42 PM, Shubham Rathore <shubhamrathore1...@gmail.com>
> wrote:
>
> Sir, I think volume needs to be defined before using analyze on the ehy. The
> analyze_general() doesn't take care of this. All I get is "analyze: unable to
> process ID_EHY solid
> ". Thus defining the volume may resolve the issue.
Shubham,
I’m not following what analyze has to do with annotations, the sequence of
transformations Daniel referred to, or how they get drawn. If this is a
different topic, please be sure to start a different discussion thread, i.e.,
change the subject instead of replying to an existing mail that is unrelated.
Not a major problem, but it can be very confusing.
As to your statement, the ‘analyze’ command (src/libged/analyze.c) doesn’t
require volume to be defined but will call a primitives volume callback if one
is defined and hooked into the primitive callback table
(src/librt/primitives/table.c). If the goal is to get EHY’s reporting their
volume, then certainly one will have to define a volume function (in
src/librt/primitives/ehy/…), hook it into the table, and ensure analyze can
call it.
Cheers!
Sean
>
> On Tue, Apr 11, 2017 at 1:21 AM, Daniel Roßberg <danielmrossb...@gmail.com
> <mailto:danielmrossb...@gmail.com>> wrote:
> The pipeline I drafted is the usual one for 3D objects. The
> annotations should draw themselves somehow on the 2D plane. My point
> was to identify this sequence of transformations in the BRL-CAD code
> and get the 2D plane -> screen part from it.
>
> Regards,
> Daniel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
