> On Apr 13, 2014, at 1:40 PM, Ilie Denis wrote:
>
> Hi! The main thing that I am concerned are the next variables:
> idb_magic,idb_major_type, idb_minor_type and idb_ptr. Until now I have some
> idea about this, but I am not quite sure. idb_ptr=point trace ( form
> generating point trace ),
Hi! The main thing that I am concerned are the next variables:
idb_magic,idb_major_type, idb_minor_type and idb_ptr. Until now I have some
idea about this, but I am not quite sure. idb_ptr=point trace ( form
generating point trace ), and idb_major_type, idb_minor_type might be a
clasification of th
Hi!Could you describe me the variables purpose from rt_db_internal from
"raytrace.h" library.
Thank you!
Ilie-Ablachim Constantin-Denis
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integra
On Wed, May 23, 2012 at 1:44 PM, brlcad wrote:
> On May 23, 2012, at 12:23 PM, Tom Browder wrote:
>
> I see no function to deal with changing individual bu_vls characters.
...
> It's easy enough and common in the code to just directly access the string.
> Example:
...
Thanks.
-Tom
---
On May 23, 2012, at 12:23 PM, Tom Browder wrote:I see no function to deal with changing individual bu_vls characters.
Have I just missed them or should I just access the bu_vls string
directly?
It's easy enough and common in the code to just directly access the string. Example:int main(int ac, ch
On Wed, May 23, 2012 at 11:23 AM, Tom Browder wrote:
...
> I envision them like this:
On more thought, maybe slightly different versions (size_t and char
inputs, int returns):
int
bu_vls_readc(struct bu_vls *vp, const size_t pos)
{
BU_CK_VLS(vp);
/* error to request past ending char */
In the process of trying to deal with the vls regression failure on
32-bit *nix systems I see the need for some hackery for an old type
specifier. The hack involves creating a tmp bu_vls as a copy of the
current format string and modifying it.
I see no function to deal with changing individual bu
On Wed, Apr 4, 2012 at 6:32 PM, Edward <55549...@qq.com> wrote:
> Hi!
> when I input draw sph.brep in command line,It only draws a half
> circle.It is different from draw sph(draw a frame model). I‘m confused
> about it. Is it related to the structure of brep?
>
Short answer - yes, it has to
Hi!
when I input draw sph.brep in command line,It only draws a half circle.It
is different from draw sph(draw a frame model). I‘m confused about it. Is it
related to the structure of brep?
I have submit my proposal.
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/plu
On Jan 15, 2011, at 7:10 AM, Tom Browder wrote:
> I have seen several places in the tree with chunks of code like this
> (from fedex_main.c):
Changes to source code in src/other is generally discouraged, with
the exception of src/other/URToolkit, src/other/libtermlib, src/other/
libutahrle, s
I have seen several places in the tree with chunks of code like this
(from fedex_main.c):
fprintf(stderr,"and is one or more of:\n");
fprintf(stderr,"e entity\n");
fprintf(stderr,"p procedure\n");
fprintf(stderr,"r rule\n")
Alex,
My apologies for the belated reply but it's take a while to review
this problem in detail. I believe we talked about this some on IRC
(maybe?) ... but regardless, this is a long-overdue reply. In short,
I think you found what I'd effectively consider a bug but is actually
an initi
Hi all,
I don't know if I should be asking for help on the dev
mailing list or not, but I suppose I will quickly be told to stop if
this is the incorrect procedure.
I've been trying to add a binary file into a ".g"
BRL-CAD file using the 'rt_mk_binunif()' fun
Bengt,
Yes, there are updates regularly posted to the brlcad-news mailing
list and the main website at http://brlcad.org
When dsp tessellation support is added, the change is immediately
reflected in our NEWS file (included in all releases) which becomes
part of our announcements too. Y
Bengt,
No problem. The missing implementation isn't specific to either g-
stl or mged. It's the geometry engine that represents and describes
all BRL-CAD geometry. You'll run into the tessellation problem with
the DSP for *any* of the exporters as they all require tessellation
to perfor
Bengt,
Hello and thanks for writing!
The error message you mentioned (_nul_tess unimplemented) pretty much
sums up the problem. To export any geometry to the STL format
requires tessellating the geometry and apparently tessellation of the
DSP primitive is not yet implemented.
It really
16 matches
Mail list logo
