Sir,
- I have already completed a part of the annotation.c file.
The functions included till now are:
1) rt_annotation_check()
2) rt_annotation_prep()
3) rt_annotation_prep()
4) rt_annotation_shot()
5) rt_annotation_norm()
6) rt_annotation_curve()
7) rt_annotation_uv()
8) rt_annotation_free()
[Some of them will be empty because of the non- ray traceability of the
annotations]
Functions that are to be included are:
1) import4()
2) export4()
3) import5()
4) export5()
I would like to know more about the functions that should be included in
this file.
- From where exactly are these routines called from? Is it the rt^3 ?
- I was working on the import functions and then I came across the
functions ntohl(), bu_cv_ntohd() etc. I know these are related to the
byte conversion (endianess), but I'd like to exactly know about their
functioning.
Regards,
Shubham Rathore(:gabbar1947)
On Mon, May 15, 2017 at 11:17 PM, Shubham Rathore <
shubhamrathore1...@gmail.com> wrote:
> contd.
> -ively. Will surely consider this.
>
> Regards,
> Shubham Rathore(:gabbar1947)
> [apologies for the broken mail]
>
> On Mon, May 15, 2017 at 11:16 PM, Shubham Rathore <
> shubhamrathore1...@gmail.com> wrote:
>
>> Sir,
>>
>>>
>>> There are probable some misunderstandings.
>>> First, be careful with using the term "sketch". A sketch is a BRL-CAD
>>> primitive which isn't very interesting as it is because it's 2D and
>>> has therefore no correspondence in the 3D world. I.e. you won't find
>>> much sketches in BRL-CAD models (except maybe in extrudes). What you
>>> mean is probable drawing/blueprint/model.
>>>
>> Yes sir, this is very much clear. By the term sketch I meant the entire
>> geometric object that is made by the user and not the "sketch primitive".
>>
>> Second, the geometric objects which represent the real-world entities
>>> and therefore are the basic components of the models are the regions
>>> (special type of combinations: the Boolean combinations). Imagine a
>>> wall with a window in the middle. It can be build from two cuboids.
>>> But no canonical point from the underlying primitives (corners,
>>> centroids, middles of the faces) would be a good anchor point for an
>>> annotation with the stone type, for example. I.e., at least at this
>>> stage of development, I would leave the determination of the reference
>>> point completely to the user.
>>>
>> Fine, thus the user gives the coordinates as the input irrespect
>>
>
>
------------------------------------------------------------------------------
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
