Re: [brlcad-devel] [BUG] MGED fails to start from dmenu application launcher or with /dev/null as stdin

On Mar 27, 2018, at 10:13 AM, Pronaip via brlcad-devel wrote: As the title says. I think it should be left up to the user to decide if they want to run in interactive mode or not, because trying to guess it will just add unnecessary complexity and make things flakier. Providing /dev/null as

[brlcad-devel] [BUG] MGED fails to start from dmenu application launcher or with /dev/null as stdin

As the title says. I think it should be left up to the user to decide if they want to run in interactive mode or not, because trying to guess it will just add unnecessary complexity and make things flakier.-- Check out th

[brlcad-devel] Bug Tracker and Research

Hi, I did the one thing I for some reason hadn't done up to this point. I googled BRL-CAD bug tracker. D'oh. I guess in terms of coding experience, it's very much been quite practical stuff for me up to now; take a system of molecules, abstract their properties as matrixes and simulate some condi

Re: [brlcad-devel] Bug in "sh/make_dep.sh" or "misc/debian"?

On Mon, Mar 31, 2014 at 12:36 PM, Nicholas Reed wrote: > If you're asking about the "Unknown media type" messages, > they appear to be harmless ... Thanks, Nick--that fixed it! Best regards, -Tom -- ___

Re: [brlcad-devel] Bug in "sh/make_dep.sh" or "misc/debian"?

If you're asking about the "Unknown media type" messages, they appear to be harmless (http://askubuntu.com/questions/18806/why-does-update-mime-database-complain-about-uri-rtspt-and-other-unusual-types, http://forums.debian.net/viewtopic.php?f=30&t=54063). On Mon, Mar 31, 2014 at 11:58 AM, Tom Br

[brlcad-devel] Bug in "sh/make_dep.sh" or "misc/debian"?

When removing and installed local-built BRL-CAD Debian package, I get the following: $ sudo aptitude remove brlcad [sudo] password for tbrowde: The following packages will be REMOVED: brlcad 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 0 B of archives. Aft

Re: [brlcad-devel] Bug spotted in g-step

On Fri, Oct 25, 2013 at 2:58 PM, Rob McDonald wrote: > All, > > Thanks for your work on BRL-CAD and STEPcode. I've been studying some of > BRL-CAD's step export capability to learn to use STEPcode to do the same. Excellent! > In that studying, I found a subtle bug that probably won't bite anybo

[brlcad-devel] Bug spotted in g-step

All, Thanks for your work on BRL-CAD and STEPcode. I've been studying some of BRL-CAD's step export capability to learn to use STEPcode to do the same. In that studying, I found a subtle bug that probably won't bite anybody, but just to be sure, I wanted to report it here. The units set up in t

Re: [brlcad-devel] bug

Pawleeq, Thanks for the bug report! On Aug 20, 2013, at 4:52 PM, jans...@email.cz wrote: > 1. Try the B command on the same object and see if you get the same behavior. > B command works fine. > Try the "E" command on the same object. > 2. If possible, extract the problem objects into their

Re: [brlcad-devel] Bug: attr, comb_color???

On Aug 20, 2013, at 9:06 PM, Clifford Yapp wrote: > I think that sounds good - so to "downgrade" the attributes it would > be something like "attr upgrade -v3" ? Part of me wonders if that > would set up an expectation for dbupgrade supporting a similar > capability... Something like that. I d

Re: [brlcad-devel] Bug: attr, comb_color???

On Tue, Aug 20, 2013 at 2:00 PM, Christopher Sean Morrison wrote: > I think the issue right now is that the > conversion happens at too low a level, in an attempt to catch most commands, > and that will likely need to change. I can confirm that - I was trying to make rgb and color transparently

Re: [brlcad-devel] bug

Thanks. I'll take a look when I get home. Best, -Tom -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for ef

Re: [brlcad-devel] bug

Please see below: -- Původní zpráva -- Od: Tom Browder Datum: 20. 8. 2013 Předmět: Re: [brlcad-devel] bug " Pawleeq, can you do a few things: 1.  Try the B command on the same object and see if you get the same behavior. " B command works fine.  "

Re: [brlcad-devel] bug

Pawleeq, can you do a few things: 1. Try the B command on the same object and see if you get the same behavior. 2. If possible, extract the problem objects into their own .g file and send it to this list. 3. Give us details of your OS. Best, -Tom

Re: [brlcad-devel] Bug: attr, comb_color???

On Tue, Aug 20, 2013 at 1:00 PM, Christopher Sean Morrison wrote: > On Aug 18, 2013, at 04:33 PM, Clifford Yapp wrote: > On Sun, Aug 18, 2013 at 3:52 PM, Tom Browder > wrote: > > So, what is the user to do to truly affect the color: use both rgb and > color > > attributes? Or does it matter sinc

Re: [brlcad-devel] Bug: attr, comb_color???

On Aug 18, 2013, at 04:33 PM, Clifford Yapp wrote:On Sun, Aug 18, 2013 at 3:52 PM, Tom Browder wrote:So, what is the user to do to truly affect the color: use both rgb and colorattributes? Or does it matter since BRL-CAD may be treating 'color' and'rgb' as aliases for each

Re: [brlcad-devel] Bug: attr, comb_color???

On Sun, Aug 18, 2013 at 3:33 PM, Clifford Yapp wrote: > On Sun, Aug 18, 2013 at 3:52 PM, Tom Browder > wrote: > > > > So, what is the user to do to truly affect the color: use both rgb and > color > > attributes? Or does it matter since BRL-CAD may be treating 'color' and > > 'rgb' as aliases f

Re: [brlcad-devel] Bug: attr, comb_color???

On Sun, Aug 18, 2013 at 3:52 PM, Tom Browder wrote: > > So, what is the user to do to truly affect the color: use both rgb and color > attributes? Or does it matter since BRL-CAD may be treating 'color' and > 'rgb' as aliases for each other? Tom, The rgb/color thing is basically a consequence o

Re: [brlcad-devel] Bug: attr, comb_color???

On Sun, Aug 18, 2013 at 2:52 PM, Tom Browder wrote: > I'm showing a user how to use scripts for mged to change region and > combination attributes and I ran across a situation I can't explain: > ... > Now run the comb_color again: > > mged> comb_color stool2 80 80 80 > mged> attr show stool2 >

[brlcad-devel] Bug: attr, comb_color???

I'm showing a user how to use scripts for mged to change region and combination attributes and I ran across a situation I can't explain: Use the comb_color command to set RGB on a combination with no existing color: mged> attr show stool2 stool2 combination: mged> comb_color stool2 80 80 80 mged

Re: [brlcad-devel] Bug 3197208 (mged's red command) should be reopened

On Tue, Aug 16, 2011 at 22:26, Christopher Sean Morrison wrote: ... >> I added a comment to the subject bug because I think red ought to >> either be unavailable or at least get the user to acknowledge the >> danger before red is actually activated.  red is not yet ready for >> production use Tha

Re: [brlcad-devel] Bug 3197208 (mged's red command) should be reopened

On Aug 16, 2011, at 12:54 PM, Tom Browder wrote: > I added a comment to the subject bug because I think red ought to > either be unavailable or at least get the user to acknowledge the > danger before red is actually activated. red is not yet ready for > production use and the bug should be reop

[brlcad-devel] Bug 3197208 (mged's red command) should be reopened

I added a comment to the subject bug because I think red ought to either be unavailable or at least get the user to acknowledge the danger before red is actually activated. red is not yet ready for production use and the bug should be reopened IMHO. I'm using BRL-CAD 7.20.2 and red still has prob

Re: [brlcad-devel] Bug in or around sh_billboard.c

On Jan 21, 2011, at 8:27 AM, Tom Browder wrote: > cc1: warnings being treated as errors > sh_billboard.c:125:12: error: pointer of type 'void *' used in subtraction > /bin/bash ../../libtool --tag=CC --mode=compile gcc-4.5.1 > -DHAVE_CONFIG_H -I. -I../../include -pedantic -W -Wall -Wundef > -W

[brlcad-devel] Bug in or around sh_billboard.c

Getting this on current trunk build: cc1: warnings being treated as errors sh_billboard.c:125:12: error: pointer of type 'void *' used in subtraction /bin/bash ../../libtool --tag=CC --mode=compile gcc-4.5.1 -DHAVE_CONFIG_H -I. -I../../include -pedantic -W -Wall -Wundef -Wfloat-equal -Wshadow -

Re: [brlcad-devel] Bug or user error: comment in tcl source for asc2g

On Mon, Jan 10, 2011 at 13:57, John Anderson wrote: > The asc2g code looks at the first line of the input file to > determine if the file is the current ascii version (i.e., a tcl script) > or the old ascii version. It is looking for a "title" or "put" command > on the first line to identify t

Re: [brlcad-devel] Bug or user error: comment in tcl source for asc2g

The asc2g code looks at the first line of the input file to determine if the file is the current ascii version (i.e., a tcl script) or the old ascii version. It is looking for a "title" or "put" command on the first line to identify tcl input. This could be easily changed to do this check

Re: [brlcad-devel] Bug or user error: comment in tcl source for asc2g

On Jan 6, 2011, at 6:15 PM, Tom Browder wrote: > Should I not expect comments to work? Sounds like a bug to me. Given they are simple text/tcl files, being able to add comments seems like a no-brainer. Cheers! Sean ---

[brlcad-devel] Bug or user error: comment in tcl source for asc2g

As an experiment I added a tcl comment as the first line in my hitherto working ascii file which makes a valid .g with asc2g t.asc t.g Now it bombs with: ERROR: _bu_alloc size=0 (cnt=0, sz=8) botbld: vertices ERROR: bu_malloc(0) ERROR: bu_malloc(0) Saving stack trace to (unknown)-14268-bomb

Re: [brlcad-devel] Bug #1525332

On Thu, Nov 26, 2009 at 07:59, Christopher Sean Morrison wrote: > Tom, Hi, Sean, Happy Thanksgiving! > It has.. One of the guys (indianlarry) was looking into the bug just > last week, but still no resolution just yet.  If I recall, there was > some issue with the tracker item not having a .g ex

Re: [brlcad-devel] Bug #1525332

Tom, It has.. One of the guys (indianlarry) was looking into the bug just last week, but still no resolution just yet. If I recall, there was some issue with the tracker item not having a .g example case? Cheers! Sean On Nov 10, 2009, at 8:16 PM, Tom Browder wrote: > I added a new commen

[brlcad-devel] Bug #1525332

I added a new comment to the subject bug bback in mid September but have seen no response from anyone. Has it shown up on anyone's radar? Thanks. -Tom Tom Browder Niceville, Florida USA -- Let Crystal Reports handle th

Re: [brlcad-devel] Bug in 7.14.0 Configuration

That makes sense. The source tarballs for 7.14 were generated on a system with automake 1.6 so the prebuilt build files have the cppflags bug. Once you ran autogen.sh it was fixed, just doubly so. :-) I'm adding a regression test now to detect per-product cppflags since this isn't the fir

Re: [brlcad-devel] Bug in 7.14.0 Configuration

On Wed, Nov 12, 2008 at 6:44 PM, Christopher Sean Morrison <[EMAIL PROTECTED]> wrote: > > Did you run ./autogen.sh before running configure, or just run configure? > The bombardier_CPPFLAGS have both tcl and tk flags set so if everything is > working right and is up to date, it should be includi

Re: [brlcad-devel] Bug in 7.14.0 Configuration

Did you run ./autogen.sh before running configure, or just run configure? The bombardier_CPPFLAGS have both tcl and tk flags set so if everything is working right and is up to date, it should be including the dirs via that directive. Setting AM_CPPFLAGS is sort of the shotgun approach since i

Re: [brlcad-devel] Bug in 7.14.0 Configuration

On Wed, Nov 12, 2008 at 5:57 PM, Christopher Sean Morrison <[EMAIL PROTECTED]> wrote: > > Tom, > > Ah, that's actually a bug in automake. The rule that builds bombardier > already had those two CPPFLAGS set but just set on that product -- > AM_CPPFLAGS sets it on all of them in that directory.

Re: [brlcad-devel] Bug in 7.14.0 Configuration

Tom, Ah, that's actually a bug in automake. The rule that builds bombardier already had those two CPPFLAGS set but just set on that product -- AM_CPPFLAGS sets it on all of them in that directory. Automake 1.8 (iirc) and later don't have the bug, but the fix is to just make it a product-spec

[brlcad-devel] Bug in 7.14.0 Configuration

I noticed that my build failed when compiling ./src/util/bombardier.c because tk.h couldn't be found. The line (no. 146) in ./src/util/Makefile.am that reads: AM_CPPFLAGS = ${TCL_CPPFLAGS} was changed to: AM_CPPFLAGS = ${TCL_CPPFLAGS} ${TK_CPPFLAGS} After running autogen.sh and configure a