Compare commits

..
169 Commits
Author SHA1 Message Date
Clifford Yapp 886b70e368 Trunk now has work-to-date for osg - delete branches (svn branch delete)
svn:revision:62975
svn:branch:openscenegraph
svn:account:starseeker
2014-09-24 20:32:04 +00:00
Clifford Yapp 1ea5ae5d52 Sync through trunk r62100
svn:revision:62102
svn:branch:openscenegraph
svn:account:starseeker
2014-08-12 18:42:50 +00:00
Clifford Yapp 1f430a0706 Merge in work to date from framebuffer-experiment branch to openscenegraph branch.
svn:revision:62070
svn:branch:openscenegraph
svn:account:starseeker
2014-08-11 19:07:08 +00:00
Clifford Yapp f1402f58bd Sync through trunk r62062
svn:revision:62064
svn:branch:openscenegraph
svn:account:starseeker
2014-08-11 13:36:25 +00:00
Clifford Yapp c2d70803a5 Sync through trunk r62021
svn:revision:62024
svn:branch:openscenegraph
svn:account:starseeker
2014-08-06 20:04:48 +00:00
Clifford Yapp 610c6417d6 Sync through trunk r61988
svn:revision:61993
svn:branch:openscenegraph
svn:account:starseeker
2014-07-31 18:58:53 +00:00
Clifford Yapp 9763433049 Add a note about struct client's usage of pkg_conn vs. Tcl_Channel
svn:revision:61988
svn:branch:openscenegraph
svn:account:starseeker
2014-07-31 18:23:25 +00:00
Clifford Yapp 9f5071dde5 checkpoint header work.
svn:revision:61987
svn:branch:openscenegraph
svn:account:starseeker
2014-07-31 18:21:50 +00:00
Clifford Yapp 60112b7b24 The pattern looks to be function get/sets for all the hard coded struct based settings, the the avs holding any others.
svn:revision:61984
svn:branch:openscenegraph
svn:account:starseeker
2014-07-31 13:48:06 +00:00
Clifford Yapp 218a985607 Return matp_t, not mat_t
svn:revision:61973
svn:branch:openscenegraph
svn:account:starseeker
2014-07-29 15:00:28 +00:00
Clifford Yapp 393564081d Another iteration of API pondering.
svn:revision:61972
svn:branch:openscenegraph
svn:account:starseeker
2014-07-29 14:41:21 +00:00
Clifford Yapp d7bb6151b0 Organize set/get sets together. Might be able to completely hide the dm struct, depending on how this works...
svn:revision:61971
svn:branch:openscenegraph
svn:account:starseeker
2014-07-29 14:08:11 +00:00
Clifford Yapp 7e4bace245 Sync through trunk r61966
svn:revision:61967
svn:branch:openscenegraph
svn:account:starseeker
2014-07-29 14:04:51 +00:00
Clifford Yapp b15b6dce0d Start actually mocking up the new libdm approach, to see if it is actually workable or not.
svn:revision:61966
svn:branch:openscenegraph
svn:account:starseeker
2014-07-28 22:23:01 +00:00
Clifford Yapp 686476d8d8 Sync through trunk r61952
svn:revision:61954
svn:branch:openscenegraph
svn:account:starseeker
2014-07-28 13:08:03 +00:00
Clifford Yapp fc484a7a23 Some funny line drawing, but it's hard to tell what the issue might be since this drawing mode is known to be really bad in a scene graph context. To be safe, make sure culling is off.
svn:revision:61944
svn:branch:openscenegraph
svn:account:starseeker
2014-07-25 20:54:39 +00:00
Clifford Yapp 79ca22bef0 OK, looks like (once we actually feed it properly into openscenegraph) the OpenGL translations of the matricies will work. (that transformation *really* needs to live in its own function, with proper docs...)
svn:revision:61943
svn:branch:openscenegraph
svn:account:starseeker
2014-07-25 20:15:18 +00:00
Clifford Yapp 52e6af3c7d Closer to correct drawing, but not there yet.
svn:revision:61940
svn:branch:openscenegraph
svn:account:starseeker
2014-07-25 18:12:28 +00:00
Clifford Yapp 341f39cb65 Set both view and projection matricies
svn:revision:61932
svn:branch:openscenegraph
svn:account:starseeker
2014-07-25 15:41:31 +00:00
Clifford Yapp f7d58c8b92 Not even remotely correct, but get something showing in osgviewer window.
svn:revision:61931
svn:branch:openscenegraph
svn:account:starseeker
2014-07-25 15:37:21 +00:00
Clifford Yapp 4696066120 Need to establish a 'rosetta stone' translation between libdm/mged and osg conventions. Set up an osgViewer to run 'in parallel' with the raw opengl context version of libdm's drawing.
svn:revision:61928
svn:branch:openscenegraph
svn:account:starseeker
2014-07-25 15:13:40 +00:00
Clifford Yapp af5bef8f55 More thinking about libdm API.
svn:revision:61925
svn:branch:openscenegraph
svn:account:starseeker
2014-07-25 14:17:12 +00:00
Clifford Yapp a93aa35694 Get osg building again after merge.
svn:revision:61825
svn:branch:openscenegraph
svn:account:starseeker
2014-07-17 21:56:24 +00:00
Clifford Yapp fc6c6e6070 Sync through trunk r61819
svn:revision:61821
svn:branch:openscenegraph
svn:account:starseeker
2014-07-17 21:18:44 +00:00
Clifford Yapp d46f6c43a2 Sync through trunk r61669
svn:revision:61672
svn:branch:openscenegraph
svn:account:starseeker
2014-07-11 19:24:42 +00:00
Clifford Yapp 61ddf58bb6 Have osg-test use db_full_path_transformation_matrix instead of the search-based matrix logic.
svn:revision:61634
svn:branch:openscenegraph
svn:account:starseeker
2014-07-10 00:06:26 +00:00
Clifford Yapp c66a30cfcd Finish putting ged.h back
svn:revision:61633
svn:branch:openscenegraph
svn:account:starseeker
2014-07-10 00:04:29 +00:00
Clifford Yapp a892d0cafb Sync through trunk r61609
svn:revision:61610
svn:branch:openscenegraph
svn:account:starseeker
2014-07-07 17:01:40 +00:00
Clifford Yapp 24a67c84dd Sync through trunk r61598
svn:revision:61599
svn:branch:openscenegraph
svn:account:starseeker
2014-07-07 13:09:40 +00:00
Clifford Yapp f862563508 Sync through trunk r61587
svn:revision:61588
svn:branch:openscenegraph
svn:account:starseeker
2014-07-03 21:46:47 +00:00
Clifford Yapp 22c1a5fa24 Rather than get into libged at all, is there enough information in the various GED structures to map information to a new libdm structure? Test that first, because libged refactoring needs a lot of design thought.
svn:revision:61580
svn:branch:openscenegraph
svn:account:starseeker
2014-07-03 19:12:14 +00:00
Clifford Yapp 054f10f441 More thinking on 'what information do we need for display list entries to have all the information a display will need?'
svn:revision:61565
svn:branch:openscenegraph
svn:account:starseeker
2014-07-03 01:08:21 +00:00
Clifford Yapp 6305fd62c6 Start thinking about what a new display list structure is going to look like.
svn:revision:61564
svn:branch:openscenegraph
svn:account:starseeker
2014-07-03 00:29:43 +00:00
Clifford Yapp f57da7657a Sync through trunk r61560
svn:revision:61561
svn:branch:openscenegraph
svn:account:starseeker
2014-07-02 23:59:53 +00:00
Clifford Yapp 8dbe178bcf Sync through trunk r61519
svn:revision:61520
svn:branch:openscenegraph
svn:account:starseeker
2014-07-02 13:31:26 +00:00
Clifford Yapp c420dcdf7a Sync through trunk r61517
svn:revision:61518
svn:branch:openscenegraph
svn:account:starseeker
2014-07-02 13:23:24 +00:00
Clifford Yapp 6a2259bfe1 Add a freetype 3rd party build for openscenegraph.
svn:revision:61512
svn:branch:openscenegraph
svn:account:starseeker
2014-07-01 22:02:06 +00:00
Clifford Yapp 4be09016bd Sync through trunk r61508
svn:revision:61509
svn:branch:openscenegraph
svn:account:starseeker
2014-07-01 21:28:25 +00:00
Clifford Yapp 2827b3e64a Revert libged changes - apparently the design intent of libged is that it does retain some view knowledge - question is where/how/how much.
svn:revision:61504
svn:branch:openscenegraph
svn:account:starseeker
2014-07-01 19:14:10 +00:00
Clifford Yapp df9f5b0284 More winnowing of libdm pieces - plot and postscript should be outputs of displays, not full-fledged display managers.
svn:revision:61482
svn:branch:openscenegraph
svn:account:starseeker
2014-06-30 15:08:16 +00:00
Clifford Yapp 30df746994 ged_vclip is no more - was just a copy of a libdm function.
svn:revision:61481
svn:branch:openscenegraph
svn:account:starseeker
2014-06-30 14:48:06 +00:00
Clifford Yapp e60dc093c4 Complete the first stage of dm extraction from libged - mged and archer build and run again. Still a great deal more extraction/rationalization to do before starting to rework the libdm API towards a scene graph approach, but this was the first stage.
svn:revision:61480
svn:branch:openscenegraph
svn:account:starseeker
2014-06-30 14:44:35 +00:00
Clifford Yapp f0a6e49602 Not quite there yet, but this is the first stage of extracting view management from libged and moving it into libdm.
svn:revision:61471
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 23:19:29 +00:00
Clifford Yapp d7836eb000 Use a (much) faster search for assemblies.
svn:revision:61456
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 16:58:30 +00:00
Clifford Yapp 3913cf1329 Don't need to actually identify the assemblies, just see whether we have any - faster search.
svn:revision:61455
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 16:48:13 +00:00
Clifford Yapp 3850863d77 Return code of search apparently wasn't returning the count - need to check why, we don't need the results table here.
svn:revision:61454
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 16:38:24 +00:00
Clifford Yapp 7db4b4e1d1 Attempt to generalize the drawing logic - managed to slow down the rendering in the process, needs more investigation.
svn:revision:61453
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 16:24:47 +00:00
Clifford Yapp 6832ec7c59 Get drawing working with the region optimization enabled. Need to look into creating just combs above regions to save memory, and lazily create lower level structure as needed, but shaping up.
svn:revision:61446
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 01:09:10 +00:00
Clifford Yapp 54b360c09b Need to be aware that the vertArray might already have elements in it. Gets us closer, but missing the stipple for subtracted elements.
svn:revision:61445
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 00:46:02 +00:00
Clifford Yapp 52b3930a00 Recreating wireframes as regions isn't working, not sure what's wrong yet...
svn:revision:61444
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 00:30:39 +00:00
Clifford Yapp d1a743b1c2 Not actually fully working yet (havoc looks wrong) but start setting up to assemble vlists for regions.
svn:revision:61443
svn:branch:openscenegraph
svn:account:starseeker
2014-06-27 00:17:31 +00:00
Clifford Yapp 8ffa458d41 Look into using a multimap to reconstitute comb structures below regions if we swap out the comb sub-nodes for a single common geometry node.
svn:revision:61440
svn:branch:openscenegraph
svn:account:starseeker
2014-06-26 21:24:21 +00:00
Clifford Yapp 8667711182 Modularlize the comb logic a bit.
svn:revision:61437
svn:branch:openscenegraph
svn:account:starseeker
2014-06-26 19:58:55 +00:00
Clifford Yapp dfea3de197 Don't need the duplicate map, just use the one already being built.
svn:revision:61435
svn:branch:openscenegraph
svn:account:starseeker
2014-06-26 19:43:30 +00:00
Clifford Yapp 59163dda54 Sync through trunk r61430
svn:revision:61431
svn:branch:openscenegraph
svn:account:starseeker
2014-06-26 19:05:58 +00:00
Clifford Yapp e08387ee22 Break out more logic into individual functions.
svn:revision:61425
svn:branch:openscenegraph
svn:account:starseeker
2014-06-26 15:14:25 +00:00
Clifford Yapp 3d5891a189 Break out the vlist extraction into its own function.
svn:revision:61424
svn:branch:openscenegraph
svn:account:starseeker
2014-06-26 14:13:31 +00:00
Clifford Yapp 8f5e52ddda Start figuring out how to handle regions as atomic objects in the scenegraph for performance.
svn:revision:61416
svn:branch:openscenegraph
svn:account:starseeker
2014-06-25 22:12:45 +00:00
Clifford Yapp 9a292b5c5d Sync through trunk r61413
svn:revision:61414
svn:branch:openscenegraph
svn:account:starseeker
2014-06-25 21:59:01 +00:00
Clifford Yapp 726e6afc6c Sync through trunk r61391
svn:revision:61393
svn:branch:openscenegraph
svn:account:starseeker
2014-06-25 16:29:29 +00:00
Clifford Yapp e4d29a0bb1 Sync osg with trunk through r61361
svn:revision:61362
svn:branch:openscenegraph
svn:account:starseeker
2014-06-24 14:59:14 +00:00
Clifford Yapp 05870b90b4 Strip down to osg and qt for graphical dm/fb - it's looking like a major API rework is in order, and we don't want more than the minimum options for that sort of iterative API development. Probably will consolidate the debug/txt/etc. options as well.
svn:revision:61339
svn:branch:openscenegraph
svn:account:starseeker
2014-06-17 14:56:01 +00:00
Clifford Yapp 11f8eb9ee1 Reorg slightly
svn:revision:61334
svn:branch:openscenegraph
svn:account:starseeker
2014-06-16 23:34:08 +00:00
Clifford Yapp a6764c30a4 Merge the trimmed down FrameBufferManipulator into if_osg.cpp
svn:revision:61333
svn:branch:openscenegraph
svn:account:starseeker
2014-06-16 23:26:33 +00:00
Clifford Yapp 8e04d302b9 Remove more from FrameBufferManipulator
svn:revision:61332
svn:branch:openscenegraph
svn:account:starseeker
2014-06-16 23:14:32 +00:00
Clifford Yapp f0abe54b35 Strip some unused bits out of FrameBufferManipulator
svn:revision:61331
svn:branch:openscenegraph
svn:account:starseeker
2014-06-16 23:07:03 +00:00
Clifford Yapp 339a31761d Add a Key handler (which is where we'll do the framebuffer bindings) but the osgViewer continues to insist on a camera manipulator to keep showing the image. Trim down the FrameBufferManipulator some more - if we need to have it, want it to be the minimal code to get the job done.
svn:revision:61330
svn:branch:openscenegraph
svn:account:starseeker
2014-06-16 22:55:23 +00:00
Clifford Yapp 0942dd4637 For now, we'll focus on osg. Ideally, in the end, we'll have osg and qt (maybe X and Ogre) so it's not clear if these functions will survive in their current form.
svn:revision:61329
svn:branch:openscenegraph
svn:account:starseeker
2014-06-16 20:21:33 +00:00
Clifford Yapp 92ec3d50cf point the osg branch's Archer to osg exclusively. Old MGED will be a lot more difficult...
svn:revision:61327
svn:branch:openscenegraph
svn:account:starseeker
2014-06-16 19:40:25 +00:00
Clifford Yapp 03c1812419 Generally speaking osgViewer does well as a framebuffer container, but the trackball handler isn't appropriate for this application. Start customizing the OrbitManipulator from OSG to suit the framebuffer use case - for now, just turn off the mouse's ability to rotate the image in 3D. Will need to figure out how to make it do more later - eventually, can try sending it back upstream for OSG inclusion, if it gets good enough.
svn:revision:61315
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 20:22:14 +00:00
Clifford Yapp 53c6cadf9e Don't need glfw any more
svn:revision:61311
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 17:09:44 +00:00
Clifford Yapp 377e723626 Get a working framebuffer going - the key, despite hints to the contrary online, turned out to be the image->dirty() call. Add in some timer magic, so we only update when we need to for the user instead of on every single scan line change.
svn:revision:61310
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 17:01:50 +00:00
Clifford Yapp af31fcf2d1 If we set up the quad and texture after the image is generated, we can see it.
svn:revision:61307
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 15:54:26 +00:00
Clifford Yapp 1d636113a6 Writing out a test image, it appears the raytracing data *is* in the image. So the question narrows to displaying it successfully.
svn:revision:61304
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 15:27:48 +00:00
Clifford Yapp c70a08cfe2 We'll want the ability to read and write PNG files from osg images.
svn:revision:61303
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 15:23:29 +00:00
Clifford Yapp 6389261030 Not sure we've got the right visual alignment - use free rotation to get a look at the quad and verify the image (which is apparently not getting the raytracing content yet.)
svn:revision:61297
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 12:30:55 +00:00
Clifford Yapp bcb99fef20 Clear set-but-unused warnings - the rest of it
svn:revision:61295
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 03:29:15 +00:00
Clifford Yapp 03491cc292 Clear set-but-unused warnings
svn:revision:61294
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 03:26:21 +00:00
Clifford Yapp 9a7f9d9fe7 Still don't see anything, but at least we aren't crashing now.
svn:revision:61293
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 01:11:08 +00:00
Clifford Yapp c5bad9ee8f Not working yet, but get osgViewer libfb compiling.
svn:revision:61292
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 00:52:32 +00:00
Clifford Yapp 7fb3ffc06a Start reworking libfb to try and use osgViewer.
svn:revision:61291
svn:branch:openscenegraph
svn:account:starseeker
2014-06-13 00:30:21 +00:00
Clifford Yapp 136b05aad8 Sync osg with trunk through r61286
svn:revision:61287
svn:branch:openscenegraph
svn:account:starseeker
2014-06-12 20:28:23 +00:00
Clifford Yapp 21ec992873 doesn't matter, so no need to change the setting.
svn:revision:61286
svn:branch:openscenegraph
svn:account:starseeker
2014-06-12 20:24:15 +00:00
Clifford Yapp fe29ccffb6 The optimizer helps improve FPS.
svn:revision:61269
svn:branch:openscenegraph
svn:account:starseeker
2014-06-12 13:47:10 +00:00
Clifford Yapp 97f6308802 Might as well note that these don't improve the FPS...
svn:revision:61256
svn:branch:openscenegraph
svn:account:starseeker
2014-06-12 01:16:53 +00:00
Clifford Yapp a8b1b7a12e Rework test a bit.
svn:revision:61252
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 22:31:13 +00:00
Clifford Yapp 6dc5f0c51e Get reasonable colors, but fps is slow.
svn:revision:61251
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 21:36:58 +00:00
Clifford Yapp f3af66ceb4 This is an incorrect application of color, but it does do something...
svn:revision:61249
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 20:09:59 +00:00
Clifford Yapp 43f7a1c0bb Few more notes on color.
svn:revision:61246
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 15:01:39 +00:00
Clifford Yapp fd9db0bcd1 Color is... complicated in a .g file. Need to figure out all the permutations and how to map them.
svn:revision:61245
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 14:51:54 +00:00
Clifford Yapp e1876e44fc Specify the stipple pattern.
svn:revision:61244
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 14:17:41 +00:00
Clifford Yapp cf6003cd7b Turn off lighting for wireframes. Start trying to figure out how to do dashed lines for subtractions.
svn:revision:61243
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 14:10:23 +00:00
Clifford Yapp 34c87c92b5 Get a wireframe view up, but not (yet) correct for coloring or lighting.
svn:revision:61234
svn:branch:openscenegraph
svn:account:starseeker
2014-06-11 01:43:28 +00:00
Clifford Yapp 034099941c No idea if this will work, but make group structure and matrix structure corresponding to comb structure.
svn:revision:61233
svn:branch:openscenegraph
svn:account:starseeker
2014-06-10 22:23:07 +00:00
Clifford Yapp 49ea1cadff Start to work on combs - should be able to define a Group, adding children directly where there isn't a matrix and adding an intermediate matrix transform when there is.
svn:revision:61232
svn:branch:openscenegraph
svn:account:starseeker
2014-06-10 22:13:20 +00:00
Clifford Yapp 8546c732b0 Start working on using the LINE_STRIP approach to wireframe drawing in the osg test program.
svn:revision:61231
svn:branch:openscenegraph
svn:account:starseeker
2014-06-10 21:53:18 +00:00
Clifford Yapp 32054f46e8 Sync osg with trunk through r61217, checkpoint the beginnings of an osg test application.
svn:revision:61218
svn:branch:openscenegraph
svn:account:starseeker
2014-06-10 14:46:10 +00:00
Clifford Yapp b8d5549bc1 Update osg branch through r61178
svn:revision:61179
svn:branch:openscenegraph
svn:account:starseeker
2014-06-09 17:39:30 +00:00
Clifford Yapp 8c65e301ae Update openscenegraph with trunk changes through r61164
svn:revision:61167
svn:branch:openscenegraph
svn:account:starseeker
2014-06-06 15:49:11 +00:00
Clifford Yapp edb126f437 Got the glfw version of this to interactively update - had forgotten the code to free the context for writing by other threads. Will try to do this with osgViewer, if possible, to avoid needing to keep glfw, but definitely checkpoint this working state for reference.
svn:revision:60421
svn:branch:openscenegraph
svn:account:starseeker
2014-04-10 19:42:39 +00:00
Clifford Yapp 67a8229819 The texture-based approach appears to work in this context, but still get the window flickering from Tk.
svn:revision:60420
svn:branch:openscenegraph
svn:account:starseeker
2014-04-10 14:34:07 +00:00
Clifford Yapp ce21726491 Back up to r60395 - preparing to try the texture based rendering with the working-but-flickering Tk window framebuffer.
svn:revision:60419
svn:branch:openscenegraph
svn:account:starseeker
2014-04-10 14:05:46 +00:00
Clifford Yapp 06d4c1fae9 Doesn't update, but there's a performance penalty to pay. Will try switching back to osg and see if triangle-based solution works with an osgViewer...
svn:revision:60413
svn:branch:openscenegraph
svn:account:starseeker
2014-04-09 15:10:19 +00:00
Clifford Yapp c8e94b4828 Can see image now, but no incremental update.
svn:revision:60412
svn:branch:openscenegraph
svn:account:starseeker
2014-04-09 14:52:34 +00:00
Clifford Yapp fb9777c30f Not working properly yet, but get raytracing data into texture memory a show in view.
svn:revision:60411
svn:branch:openscenegraph
svn:account:starseeker
2014-04-09 14:18:30 +00:00
Clifford Yapp ab721a2a2a Back to basics. First order of business will be to get librt's pixel output rendering using the texture+triangle method. Start with a minimally tweaked null fb, since this approach is very different from the old ogl approach.
svn:revision:60408
svn:branch:openscenegraph
svn:account:starseeker
2014-04-08 20:33:22 +00:00
Clifford Yapp a9ca7bf6b6 Looks like for a number of reasons (the most compelling being inserting framebuffers into scenegraphs) it's time to take the work done for rendering isst's raytracing via textures-and-triangles and port it to libfb.
svn:revision:60407
svn:branch:openscenegraph
svn:account:starseeker
2014-04-08 19:30:53 +00:00
Clifford Yapp ff38c1d539 OK. If I put the triangle example in the final lingering code, *that* displays - so the window at least *can* function in this context. Now, need to work backwards and figure out why the fb drawing isn't.
svn:revision:60406
svn:branch:openscenegraph
svn:account:starseeker
2014-04-08 13:59:52 +00:00
Clifford Yapp 88e6e6b909 Do some experimenting with glfw to see if it represents an improvement over Tk for this application. Not getting something quite right with the opengl view, but checkpoint testing thus far.
svn:revision:60405
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 23:30:28 +00:00
Clifford Yapp c8afe450a1 Need to make sure we're set up to display.
svn:revision:60404
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 20:59:30 +00:00
Clifford Yapp 4b492e7265 Even if we do customize the Tk bindings, not sure how to properly manage this - mged appears to be using a global somehow.
svn:revision:60403
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 19:12:29 +00:00
Clifford Yapp fa2a67b474 Trying to see how mged+libdm remain properly drawn... looks like they do a custom event handling setup. Not exactly sure how/if that can map to the libfb api - start experimenting.
svn:revision:60402
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 17:17:10 +00:00
Clifford Yapp 6972c6e320 Fix the 'load the libs' viewer invocation - we still need that.
svn:revision:60401
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 16:30:16 +00:00
Clifford Yapp d3a5d42f73 It looks like the issue is rather more fundamental. Essentially, when we invoke the viewer, we're activating the 'this is a scene' aspect of openscenegraph and that doesn't appear to interact well with the low-level drawing calls in the framebuffer. Several options here - figure out what's going on with Tk's events, see if something a bit more modern like glfw makes a better container, or map adrt's 'framebuffer is a texture on triangles' approach to the libfb framebuffer drawing. All have drawbacks, but it looks like digging deeper into Tk is what will have to happen, at least in the short run.
svn:revision:60400
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 16:27:22 +00:00
Clifford Yapp c76351701c Make a stab at creating an osg event handler that calls framebuffer updates - since nothing shows in the viewport when using a viewer currently (might have to draw to a texture and paint it on triangles for the scene graph, as opposed to the current raw opengl?) this isn't immediately useful. Checkpointing it because it does seem to make the call when the event occurs.
svn:revision:60399
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 15:20:40 +00:00
Clifford Yapp b598a97354 Start trying to ease the osgViewer in as a functional component.
svn:revision:60398
svn:branch:openscenegraph
svn:account:starseeker
2014-04-07 14:38:18 +00:00
Clifford Yapp 79ed8a47d0 Make a specific note to check out GraphicsWindowEmbedded
svn:revision:60396
svn:branch:openscenegraph
svn:account:starseeker
2014-04-06 15:56:34 +00:00
Clifford Yapp 302a9934b3 Went too low level in the APIs and wasn't getting the initialization code I needed to call. Short term, create and delete a viewer to make sure all the right setup is called. Longer term, study how the osgviewerFLTK example works in osg and find out if it makes sense to retool how we are embedding osg in Tk.
svn:revision:60395
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 17:38:54 +00:00
Clifford Yapp df152a236a I can get away at this stage with supplying *ONLY* osgViewer as a library, but I still need the no-as-needed flag or the initialization changes (I don't see my debugging line indicating the plugin directory has been loaded when starting MGED.)
svn:revision:60394
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 16:59:30 +00:00
Clifford Yapp ed47df2764 Try adding other osg libraries explicitly in case the ordering needs to be explicit...
svn:revision:60393
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 16:50:01 +00:00
Clifford Yapp 1591774202 Narrow down on the problem - libfb is providing the first set of osg libs, and libdm doesn't have to factor in - solve the issue in libfb, and we've got it.
svn:revision:60392
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 16:41:14 +00:00
Clifford Yapp 7e832087a2 OK, it's down to libfb and libdm
svn:revision:60391
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 16:26:50 +00:00
Clifford Yapp dd0e1f849b Getting closer - don't need the toplevel set
svn:revision:60390
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 16:17:02 +00:00
Clifford Yapp 01564ca94d Put things back for now, since osgGA seems to be a requirement for osgViewer...
svn:revision:60389
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 15:37:54 +00:00
Clifford Yapp debbb511b5 Try to get osg to be aware of osgViewer from the get-go (didn't seem to work...)
svn:revision:60388
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 15:32:40 +00:00
Clifford Yapp d34bfe0c53 Gah. Ubuntu is apparently adding --as-needed to ld linking by default now (http://stackoverflow.com/questions/8814707/shared-library-mysteriously-doesnt-get-linked-to-application) which in turn messed up the openscenegraph linking for BRL-CAD. Better solution here is to figure out *why* it's concluding it doesn't need those libraries, but until then here's a temporary work-around...
svn:revision:60387
svn:branch:openscenegraph
svn:account:starseeker
2014-04-05 03:46:05 +00:00
Clifford Yapp f2d0e559f6 Include fbio.h
svn:revision:60380
svn:branch:openscenegraph
svn:account:starseeker
2014-04-04 14:21:29 +00:00
Clifford Yapp 9774c5f54d Sync osg branch with trunk through r60359
svn:revision:60362
svn:branch:openscenegraph
svn:account:starseeker
2014-04-03 15:21:12 +00:00
Clifford Yapp 0f9b3f290a Add bio.h for Windows types.
svn:revision:60249
svn:branch:openscenegraph
svn:account:starseeker
2014-03-27 11:31:36 +00:00
Clifford Yapp 51d544a4df Cast bu_malloc type for MSVC
svn:revision:60246
svn:branch:openscenegraph
svn:account:starseeker
2014-03-27 10:54:41 +00:00
Clifford Yapp c72b47fa36 Sync with trunk thru r60212
svn:revision:60213
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 16:59:55 +00:00
Clifford Yapp 49ab312465 Remove XVisualInfo from the osg structures.
svn:revision:60212
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 14:17:25 +00:00
Clifford Yapp ebbfb428c8 Closer to building libdm osg code on Windows, but not there yet.
svn:revision:60207
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 02:40:48 +00:00
Clifford Yapp 3893af2623 Try stubbing in Tk_GetHWND for libdm as well...
svn:revision:60206
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 02:18:19 +00:00
Clifford Yapp 025d6f777d apparently Tk_GetHWND uses wind after all?
svn:revision:60205
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 02:12:31 +00:00
Clifford Yapp 05de27e9cf Try the Tk_GetHWND function for Tk on Win32...
svn:revision:60204
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 01:58:50 +00:00
Clifford Yapp cbb9896d98 Put variables in ifdef
svn:revision:60203
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 01:35:08 +00:00
Clifford Yapp 606fad0fd8 Comment and wrap some more code
svn:revision:60202
svn:branch:openscenegraph
svn:account:starseeker
2014-03-26 01:31:50 +00:00
Clifford Yapp e3e6546910 Swap out or comment out some more X specific code.
svn:revision:60199
svn:branch:openscenegraph
svn:account:starseeker
2014-03-25 22:17:17 +00:00
Clifford Yapp d86a7cb8b2 Use practical ifdef setup until the time comes for proper DM_ flags
svn:revision:60198
svn:branch:openscenegraph
svn:account:starseeker
2014-03-25 22:01:00 +00:00
Clifford Yapp 0102156c00 Check for the header as well.
svn:revision:60197
svn:branch:openscenegraph
svn:account:starseeker
2014-03-25 21:58:46 +00:00
Clifford Yapp 4701a865bc Test for the shm functions and conditionalize on their presence - has the net result of making the code look more like wgl-version on Windows.
svn:revision:60196
svn:branch:openscenegraph
svn:account:starseeker
2014-03-25 21:50:22 +00:00
Clifford Yapp a4728cd8bf temporarily, use _WIN32 to determine which osgViewer api we will need. The 'correct' solution will probably be a lot harder.
svn:revision:60191
svn:branch:openscenegraph
svn:account:starseeker
2014-03-24 22:30:34 +00:00
Clifford Yapp 36434e5872 Wrap ipc.h
svn:revision:60190
svn:branch:openscenegraph
svn:account:starseeker
2014-03-24 22:27:19 +00:00
Clifford Yapp aad0e5f4ba Add opengl library to link list
svn:revision:60187
svn:branch:openscenegraph
svn:account:starseeker
2014-03-24 17:56:03 +00:00
Clifford Yapp bea445c1ad We aren't worried about older versions of CMake - simplify some of this. It may go away altogether...
svn:revision:60182
svn:branch:openscenegraph
svn:account:starseeker
2014-03-24 14:28:03 +00:00
Clifford Yapp bc4074edd4 add SET_OUTPUT_DIR_PROPERTY_260
svn:revision:60181
svn:branch:openscenegraph
svn:account:starseeker
2014-03-24 14:22:09 +00:00
Clifford Yapp 3b81aedd8a Add one of the utilty macros to OpenThreads
svn:revision:60180
svn:branch:openscenegraph
svn:account:starseeker
2014-03-24 14:20:16 +00:00
Clifford Yapp 02e76b2ac2 Start working on the Windows side of OpenSceneGraph building.
svn:revision:60179
svn:branch:openscenegraph
svn:account:starseeker
2014-03-24 14:13:55 +00:00
Clifford Yapp 1f58a8c17a Now that it's defined, enable Osg_fb_open. Can now successfully raytrace using the osg dm inside MGED.
svn:revision:60165
svn:branch:openscenegraph
svn:account:starseeker
2014-03-19 20:40:16 +00:00
Clifford Yapp 5bd0d47da1 Add an Osg_fb_open function
svn:revision:60164
svn:branch:openscenegraph
svn:account:starseeker
2014-03-19 20:36:29 +00:00
Clifford Yapp 3bf51c71ee Make mged's dm-osg file a cpp file
svn:revision:60163
svn:branch:openscenegraph
svn:account:starseeker
2014-03-19 20:30:49 +00:00
Clifford Yapp c8bc2b9778 Make mged's dm-osg file a cpp file (preliminary file move commit) 2014-03-19 20:30:49 +00:00
Clifford Yapp 449ba9d0e9 Start adding in Tk window controls.
svn:revision:60158
svn:branch:openscenegraph
svn:account:starseeker
2014-03-19 19:04:08 +00:00
Clifford Yapp 2b0806c8f8 Sync with trunk through revision 60153
svn:revision:60154
svn:branch:openscenegraph
svn:account:starseeker
2014-03-19 13:34:39 +00:00
Clifford Yapp 24f8b9b9d5 Use the toplevel window - actually got a working raytrace, although none of the controls are operational yet.
svn:revision:60119
svn:branch:openscenegraph
svn:account:starseeker
2014-03-11 19:37:33 +00:00
Clifford Yapp 60ef7d2830 Switch out more of the glX calls.
svn:revision:60118
svn:branch:openscenegraph
svn:account:starseeker
2014-03-11 16:14:45 +00:00
Clifford Yapp dbe768fd3b Need Tk before we can do any windowing.
svn:revision:60115
svn:branch:openscenegraph
svn:account:starseeker
2014-03-11 14:18:02 +00:00
Clifford Yapp 8f07b0709a Start trying to figure out the puzzle of the framebuffer windowing. Got a long way to go.
svn:revision:60114
svn:branch:openscenegraph
svn:account:starseeker
2014-03-11 14:08:27 +00:00
Clifford Yapp a3dc872218 Start trying to figure out the puzzle of the framebuffer windowing. Got a long way to go. (preliminary file move commit) 2014-03-11 14:08:27 +00:00
Clifford Yapp 13aff3993f Make sure the include dirs are set.
svn:revision:60113
svn:branch:openscenegraph
svn:account:starseeker
2014-03-10 16:41:27 +00:00
Clifford Yapp e93fd6b1b0 grab trunk ThirdParty update
svn:revision:60112
svn:branch:openscenegraph
svn:account:starseeker
2014-03-10 16:31:33 +00:00
Clifford Yapp 69d073d86a More build tweaking for OSG. Need another feature in the ThirdParty macro - a list of variables to reset for the search. STEPcode will probably need something similar once we actually start looking for system versions...
svn:revision:60110
svn:branch:openscenegraph
svn:account:starseeker
2014-03-10 16:14:12 +00:00
Clifford Yapp 6674908a4c Update ThirdParty macro from trunk, make appropriate tweaks.
svn:revision:60109
svn:branch:openscenegraph
svn:account:starseeker
2014-03-10 15:39:40 +00:00
Clifford Yapp f2c427d6e4 Get local openscenegraph build going. Will need both better handling of the build dir plugin situation and an upgraded ThirdParty macro that allows for version specification. Needs a bit of a rework of top level option handling across the board to be done right.
svn:revision:60106
svn:branch:openscenegraph
svn:account:starseeker
2014-03-10 13:40:01 +00:00
Clifford Yapp 804f5dd8f2 Fudge a way to run the viewer from at least one of the build directories. The right way to do this is probably to have the application pass the appropriate path to filepath at runtime, if the hooks for that exist. (If not, then the right way is to create the hooks.)
svn:revision:60104
svn:branch:openscenegraph
svn:account:starseeker
2014-03-07 23:12:06 +00:00
Clifford Yapp 0dc8ea3087 Whoops - add the viewer app
svn:revision:60103
svn:branch:openscenegraph
svn:account:starseeker
2014-03-07 23:10:42 +00:00
Clifford Yapp ca821a6530 Add a 'minimal subset' build of OpenSceneGraph 3.2.0. The build system has been extensively reworked as a prelude to making it 'play nice' with BRL-CAD's more advanced build system features.
svn:revision:60102
svn:branch:openscenegraph
svn:account:starseeker
2014-03-07 23:07:03 +00:00
Clifford Yapp ce414501d0 Create a branch for more radical testing with openscenegraph.
svn:revision:60101
svn:branch:openscenegraph
svn:account:starseeker
2014-03-07 22:32:20 +00:00
2508 changed files with 52940 additions and 452761 deletions
+2
View File
@@ -0,0 +1,2 @@
/bin
/lib
+1 -11
View File
@@ -703,13 +703,12 @@ Open Source (GSoC)
Huff, Emory
nicknames hknoll
2013 July
ARL Student Hire
U.S. Army Research Laboratory (SEAP)
Engbert, Jonathan
nicknames ejno
2013 July
Open Source
ARL Student Hire / University of Maryland, Baltimore County
Andrew
2013 November
@@ -748,15 +747,6 @@ Roberts, Mitchell
2014 July
ARL Student Hire
Bayes, Matthew
nicknames klinger4077
2014 July
ARL Student Hire / University of Maryland College Park
Mirea, Ștefan-Gabriel
2014 October
Open Source
SPECIAL THANKS
--------------
-22
View File
@@ -15,28 +15,6 @@ on-going issues.
Recent Bugs
-----------
* report that attempting to change units on a read-only file in MGED
will not change the units in the file but changes them in MGED,
resulting in problems with nirt missing geometry it shouldn't miss.
* typing 'comb -f -r assembly_name' shuts down mged with the error:
ERROR: bad pointer 0000000000B4CA50: s/b bu_external(x768dbbd0), was bu_vls(x89333bbb), file ..\..\..\brlcad_src\src\libbu\parse.c, line 2443"
And on the mged command line:
rt_db_cvt_to_external5 expecting non-NULL name parameter
wdb_export((null)): solid export failure
* running "draw -C 0/255/0" in archer dies with a bu_malloc(0) error.
* iges exporter is writing out corrupted output due to spaces after
commas.
* report of mged command history not working with the down arrow key
in 7.25.0 (on Windows, unknown on other platforms). Up arrow works
fine.
* wgl framebuffer is not lingering on windows (regardless of using
wgll or default) when it should
* count_non_union_ops() in g-iges crashes with simple conversion case
* gqa bypasses rt_dirbuild() so it never sets rt_bot_mintie nor uses
+21 -52
View File
@@ -8,7 +8,7 @@ include developer application programming interface (API) calls as
well as user application command-line interface (CLI) and graphical
user interface (GUI) behaviors. Changes are characterized as:
1) those affecting a new interface,
1) changing a new interface,
2) being minimally impacting, or
3) requiring adherence to deprecation policy.
@@ -23,11 +23,10 @@ NEW INTERFACE
-------------
Changes to interfaces that have been recently introduced are often
subject to further change and should not yet be relied upon by
application developers or users until they stabilize. They are
allowed to change from release to release and are not subject to
change policy restrictions until they have been included in at least
TWO releases without any change.
subject to change and should not yet be relied upon by application
developers or users. They may be changed as needed from release to
release and are not subject to change policy restrictions until they
have been included in at least TWO releases without change.
MINIMALLY IMPACTING
@@ -36,21 +35,20 @@ MINIMALLY IMPACTING
If a change to an interface has a suitable and completely equivalent
alternative, the change is deemed to be "minimally impacting" and can
be made during any release. Examples of such changes include renaming
an interface, reordering parameters, adding optional parameters,
adding additional parameters for previously implicit behavior, and
removing unused parameters.
an interface, reordering parameters, adding additional parameters for
previously implicit behavior, and removing unused parameters.
Generally, the impact can usually be considered minimally impacting if
Basically, the impact can usually be considered minimally impacting if
a static regular expression search-and-replace is all that is needed
to update calling code, and no manual intervention is required.
to update calling code, and no change is imposed on the user.
DEPRECATION POLICY
------------------
If a change will intentionally alter, replace, or remove functionality
that has been documented and published in at least TWO releases, it
should mut first be announced as DEPRECATED. Otherwise, changes to
If a change will intentionally change, replace, or remove
functionality that has been documented and published in at least TWO
releases should be first marked as DEPRECATED. Otherwise, changes to
interfaces that have not been publicly announced or are not publicly
documented for at least two releases may be changed without notice.
@@ -117,16 +115,6 @@ and new names should be listed for reference.
7.26
----
include/bn.h
bn_tcl_mat_print, removal of all tcl-specific API functions [deprecated 7.26]
include/raytrace.h
curve_to_tcl_list rt_tcl_parse_ray rt_tcl_pr_cutter
rt_tcl_pr_hit rt_tcl_rt rt_tcl_import_from_path
db_full_path_appendresult tcl_obj_to_int_array
tcl_obj_to_fastf_array tcl_list_to_int_array
tcl_list_to_fastf_array *_tcl_*, removal of all tcl-specific
API functions [deprecated 7.26]
pixcut, pixpaste
copyright cleanup [deprecated 7.26]
librt, fast4-g
@@ -134,6 +122,11 @@ librt, fast4-g
7.24
----
include/bu
hist.h bu_hist bu_hist_t BU_HIST_NULL BU_HIST_INIT_ZERO [deprecated 7.24]
BU_HIST_IS_INITIALIZED BU_HIST_TALLY BU_HIST_TALLY_MULTIPLE [deprecated 7.24]
bu_hist_free bu_hist_init bu_hist_range bu_hist_pr [deprecated 7.24]
functions, macros, and header will be renamed for clarity [deprecated 7.24]
fbed, pp-fb
removes termcap use, no known users [deprecated 7.24]
include/raytrace librt
@@ -273,8 +266,6 @@ now no longer a part of BRL-CAD.
7.26.0
------
include/dg.h
implementation detail no longer being exposed, use libged [deprecated 7.22]
autogen.sh && configure
GNU Autotools build system -> CMake build system [deprecated 7.20]
Dunn camera and Canon printer tools
@@ -303,7 +294,6 @@ include/vmath.h
VSCALE_2D -> V2SCALE [deprecated 7.14]
VJOIN1_2D -> V2JOIN1 [deprecated 7.14]
liborle
include/orle.h
remove liborle and the tools using it, fb-orle, orle-fb, orle-pix and
pix-orle [deprecated 7.20]
mged
@@ -982,10 +972,10 @@ s/bu_find_hash_entry/bu_hash_tbl_find/g
s/bu_hash_add_entry/bu_hash_tbl_add/g
s/bu_hash_tbl_pr/bu_hash_tbl_print/g
renamed for better consistency in hash table API and with other libbu API [7.24]
s/dm_applicationfocus\([[:space:]]*\);//g
only useful in older os x versions, users can now do the same thing via XQuartz preferences [7.24]
s/dm_applicationfocus\([[:space:]]\);//g
only useful in older os x versions, users can now do the same thing via XQuartz preferences
s/bu_vls_trunc2/bu_vls_trunc/g
removed duplicitous function in favor of more general version [7.24]
removed duplicitous function in favor of more general version
s/bn_pi/M_PI/g
s/bn_twopi/M_2PI/g
s/bn_halfpi/M_PI_2/g
@@ -997,31 +987,10 @@ s/bn_inv255/(1.0 \/ 255.0)/g
s/bn_degtorad/DEG2RAD/g
s/bn_radtodeg/RAD2DEG/g
s/bn_sin_scale/(BN_SINTABSIZE \/ M_2PI)/g
eliminated a number of libbn globals in favor of existing constants [7.24]
eliminated a number of libbn globals in favor of existing constants
s/(#[[:space:]]*include[[:space:]]+["<])vfont-if\.h/\1bu\/vfont.h/g
s/(#[[:space:]]*include[[:space:]]+["<])cmd\.h/\1bu\/cmd.h/g
s/(#[[:space:]]*include[[:space:]]+["<])hist\.h/\1bu\/hist.h/g
s/(#[[:space:]]*include[[:space:]]+["<])magic\.h/\1bu\/magic.h/g
library-specific public headers moved into a subdir [7.24]
s/([^_])([nh]to[hn][fd])/\1bu_cv_\2/g
ntohf, ntohd, htonf, htond renamed with bu_cv_ prefix [7.24]
7.26
----
s/bu_kill_parallel\([[:space:]]*\);//g
didn't do anything unless called from forked process, use bu_terminate() [7.25]
s/bu_jmpbuf/bu_jmpbuf[0]/g
s/bu_setjmp_valid/bu_setjmp_valid[0]/g
can replace 0 with bu_parallel_id() to get thread-safe jumping [7.25]
s/bu_semaphore_reinit/bu_semaphore_init/g
no longer need to manually reinitialize (or initialize) semaphores [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])fbio\.h/\1bu\/fb.h/g
fbio.h is now part of fb.h [7.25]
s/UNION/'u'/g
s/SUBTRACT/'-'/g
s/INTERSECT/'+'/g
old db.h db4 preprocessor symbols removed, use char or DB_OP_* [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])bselect\.h/\1bsocket.h/g
s/(#[[:space:]]*include[[:space:]]+["<])bin\.h/\1bnetwork.h/g
rename bselect.h and bin.h public headers to be more declaratively named [7.25]
+7 -95
View File
@@ -703,8 +703,6 @@ CONFIG_H_APPEND(BRLCAD "#define BRLCAD_VERSION_MAJOR ${BRLCAD_VERSION_MAJOR}\n")
CONFIG_H_APPEND(BRLCAD "#define BRLCAD_VERSION_MINOR ${BRLCAD_VERSION_MINOR}\n")
CONFIG_H_APPEND(BRLCAD "#define BRLCAD_VERSION_PATCH ${BRLCAD_VERSION_PATCH}\n")
# Let programs know what the executable suffix is on this platform, if any
CONFIG_H_APPEND(BRLCAD "#define EXECUTABLE_SUFFIX \"${CMAKE_EXECUTABLE_SUFFIX}\"\n")
#----------------------------------------------------------------------
# Decide whether to do a 32 or a 64 bit build.
@@ -784,12 +782,6 @@ if(MSVC)
endif(CMAKE_CL_64)
endif(MSVC)
if (APPLE)
if (${CMAKE_WORD_SIZE} MATCHES "32BIT")
set(CMAKE_OSX_ARCHITECTURES "i386" CACHE STRING "Building for i386" FORCE)
endif (${CMAKE_WORD_SIZE} MATCHES "32BIT")
endif (APPLE)
# Based on what we are doing, we may need to constrain our search paths
#
# NOTE: Ideally we would set a matching property for 32 bit paths
@@ -1035,24 +1027,11 @@ endif(NOT Qt5Widgets_FOUND AND BRLCAD_ENABLE_QT)
mark_as_advanced(Qt5Widgets_DIR)
# Enable features requiring OpenSceneGraph
option(BRLCAD_ENABLE_OSG "Enable features requiring OpenSceneGraph" OFF)
option(BRLCAD_ENABLE_OSG "Enable features requiring OpenSceneGraph" ON)
mark_as_advanced(BRLCAD_ENABLE_OSG)
if(BRLCAD_ENABLE_OSG)
if(APPLE AND NOT BRLCAD_ENABLE_AQUA)
set(OSG_WINDOWING_SYSTEM "X11" CACHE STRING "Use X11" FORCE)
endif(APPLE AND NOT BRLCAD_ENABLE_AQUA)
endif(BRLCAD_ENABLE_OSG)
# Enable features requiring OpenCL
option(BRLCAD_ENABLE_OPENCL "Enable features requiring OpenCL" OFF)
mark_as_advanced(BRLCAD_ENABLE_OPENCL)
if(BRLCAD_ENABLE_OPENCL)
find_package(OpenCL)
if(NOT OPENCL_FOUND)
message("OpenCL enablement requested, but OpenCL is not found - disabling")
set(BRLCAD_ENABLE_OPENCL OFF)
endif(NOT OPENCL_FOUND)
endif(BRLCAD_ENABLE_OPENCL)
#if(BRLCAD_ENABLE_OSG)
# find_package(OpenSceneGraph 3.2.0 REQUIRED osgText osgViewer)
#endif(BRLCAD_ENABLE_OSG)
#----------------------------------------------------------------------
# The following are fine-grained options for enabling/disabling compiler
@@ -1230,11 +1209,6 @@ if(BRLCAD_ENABLE_SMP)
CONFIG_H_APPEND(BRLCAD "#define PARALLEL 1\n")
endif(BRLCAD_ENABLE_SMP)
if(BRLCAD_HEADERS_OLD_COMPAT)
add_definitions(-DEXPOSE_FB_HEADER)
add_definitions(-DEXPOSE_DM_HEADER)
endif(BRLCAD_HEADERS_OLD_COMPAT)
#----------------------------------------------------------------------
# Some generators in CMake support generating folders in IDEs for
# organizing build targets. We want to use them if they are there.
@@ -1809,7 +1783,6 @@ BRLCAD_INCLUDE_FILE(sys/cpuset.h HAVE_SYS_CPUSET_H)
BRLCAD_INCLUDE_FILE(sys/file.h HAVE_SYS_FILE_H)
BRLCAD_INCLUDE_FILE(sys/ioctl.h HAVE_SYS_IOCTL_H)
BRLCAD_INCLUDE_FILE(sys/ioctl_compat.h HAVE_SYS_IOCTL_COMPAT_H)
BRLCAD_INCLUDE_FILE(sys/ipc.h HAVE_SYS_IPC_H)
BRLCAD_INCLUDE_FILE(sys/machd.h HAVE_SYS_MACHD_H)
BRLCAD_INCLUDE_FILE(sys/mman.h HAVE_SYS_MMAN_H)
BRLCAD_INCLUDE_FILE(sys/mount.h HAVE_SYS_MOUNT_H)
@@ -1840,6 +1813,7 @@ BRLCAD_INCLUDE_FILE(tinfo.h HAVE_TINFO_H)
BRLCAD_INCLUDE_FILE(ulocks.h HAVE_ULOCKS_H)
BRLCAD_INCLUDE_FILE(unistd.h HAVE_UNISTD_H)
BRLCAD_INCLUDE_FILE(windows.h HAVE_WINDOWS_H) # for QueryPerformanceCounter() on Windows
BRLCAD_INCLUDE_FILE(winsock.h HAVE_WINSOCK_H)
# C++
BRLCAD_INCLUDE_FILE_CXX(istream HAVE_ISTREAM)
@@ -1945,11 +1919,9 @@ BRLCAD_FUNCTION_EXISTS(gethostname HAVE_GETHOSTNAME)
BRLCAD_FUNCTION_EXISTS(getloadavg HAVE_GETLOADAVG)
BRLCAD_FUNCTION_EXISTS(getopt_long HAVE_GETOPT_LONG)
BRLCAD_FUNCTION_EXISTS(getprogname HAVE_GETPROGNAME) # bsd
BRLCAD_FUNCTION_EXISTS(htonll HAVE_HTONLL)
BRLCAD_FUNCTION_EXISTS(lrand48 HAVE_LRAND48)
BRLCAD_FUNCTION_EXISTS(memset HAVE_MEMSET)
BRLCAD_FUNCTION_EXISTS(mkstemp HAVE_MKSTEMP)
BRLCAD_FUNCTION_EXISTS(ntohll HAVE_NTOHLL)
BRLCAD_FUNCTION_EXISTS(pipe HAVE_PIPE)
BRLCAD_FUNCTION_EXISTS(popen HAVE_POPEN)
BRLCAD_FUNCTION_EXISTS(posix_memalign HAVE_POSIX_MEMALIGN) # IEEE Std 1003.1-2001
@@ -1979,22 +1951,6 @@ BRLCAD_FUNCTION_EXISTS(vfork HAVE_VFORK)
BRLCAD_FUNCTION_EXISTS(vsscanf HAVE_VSSCANF)
BRLCAD_FUNCTION_EXISTS(writev HAVE_WRITEV)
# ntohll and htonll maybe harder to spot - do some extra tests
if("${HAVE_NTOHLL}" STREQUAL "")
CHECK_SYMBOL_EXISTS(ntohll "sys/_endian.h" HAVE_NTOHLL_SYS__ENDIAN)
if(HAVE_NTOHLL_SYS__ENDIAN AND CONFIG_H_FILE)
set(HAVE_NTOHLL 1 CACHE INTERNAL "Have function NTOHLL")
CONFIG_H_APPEND(BRLCAD "#cmakedefine HAVE_NTOHLL 1\n")
endif(HAVE_NTOHLL_SYS__ENDIAN AND CONFIG_H_FILE)
endif("${HAVE_NTOHLL}" STREQUAL "")
if("${HAVE_HTONLL}" STREQUAL "")
CHECK_SYMBOL_EXISTS(htonll "sys/_endian.h" HAVE_HTONLL_SYS__ENDIAN)
if(HAVE_HTONLL_SYS__ENDIAN AND CONFIG_H_FILE)
set(HAVE_HTONLL 1 CACHE INTERNAL "Have function HTONLL")
CONFIG_H_APPEND(BRLCAD "#cmakedefine HAVE_HTONLL 1\n")
endif(HAVE_HTONLL_SYS__ENDIAN AND CONFIG_H_FILE)
endif("${HAVE_HTONLL}" STREQUAL "")
# we may compile in strict pedantic mode, but still want access to
# some POSIX functions. test whether some symbols (below) are
# declared in addition to whether they resolve (above).
@@ -2110,42 +2066,6 @@ if(WIN32)
set(asinh 1)
endif(NOT HAVE_ASINH)
CHECK_SYMBOL_EXISTS(isnan "math.h" HAVE_ISNAN)
#If we don't have it, need to define it in config_win
if(NOT HAVE_ISNAN)
set(isnan 1)
endif(NOT HAVE_ISNAN)
CHECK_SYMBOL_EXISTS(isinf "math.h" HAVE_ISINF)
#If we don't have it, need to define it in config_win
if(NOT HAVE_ISINF)
set(isinf 1)
endif(NOT HAVE_ISINF)
CHECK_SYMBOL_EXISTS(rint "math.h" HAVE_RINT)
#If we don't have it, need to define it in config_win
if(NOT HAVE_RINT)
set(rint 1)
endif(NOT HAVE_RINT)
CHECK_SYMBOL_EXISTS(fmax "math.h" HAVE_FMAX)
#If we don't have it, need to define it in config_win
if(NOT HAVE_FMAX)
set(fmax 1)
endif(NOT HAVE_FMAX)
CHECK_SYMBOL_EXISTS(nextafterf "math.h" HAVE_NEXTAFTERF)
#If we don't have it, need to define it in config_win
if(NOT HAVE_NEXTAFTERF)
set(nextafterf 1)
endif(NOT HAVE_NEXTAFTERF)
CHECK_SYMBOL_EXISTS(nextafterl "math.h" HAVE_NEXTAFTERL)
#If we don't have it, need to define it in config_win
if(NOT HAVE_NEXTAFTERL)
set(nextafterl 1)
endif(NOT HAVE_NEXTAFTERL)
BRLCAD_FUNCTION_EXISTS(_fseeki64 HAVE__FSEEKI64)
BRLCAD_FUNCTION_EXISTS(_ftelli64 HAVE__FTELLI64)
@@ -2547,10 +2467,9 @@ if(NOT BRLCAD_IS_SUBBUILD)
endif()
if(NOT ${custtarget} MATCHES "buildtimedelta")
get_target_property(not_in_all ${custtarget} EXCLUDE_FROM_ALL)
get_target_property(not_in_default ${custtarget} EXCLUDE_FROM_DEFAULT_BUILD)
if(NOT not_in_all AND NOT not_in_default)
if(NOT not_in_all)
add_dependencies(buildtimedelta ${custtarget})
endif(NOT not_in_all AND NOT not_in_default)
endif(NOT not_in_all)
endif(NOT ${custtarget} MATCHES "buildtimedelta")
endforeach(custtarget ${CMAKE_CUSTOM_TARGET_LIST})
foreach(externaltarget ${CMAKE_EXTERNAL_TARGET_LIST})
@@ -2685,13 +2604,6 @@ if(NOT BRLCAD_IS_SUBBUILD)
set(CPACK_NSIS_MUI_UNIICON "${CMAKE_SOURCE_DIR}/misc/nsis\\\\uninstall.ico")
set(CPACK_NSIS_DISPLAY_NAME "BRL-CAD")
set(CPACK_NSIS_MODIFY_PATH ON)
if(BRLCAD_ENABLE_WIX)
set(CPACK_GENERATOR ${CPACK_GENERATOR} WIX)
set(CPACK_WIX_LICENSE_RTF ${CMAKE_SOURCE_DIR}/misc/wix/License.rtf)
set(CPACK_WIX_PRODUCT_ICON ${CMAKE_SOURCE_DIR}/misc/wix/brlcad_product.ico)
set(CPACK_WIX_UI_BANNER ${CMAKE_SOURCE_DIR}/misc/wix/brlcad_banner.bmp)
set(CPACK_WIX_UI_DIALOG ${CMAKE_SOURCE_DIR}/misc/wix/brlcad_dialog.bmp)
endif(BRLCAD_ENABLE_WIX)
endif(WIN32)
if(CMAKE_CL_64)
set(CPACK_PACKAGE_FILE_NAME "BRL-CAD_${BRLCAD_VERSION}_x64")
-11
View File
@@ -734,17 +734,6 @@ AUTO.
Aliases: ENABLE_GDIAM
--- BRLCAD_BULLET ---
Option for enabling and disabling compilation of the Bullet Realtime
Physics Simulation Libraries provided with BRL-CAD's source
distribution. Default is AUTO, responsive to the toplevel
BRLCAD_BUNDLED_LIBS option and testing first for a system version
if BRLCAD_BUNDLED_LIBS is also AUTO.
Aliases: ENABLE_BULLET
*** Note - Do not add or edit configuration option descriptions and alias
lists in this file - those entries are auto-generated from information in
-3
View File
@@ -14,9 +14,6 @@ changes made. See document footer for additional details.
--- 2014-XX-XX Release 7.26.XX ---
----------------------------------------------------------------------
* fixed texture mapping crash with bad image dimensions - Ștefan Mirea
* fixed g2asc and asc2g handling of dsp primitive - Cliff Yapp
* rewrote gdiff with improved output & reporting options - Cliff Yapp
* fixed pix-ps -S -W -N output size options being ignored - Carl Moore
* fixed crash exporting mixed mode merged BoT meshes - Sean Morrison
* fixed submodel primitive crash - Cliff Yapp, Sean Morrison
+23 -151
View File
@@ -18,12 +18,26 @@ tasks as they are completed.
THESE TASKS SHOULD HAPPEN BEFORE THE NEXT RELEASE
-------------------------------------------------
* fix iges exporter (spaces after commas)
* windows smp support
* make sure we can run db_dirbuild() multiple times without creating
duplicate entries.
* create a BRL-CAD .g with all possible object types embedded. The
csgbrep command is a good starting point, but only about half of
them.
* fix the bu_semaphore unit test
* fix the bn_poly_sub unit test
* fix the bu_heap_test_1 unit test (seen on ia32 fbsd)
* heap unit test needs to actually compare performance against system
allocation, not just do some work
* re-do the sh/enumerate.sh script for CMake
* sync tgc/rec shot() behavior, sort results for proper normal.
inspect t62 grazing with r653,r735 (tgc on an arb8) looking at ae0,0
and z=1524 (was hit/overlap, now misses).
@@ -32,10 +46,6 @@ THESE TASKS SHOULD HAPPEN BEFORE THE NEXT RELEASE
THESE TASKS SHOULD HAPPEN WITHIN TWO RELEASE ITERATIONS
-------------------------------------------------------
* create a BRL-CAD .g with all possible object types embedded. The
csgbrep command is a good starting point, but only about half of
them.
* bundle primary rays in rt front end into postage stamps, shoot via
rt_shootrays(), modify to pass all rays down through the spatial
partitioning simultaneously
@@ -45,6 +55,10 @@ THESE TASKS SHOULD HAPPEN WITHIN TWO RELEASE ITERATIONS
* closing the graphics window brings down X11 on Mac due to a bad
context. fix or revert recent close window behavior.
* Rework p2t so it doesn't take down the application when a NURBS
tessellation fails - should just abandon the problem input and
continue.
* havoc.g s.nos5g reliably exhibits the grazing edge bug where only
one hit point is being returned. to reproduce:
e s.nos5g ; ae 35 25 ; units mm ; center 26912.4 7089.08 7168.96 ; nirt
@@ -53,81 +67,7 @@ THESE TASKS SHOULD HAPPEN WITHIN TWO RELEASE ITERATIONS
THESE ARE UNSCHEDULED BACKLOG TASKS
-----------------------------------
* establish the Basic Application Runtime (BAR), only consisting of
libbu and libbn, as a stand-alone self-contained project. provide
an API that supports most C/C++ application development and
documents our facilities that help simplify code portability,
performance, and maintainability. the scope is basic application
utility and numerics only. this scope is particularly tailored
towards 3D and scientific application development.
the basic utility routines encapsulate platform-specific constructs
portably. the basic numeric routines provide general math
facilities common to scientific application development with a
particular emphasis on being platform agnostic, high performance,
and validated.
the Apache Portable Runtime (APR) and GIMP Toolkit (GTK) are similar
alternatives (particularly to BAR's basic utility routines) but have
different emphases, scope, and development philosophies.
BAR API design aims to be minimally intrusive on application
developers, not requiring them to be aware of or adapt types or
functions until it provides some clear advantage (e.g., portability,
performance, and/or maintainability).
* object error heuristic. implement a function/command to report how
big of an error a given geometry object has. the intent is to help
prioritize geometry modeling errors based on their spatial impact.
this is particularly relevant for nurbs/brep and nmg geometry where
there may be solidity gaps in the topology that need to be sealed or
dangling faces/surfaces of different sizes. this is meant to be a
relative heuristic applicable across all geometry, not necessary an
exact measure. this may make more sense added as an output option
to glint or as a warning category for a geometry debugger.
* create a joint articulation (manually is good, automatic is better)
for the tin woodsman so he can move his arms, legs, neck, and head.
* create a joint articulation (manually is good, automatic is probably
impossible) for ktank so the turret can spin and the gun barrel may
be raised up/down within a given range.
* make Lighting enabled by default in mged and archer (this is a libdm
issue). currently unable to set/override in .mgedrc either.
* need ability to report the smallest feature in a given hierarchy
(smallest edge?) and/or largest error in a given boundary model
(largest edge gap or distance between two points that should be
coincident).
* geometry compiler. provides different levels of "optimization"
(ways of reducing the geometry complexity with or without
introducing 3D changes. provides different stages of compilation
(e.g., similar to preprocessing, compilation, AST reduction,
optimization, encoding transformation, etc). name ideas: bcg, cg
* geometry debugger. low-level geometry database tool with minimal/no
run-time dependencies on our own libraries. the idea is a tool that
can inspect/repair a potentially corrupted/invalid .g file or help
debug library robustness issues. using headers for identifiers and
codes in the implementation is okay (as are library functions, but
just don't rely on any). name ideas: gdbg, dbadmin, dbtool, dbmaint
* BU_SETJUMP/BU_UNSETJUMP into macros
* convert all calls to BU_SETJUMP/BU_UNSETJUMP into familiar try/catch
logic layout using if/else.
* heap unit test needs to actually compare performance against system
allocation, not just do some work
* make sure we can run db_dirbuild() multiple times without creating
duplicate entries.
* re-do the sh/enumerate.sh script for CMake
* get bu_extern out of bu/parse.h into its own header file.
* See if we can use pkg_conn on Windows instead of Tcl_Channel in MGED
* geometry symbolic links (hard and soft links)
@@ -640,6 +580,9 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
* make nreed's new bot cleanup interface update interactively without
resorting to calls to Tcl_DoOneEvent() down in librt.
* convert all calls to BU_SETJUMP/BU_UNSETJUMP into familiar try/catch
logic layout using if/else.
* bu_cv_optimize() should be using bu_byteorder().
* render annotated images to the OpenDocument format. this is
@@ -1081,7 +1024,6 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
in BRL-CAD (libraries are BSD licensed: http://ngplant.sourceforge.net)
DATABASE MAINTENANCE/ADMINISTRATION
-----------------------------------
@@ -1137,31 +1079,6 @@ comp.r4 ID 5678 material code 5 LOS 75
...
};
* evaluate performance of using an SQL/XML store for BRL-CAD geometry,
particularly as it pertains to rt_dirbuild() run times on large
models and db_lookup() times.
* multiple-representation geometry. support storing different
"versions" of a given combination node, as selectable subtrees where
one selectable subtree is always marked active/selected. the
selectable subtrees could generally be entirely different
configurations (e.g., different poses) or different geometry
structure (e.g., a blast, signature, or lethality version of a given
model). These could be implemented as a modification to the union
tree and exposed to the user as a parametric selection on a comb.
Something perhaps like this:
union tree {
...
struct tree_representation {
uint32_t magic;
int tr_op;
const char *tr_name;
union tree *tr_subtree;
} tr_r;
...
};
LIBGED
------
@@ -1495,51 +1412,6 @@ NEW OBJECTS
spline := degree, control points, knot values
text := string, insertion point, size, style, alignment
* procedural geometry objects. database objects that are described at
run-time by a scripted definition. at core, this is a means to
define geometry via outboard descriptions that conform with a
particular syntax (e.g., tcl or python).
minimally, an object will need to define what parameters are
required, what parameters are optional, and what default values will
be used. the object will also need to provide a procedural
definition (e.g., a function or set of functions/objects) that
receives parameter values in order to describe geometry on-demand.
similar to shader, material, and other object constructs, it'll
likely be desirable to support embedding of the procedural
definition within a .g file as well as the ability to reference an
external file that may be more conveniently edited.
care will need to be taken to avoid bad behavior when presented with
a malformed procedure (e.g., an infinite loop, fork bomb, syntax
error, thrashing condition, etc).
* spheroid (quadratic) - special performance case of ell
* conical edge (cubic) - unsure of this one's practical utility except
as a means to construct a pinched tgc (unioning two halves).
* apple (quartic) - this is basically a continuation of torus where
the ID > OD/2.
* cushion (quartic) - bowl shape, related to elliptical torus with
filled interior.
* eight/piriform (quartic) - a conic/ellipsoid blending shape.
* goursat/tanglecube/tooth (quartic) - related to superellipsoid
surface, provides corner/edge blending and rounding shapes.
* lemon (quartic) - elliptical nose cap (requested shape) shape.
* box-spline blend - blending object that is defined by an arb8
volume, blending any entities within that volume that intersect
* lipschitz blend - means to procedurally blend surface edges based on
a blend function and sphere tracing. see "Combining CSG modeling
with soft blending using Lipschitz-based implicit surfaces".
WINDOWS
-------
+5 -4
View File
@@ -31,12 +31,13 @@
#include <stdlib.h>
#include <string.h>
#ifdef HAVE_UNISTD_H
# include <unistd.h>
#endif
#include "bio.h"
#include "bu/getopt.h"
#include "bu/log.h"
#include "bu/file.h"
#include "bu/str.h"
#include "bu.h"
/* exit codes for argument processing errors */
#define OPTS_ERROR 127
Vendored
-4
View File
@@ -202,10 +202,6 @@ do
shift;;
--disable-gdiam) options="$options -DBRLCAD_GDIAM=SYSTEM";
shift;;
--enable-bullet) options="$options -DBRLCAD_BULLET=BUNDLED";
shift;;
--disable-bullet) options="$options -DBRLCAD_BULLET=SYSTEM";
shift;;
--prefix=*) inputstr=$1;
options="$options -DCMAKE_INSTALL_PREFIX=${inputstr#--prefix=}";
shift;;
+8 -10
View File
@@ -275,14 +275,12 @@ if ($physicalFile) {
debug("END http request");
?>
<!--
Local Variables:
tab-width: 8
mode: php
c-basic-offset: 4
indent-tabs-mode: t
End:
ex: shiftwidth=4 tabstop=8
-->
# Local Variables: ***
# mode: C ***
# tab-width: 8 ***
# c-basic-offset: 2 ***
# indent-tabs-mode: t ***
# End: ***
# ex: shiftwidth=2 tabstop=8
?>
-14
View File
@@ -640,20 +640,6 @@
timestamp = {2008.02.05}
}
@PROCEEDING{doi:10.1117/12.960423,
author = {Jones, J. and Gonda, T.},
title = {A Thermal Model Preprocessor For Graphics And Material Database Generation},
journal = {Proc. SPIE},
volume = {1098},
number = {},
pages = {42-54},
abstract = {The process of developing a physical description of a target for thermal models is a time consuming and tedious task. The problem is one of data collection, data manipulation, and data storage. Information on targets can come from many sources and therefore could be in any form (2-D drawings, 3-D wireframe or solid model representations, etc.). TACOM has developed a preprocessor that decreases the time involved in creating a faceted target representation. This program allows the user to create the graphics for the vehicle and to assign the material properties to the graphics. The vehicle description file is then automatically generated by the preprocessor. By containing all the information in one database, the modeling process is made more accurate and data tracing can be done easily. A bridge to convert other graphics packages (such as BRL-CAD) to a faceted representation is being developed. When the bridge is finished, this preprocessor will be used to manipulate the converted data.},
year = {1989},
doi = {10.1117/12.960423},
URL = { http://dx.doi.org/10.1117/12.960423},
eprint = {}
}
@INCOLLECTION{Deitz90b,
author = {Deitz, Paul H.},
title = {High-Resolution, Item-Level Weapons Modeling},
-7
View File
@@ -85,13 +85,6 @@ non-parallel build will still succeed. Another workaround is to build
just subdirectories (e.g. src/other, doc, etc.) individually and then
do a toplevel make in non-parallel mode to finalize the build.
OpenSceneGraph and OSX
----------------------
For 32bit OSX builds of an X11+OpenSceneGraph BRL-CAD:
cmake .. -DBRLCAD_BUNDLED_LIBS=BUNDLED -DBRLCAD_ENABLE_OSG=ON
-DBRLCAD_REGEX=SYSTEM -DBRLCAD_WORD_SIZE=32BIT -DOSG_WINDOWING_SYSTEM=X11
Tips
----
@@ -36,7 +36,6 @@
</l:l10n>
</l:i18n>
<xsl:output method="html" encoding="UTF-8" />
<!-- ==================================================================== -->
<!-- this is a modified header nav template from html/chunk-common.xsl version 1.76.1 -->
@@ -36,7 +36,6 @@
</l:l10n>
</l:i18n>
<xsl:output method="html" encoding="UTF-8" />
<!-- ==================================================================== -->
<!-- this is a modified header nav template from html/chunk-common.xsl version 1.76.1 -->
@@ -36,7 +36,6 @@
</l:l10n>
</l:i18n>
<xsl:output method="html" encoding="UTF-8" />
<!-- ==================================================================== -->
<!-- this is a modified header nav template from html/chunk-common.xsl version 1.76.1 -->
@@ -36,7 +36,6 @@
</l:l10n>
</l:i18n>
<xsl:output method="html" encoding="UTF-8" />
<!-- ==================================================================== -->
<!-- this is a modified header nav template from html/chunk-common.xsl version 1.76.1 -->
@@ -36,7 +36,6 @@
</l:l10n>
</l:i18n>
<xsl:output method="html" encoding="UTF-8" />
<!-- ==================================================================== -->
<!-- this is a modified header nav template from html/chunk-common.xsl version 1.76.1 -->
@@ -36,7 +36,6 @@
</l:l10n>
</l:i18n>
<xsl:output method="html" encoding="UTF-8" />
<!-- ==================================================================== -->
<!-- this is a modified header nav template from html/chunk-common.xsl version 1.76.1 -->
@@ -62,6 +62,7 @@ set(docbook_man1_EN
fb-bw.xml
fb-cmap.xml
fb-fb.xml
fb-orle.xml
fb-pix.xml
fb-png.xml
fb-rle.xml
@@ -126,12 +127,15 @@ set(docbook_man1_EN
nmg-bot.xml
nmg-rib.xml
obj-g.xml
orle-fb.xml
orle-pix.xml
patch-g.xml
pictx.xml
pix-alias.xml
pix-bw.xml
pix-bw3.xml
pix-fb.xml
pix-orle.xml
pix-png.xml
pix-ppm.xml
pix-ps.xml
+10 -10
View File
@@ -32,28 +32,28 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>anim_script</command>
<para><emphasis remap='I'>Anim_script</emphasis>
is designed to produce an animation script for the
animation of the virtual camera or one
<emphasis remap='I'>brlcad</emphasis>
object at a time. It is
complementary to
<command>tabsub</command>
<emphasis remap='I'>tabsub</emphasis>
in that it performs a similar
function, but with a different philosophy.</para>
<para>Both
<command>anim_script</command>
and
<command>tabsub</command>
<emphasis remap='I'>tabsub</emphasis>
use one row of an animation table to
produce one frame of an animation script. With
<command>tabsub</command>,
<emphasis remap='I'>tabsub,</emphasis>
the user supplies
a template file which controls the form of the animation frames. This
allows the maximum user control, but also requires a good understanding
of the script format. With
<command>anim_script</command>,
<emphasis remap='I'>anim_script,</emphasis>
the user supplies all the necessary
information on the command line. The range of possible output scripts is
limited, but the user does not have to deal directly with the details.
@@ -69,7 +69,7 @@ animated, as it will appear in the output script. For example, if
"hatch1"
is a member of "turret" which is a member of "tank" which is one of the
objects specified on the command line of the call to
<command>rt</command>,
<emphasis remap='I'>rt,</emphasis>
then the objectname "tank/turret/hatch1" or simply "turret/hatch1" would be used to
animate the hatch. The tank itself would be referred to by the name,
"/tank". Note that top-level objects should be preceded by a slash.
@@ -130,16 +130,16 @@ representing no orientation change is (0,0,0,1).</para>
<para>Permuted orientation. This option indicates that transformations defined by
the quaternions should be applied to an object which has first been placed
in
<command>rt</command>'s
<emphasis remap='I'>rt</emphasis>'s
default eye orientation. Thus, the identity quaternion represents yawing the
object 90 degrees to the left and then pitching it 90 degrees downward.
The quaternions produced by
<command>mged</command>'s
<emphasis remap='I'>mged</emphasis>'s
saveview command and used by
<command>rt</command>'s
<emphasis remap='I'>rt</emphasis>'s
orientation command
are quaternions of this type. See
<command>anim_orient</command>
<emphasis remap='I'>anim_orient</emphasis>
for more information.</para>
</listitem>
</varlistentry>
+5 -5
View File
@@ -29,13 +29,13 @@
<para>Note:
<command>anim_sort</command>
has been preempted in release 5.0 by
<command>scriptsort</command>,
<emphasis remap='I'>scriptsort</emphasis>,
which sorts scripts much faster.</para>
<para><command>anim_sort</command>
<para><emphasis remap='I'>Anim_sort</emphasis>
allows the user to combine several animation scripts
into a single script suitable for input to
<command>rt</command>.
<emphasis remap='I'>rt</emphasis>.
A convenient way to
prepare a complicated animation script is to develop each part
separately and then use
@@ -68,13 +68,13 @@ output.</para>
<para>Each of the input files to be concatenated is expected to be a
viable
<command>rt</command>
<emphasis remap='I'>rt</emphasis>
animation script, containing a series of frames of the
following form:</para>
<literallayout remap='.nf'>
start framenumber;
any number of semi-colon terminated commands for <command>rt</command>;
any number of semi-colon terminated commands for rt;
end;
any number of post-raytracing commands
</literallayout> <!-- .fi -->
+1 -1
View File
@@ -43,7 +43,7 @@ calculated speed of the object. Various options allow the user to
control the assumptions on the object's initial and final speeds, and the
form of the output.</para>
<para><command>anim_time</command>
<para><emphasis remap='I'>Anim_time</emphasis>
is intended to be used in situations where the user knows what key points
an object should pass through and how long the entire motion should take,
but doesn't care exactly when the object
+16 -16
View File
@@ -38,8 +38,8 @@ track is linear between the wheels. The exception is that between the
first and last wheels, any extra track length is taken up in a hanging
catenary arc.</para>
<para><command>anim_track</command> requires two input files. The first, referred to above as
<emphasis remap='I'>wheelfile</emphasis>,
<para>anim_track requires two input files. The first, referred to above as
<emphasis remap='B'>wheelfile</emphasis>,
is a table which
defines the initial track geometry by describing the wheels around which
the track is to be wrapped. The first three columns of the table give
@@ -58,7 +58,7 @@ The track is always confined to a plane which has no left to right
variation; that is, the wheels can be in front of, behind, above, and
below each other, but may not be to the left or right of each other. If
the wheel positions specified in
<emphasis remap='I'>wheelfile</emphasis>
<emphasis remap='B'>wheelfile</emphasis>
do not lie in such a plane, then the first wheel defines the plane into
which all of the other wheels are projected.</para>
@@ -67,9 +67,9 @@ The track segments between wheels are always linear, except for the
segment between the first and last wheels. If there is any extra track
length, it is taken up in a catenary arc which hangs down between the
first and last wheels. Thus if the first wheel in
<emphasis remap='I'>wheelfile</emphasis>
<emphasis remap='B'>wheelfile</emphasis>
should be the top front wheel of the vehicle, and the last wheel in
<emphasis remap='I'>wheelfile</emphasis>
<emphasis remap='B'>wheelfile</emphasis>
should be the top back wheel of the vehicle. Depending on the track
length mode specified with the
<option>-l</option>
@@ -78,7 +78,7 @@ option, the catenary segment may or may not appear.</para>
<para>The second input file required by
<command>anim_track</command>,
referred to above as
<emphasis remap='I'>in.table</emphasis>,
<emphasis remap='B'>in.table</emphasis>,
describes the state of the track in every frame of the animation. The
format of this second file can vary greatly according to the command-line
options. The first column of the file is ignored, but is expected to
@@ -158,7 +158,7 @@ command for each of the track pads.</para>
<para>Animate the track wheels. This option takes one argument: a
slash-separated path to the wheel basename. The number of wheels is
obtained from the number of lines in the
<emphasis remap='I'>wheelfile</emphasis>.
<emphasis remap='B'>wheelfile</emphasis>.
If there is, for example, a combination named "rwheels" containing 4
wheels named wheel_0, wheel_1, wheel_2, and wheel_3, then the correct
argument is:</para>
@@ -205,14 +205,14 @@ roll. The second column through the seventh columns of the
should contain the position and orientation of the vehicle in every
frame. The distance that the track should be rolled around the wheels is
automatically calculated in every frame. If
<command>anim_script</command>
<emphasis remap='I'>anim_script</emphasis>
is being used with the same table to create the animation script for the
vehicle itself, the
<option>-b</option>
and
<option>-d</option>
options to
<command>anim_script</command>
<emphasis remap='I'>anim_script</emphasis>
and
<command>anim_track</command>
should be the same.</para>
@@ -229,14 +229,14 @@ that the track should be rolled around the wheels is automatically
calculated in every frame, based on the assumption that the vehicle is
always steered to face the direction of motion.
If
<command>anim_script</command>
<emphasis remap='I'>anim_script</emphasis>
is being used with the same table to create the animation script for the
vehicle itself, the
<option>-b</option>
and
<option>-d</option>
options to
<command>anim_script</command>
<emphasis remap='I'>anim_script</emphasis>
and
<command>anim_track</command>
should be the same.</para>
@@ -348,7 +348,7 @@ animation script. The default is zero.</para>
<listitem>
<para>Specify the common radius of all the wheels. In this case, the fourth column
should be omitted from the
<emphasis remap='I'>wheelfile</emphasis>.</para>
<emphasis remap='B'>wheelfile</emphasis>.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -369,7 +369,7 @@ frame of an animation, the specified frame number would be zero.</para>
<para>Specify the animation matrix command to apply to the pads. The default
value is "rarc", meaning that the matrix between the pad and its parent
is replaced by a new matrix. See the
<command>anim_script</command>
<emphasis remap='I'>anim_script</emphasis>
man page for more information.</para>
</listitem>
</varlistentry>
@@ -379,7 +379,7 @@ man page for more information.</para>
<para>Specify the animation matrix command to apply to the wheels. The default
value is "lmul", meaning that the new matrix is multiplied onto the left
of the old matrix between the pad and its parent combination. See the
<command>anim_script</command>
<emphasis remap='I'>anim_script</emphasis>
man page for more information.</para>
</listitem>
@@ -396,7 +396,7 @@ you obtain the position of the center of
the tank and its orientation at each time. You also need to obtain the
position of the each wheel relative to the vehicle center at each time.
All of this information is placed in
<emphasis remap='I'>in.table</emphasis>
<emphasis remap='B'>in.table</emphasis>
. The model of the tank is stored in
model.g as a combination named "tank". Its centroid is at the
point (0,0,1005) and it faces the y-axis. An animation script for the
@@ -422,7 +422,7 @@ long and 5mm thick. Ninety-six instances of the pad are created, with names "rpa
through "rpad.95", and grouped together in a combination called "rtrack".</para>
<para>Now, a file called
<emphasis remap='I'>rwheelfile</emphasis>
<emphasis remap='B'>rwheelfile</emphasis>
is created, describing the positions and radii of the four wheels in the
right track:</para>
+5 -5
View File
@@ -59,7 +59,7 @@ of the wheelbase (from the front axle to the rear axle).</para>
<varlistentry>
<term><option>-a#</option></term>
<listitem>
<para><command>anim_turn</command>
<para><emphasis remap='I'>Track</emphasis>
assumes that the truck should initially be oriented
along the line defined by the first two positions in the input table.
Otherwise, the desired initial yaw of the truck can be specified with the
@@ -71,12 +71,12 @@ option.</para>
<term><option>-r#</option></term>
<listitem>
<para>Specify the radii of the front wheels. If this option is selected,
<command>anim_turn</command>
<emphasis remap='I'>track</emphasis>
will create an animation script to animate the front wheels. The output
table would contain four columns: time, swivel-angle, roll, and a zero
channel. These represent the orientation of the front wheels, in terms
of yaw, pitch, and roll, and the table can be piped directly to
<command>anim_script</command>.</para>
<emphasis remap='I'>anim_script</emphasis>.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -85,7 +85,7 @@ of yaw, pitch, and roll, and the table can be piped directly to
<para>Specify a factor to be used to animate a steering wheel. If this option
is selected, the output table will contain four columns: time, swivel,
and two zero columns. This table can be used directly by
<command>anim_script</command>
<emphasis remap='I'>anim_script</emphasis>
to make an animation script for a steering wheel. The argument to the
option should be the factor by which to exaggerate the swiveling of
the wheels. For
@@ -106,7 +106,7 @@ frames per second is being created, the user should give an input table
with a high number of input rows and reduce the output with the
<option>-p#</option>
option. For example, if
<emphasis remap='I'>in.table</emphasis>
<emphasis remap='B'>in.table</emphasis>
contains 30 rows for each second of the
animation, then the command</para>
+4 -4
View File
@@ -25,16 +25,16 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>ap-pix</command>
<para><emphasis remap='I'>Ap-pix</emphasis>
converts an
Applicon
<emphasis remap='I'>Applicon</emphasis>
drum plotter image file into a
<citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry>
file.</para>
<para>The
Applicon
file is assumed to consist of a number lines each 3456 bits long; the
<emphasis remap='I'>Applicon</emphasis>
file is assumed to consist of a number lines each 3456 bits long, the
resulting
<emphasis remap='I'>pix</emphasis>
file thus has scanlines of 3456 pixels.</para>
+4 -6
View File
@@ -23,7 +23,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>asc-nmg</command>
<para><emphasis remap='I'>asc-nmg</emphasis>
converts the specified
<emphasis remap='I'>ascii_file</emphasis>
(not a .asc geometry database) to a binary BRL-CAD
@@ -88,15 +88,13 @@ l
v5 1 -1 1
</literallayout> <!-- .fi -->
<para>the command:</para>
<para>Then, the command:</para>
<synopsis>
$ asc-nmg <emphasis remap='I'>ascii_file sample.g</emphasis>
$ <emphasis remap='I'>asc-nmg ascii_file sample.g</emphasis>
</synopsis>
<para>will produce an 'L'-shaped NMG solid to the
<emphasis remap='I'>sample.g</emphasis>
database file.</para>
<para>will produce an 'L'-shaped NMG solid to the sample.g database file.</para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
+1 -1
View File
@@ -26,7 +26,7 @@
and converts it to
<citerefentry><refentrytitle>plot3</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format.
<command>asc-plot3</command>
<emphasis remap='I'>Asc-plot3</emphasis>
reads from standard input and writes to standard output
if file names are not supplied.</para>
+6 -6
View File
@@ -24,9 +24,9 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><emphasis remap='B'><command>asc2g</command></emphasis> is a utility provided by BRL-CAD used to convert <emphasis remap='I'><command>mged(1)</command></emphasis> geometry databases in ASCII form outputted by <emphasis remap='I'><command>g2asc(1)</command></emphasis> to the new binary format. The utility will always create the new binary format, but it will accept either of the two ASCII formats (see <emphasis remap='B'>HISTORY</emphasis>).</para>
<para><emphasis remap='B'><command>asc2g</command></emphasis> is a utility provided by BRL-CAD used to convert <emphasis remap='I'><command>mged(1)</command></emphasis> geometry databases in ASCII form outputted by <emphasis remap='I'><command>g2asc(1)</command></emphasis> to the new binary format. The utility will always create the new binary format, but it will accept either of the two ASCII formats (See <emphasis remap='B'>HISTORY</emphasis>).</para>
<para>The local machine binary representation of a mged database is inherently non-portable. <emphasis remap='I'><command>asc2g</command></emphasis> and its converse, <emphasis remap='I'><command>g2asc</command></emphasis> , are simple filters which convert between the binary form and an ASCII representation.</para>
<para>The local machine binary representation of a mged database is inherently non-portable. <emphasis remap='I'><command>asc2g</command></emphasis>, along with its converse <emphasis remap='I'><command>g2asc</command></emphasis> are simple filters which convert between the binary form and an ASCII representation.</para>
<para>This was traditionally performed so the files could be transferred to another machine in a portable format. Although no longer necessary for the current binary geometry database files that are created by mged ("v5" format), the conversion process is still necessary if manipulating older ("v4" format) geometry database files.</para>
@@ -36,17 +36,17 @@
<refsect1 xml:id='examples'><title>EXAMPLE</title>
<para><emphasis remap='B'><command>g2asc</command></emphasis> <emphasis remap='I'>file.g file.asc</emphasis></para>
<blockquote remap='RS'>
<para>On the local machine, convert the mged databases to ASCII using <emphasis remap='I'><command>g2asc</command></emphasis> .
<para>On the local machine, convert the mged databases to ASCII using <emphasis remap='I'><command>g2asc</command></emphasis>
</para></blockquote> <!-- remap='RE' -->
<para>scp <emphasis remap='I'>file.asc</emphasis> remote:<emphasis remap='I'>file.asc</emphasis></para>
<blockquote remap='RS'>
<para>Transfer the converted databases to the remote machine.
<para>Transfer the converted databases to the remote machine
</para></blockquote> <!-- remap='RE' -->
<para>ssh remote "<emphasis remap='B'><command>asc2g</command></emphasis> <emphasis remap='I'>file.asc file.g</emphasis>"</para>
<blockquote remap='RS'>
<para>On the remote machine, convert the files back to the binary representation for that machine using <emphasis remap='I'><command>asc2g</command></emphasis> .
<para>On the remote machine, convert the files back to the binary representation for that machine using <emphasis remap='I'><command>asc2g</command></emphasis>
</para></blockquote> <!-- remap='RE' -->
</refsect1>
@@ -105,6 +105,6 @@
<refsect1 xml:id='disclaimer'><title>DISCLAIMER</title>
<para>The ASCII representation of BRL-CAD geometry databases is not a fixed format and is allowed to change without deprecation notice. In general, this will not occur any more frequently than the binary geometry database format changes, though both are open specifications. Regardless, the ASCII representation is subject to change without notice and should not be relied upon by external codes. (See <emphasis remap='B'>HISTORY</emphasis>.)</para>
<para>The ASCII representation of BRL-CAD geometry databases is not a fixed format and is allowed to change without deprecation notice. In general, this will not occur any more frequently than the binary geometry database format changes, though both are open specifications. Regardless, the ASCII representation is subject to change without notice and should not be relied upon by external codes. (See <emphasis remap='B'>HISTORY</emphasis>).</para>
</refsect1>
</refentry>
+3 -3
View File
@@ -23,7 +23,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>azel</command>
<para><emphasis remap='I'>Azel</emphasis>
converts between right-handed Cartesian coordinate systems,
an application-geometry system
<emphasis remap='I'>x</emphasis>, <emphasis remap='I'>y</emphasis>, <emphasis remap='I'>z</emphasis>
@@ -76,9 +76,9 @@ Default is 0.</para>
<term><option>-c</option><replaceable> celsiz</replaceable></term>
<listitem>
<para>Specifies a cell size of
<emphasis remap='I'>celsiz</emphasis>.
<emphasis remap='I'>celsiz.</emphasis>
Output vectors are scalar multiplied by
1/<emphasis remap='I'>celsiz</emphasis>.
1/<emphasis remap='I'>celsiz.</emphasis>
Default is 1.
Useful with the
<option>-r</option>
+1 -1
View File
@@ -23,7 +23,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bary</command>
<para><emphasis remap='I'>Bary</emphasis>
computes weighted sums of a set of sites in Euclidean 3-space,
writing them on the standard output.
The site weights are read from
+1 -1
View File
@@ -76,7 +76,7 @@ the unit type specified).</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ bot_dump -o <emphasis remap='I'>some_bot_dump.dxf</emphasis> -t <emphasis remap='I'>dxf sample.g some_bot</emphasis>
$ <emphasis remap='I'>bot_dump -o some_bot_dump.dxf -t dxf sample.g some_bot</emphasis>
</synopsis>
</refsect1>
+1 -1
View File
@@ -66,7 +66,7 @@ only be useful for developers.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ bot_shell-vtk -o <emphasis remap='I'>output.vtk sample.g the_exterior</emphasis>
$ <emphasis remap='I'>bot_shell-vtk -o output.vtk sample.g the_exterior</emphasis>
</synopsis>
</refsect1>
+3 -3
View File
@@ -22,10 +22,10 @@
<refsect1 xml:id="description">
<title>DESCRIPTION</title>
<para><command>brep_simple</command> constructs a simple b-rep twisted cube directly using the
openNURBS API. The constructed twisted cube is written to a geometry database
(brep_simple.g) using the wdb interface. The cube is constructed by first
openNURBS API. The constructed twisted cube is written to a geometry database,
<emphasis remap="I">brep_simple.g</emphasis> using the wdb interface. The cube is constructed by first
defining and creating the vertices, then the twisted edges (using trimming
curves), and finally the faces to get a final topology like the following:</para>
curves), and finally the faces to get a final topology like the following --</para>
<literallayout remap=".nf">
H-------e6-------G
+2 -2
View File
@@ -78,11 +78,11 @@ creating a program that refers to <emphasis remap='I'>BRL-CAD</emphasis> headers
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>libbu</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>libbn</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>librt</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>libwdb</refentrytitle><manvolnum>3</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>libbu</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>libbn</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>librt</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>libwdb</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='bugs'><title>BUGS</title>
<para>No bugs known for <command>brlcad-config</command> .</para>
<para>No bugs known for <command>brlcad-config</command>.</para>
</refsect1>
<refsect1 xml:id='author'><title>AUTHOR</title>
+4 -4
View File
@@ -26,9 +26,9 @@ combinatorial solid geometry (CSG)
models.
See
<citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
and see also
and
<emphasis remap='I'>Understanding the Preparation and Analysis of Solid Models</emphasis>
by Michael John Muuss (enclosed, in the "paper" directory).</para>
by Michael John Muuss (enclosed, in the "paper") directory.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -263,7 +263,7 @@ When a local display device is being specified, the
<emphasis remap='I'>hostname</emphasis>
should not be specified, for performance reasons; just the
special string
<emphasis remap='I'>device_name</emphasis>
<emphasis remap='I'>Device_name</emphasis>
is used to select a particular type of framebuffer.
<emphasis remap='I'>Num</emphasis>
is type dependent and can either mean a display number or select
@@ -273,7 +273,7 @@ disk file via the remote interface.</para>
<para>If
<envar>FB_FILE</envar>
is not set, the default for your system will be used.</para>
is not set, the default for you system will be used.</para>
<para>The use of
<filename>/dev/</filename>
+3 -3
View File
@@ -22,7 +22,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>buffer</command>
<para><emphasis remap='I'>Buffer</emphasis>
is intended to be use as part of a complex pipeline.
It serves somewhat the same purpose as the Prolog "cut" operator.
Data from stdin is read and buffered until EOF is detected, and then
@@ -35,9 +35,9 @@ This can also be useful when processing data from and to the
same framebuffer with a pipeline, without interfering.</para>
</refsect1>
<refsect1 xml:id='examples'><title>EXAMPLE</title>
<refsect1 xml:id='examples'><title>EXAMPLES</title>
<literallayout remap='.nf'>
(munch | crunch | buffer | grind | package)
munch | crunch | buffer | grind | package
fb-pix | pixfilter -flo | buffer | pix-fb
</literallayout> <!-- .fi -->
+10 -9
View File
@@ -30,7 +30,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bw-imp</command>
<para><emphasis remap='I'>Bw-imp</emphasis>
converts an 8-bit monochrome
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format
@@ -76,7 +76,7 @@ produce the image roughly centered on the page.</para>
</refsect1>
<refsect1 xml:id='caveats'><title>CAVEATS</title>
<para><command>bw-imp</command>
<para><emphasis remap='I'>Bw-imp</emphasis>
will take several CPU-minutes (on a VAX 780) to convert a single
<emphasis remap='I'>file</emphasis>.</para>
</refsect1>
@@ -84,11 +84,11 @@ will take several CPU-minutes (on a VAX 780) to convert a single
<refsect1 xml:id='examples'><title>EXAMPLES</title>
<para>The following invocations are fairly typical:</para>
<literallayout remap='RS'>
pix-bw -ntsc <emphasis remap='I'>image.pix</emphasis> | bw-imp | qpr -qi300 &amp;
<emphasis remap='I'>pix-bw -ntsc image.pix | bw-imp | qpr -qi300</emphasis> &amp;
</literallayout> <!-- remap='RE' -->
<literallayout remap='RS'>
rle-pix <emphasis remap='I'>image.rle</emphasis> | pix-bw -ntsc | bw-imp | qpr -qi300 &amp;
<emphasis remap='I'>rle-pix image.rle | pix-bw -ntsc | bw-imp | qpr -qi300</emphasis> &amp;
</literallayout> <!-- remap='RE' -->
<para>The X and Y options in the bw-imp command below are to approximately
@@ -98,17 +98,18 @@ As of release 4.0 the default margins on an output page resulting from
a bw-imp usage are smaller. This allows a larger image to be printed
on one page.</para>
<literallayout remap='RS'>
rle-pix <emphasis remap='I'>image.rle</emphasis> | pix-bw -ntsc | bw-imp -X 200 -Y 800 | ipr -L impress -q i300
<emphasis remap='I'>rle-pix image.rle | pix-bw -ntsc | bw-imp -X 200 -Y 800 | ipr -L impress -q i300 </emphasis>
</literallayout> <!-- remap='RE' -->
<para>To threshold and invert the black/white sense of a pix file, use:</para>
<literallayout remap='RS'>
bwmod -m -8 -a 255 <emphasis remap='I'>image.pix</emphasis> | pix-bw | bw-imp -t1 | ttcp -t -p35 <emphasis remap='I'>printhost</emphasis>
</literallayout><!-- remap='RE' -->
<blockquote remap='RS'>
<para><emphasis remap='I'>bwmod -m -8 -a 255 image.pix | pix-bw | bw-imp -t1 |
ttcp -t -p35 printhost </emphasis>
</para></blockquote> <!-- remap='RE' -->
<para>To use the halftone package:</para>
<literallayout remap='RS'>
pix-bw -ntsc <emphasis remap='I'>image.pix</emphasis> | halftone | bw-imp | qpr -qi300 &amp;
<emphasis remap='I'>pix-bw -ntsc image.pix | halftone | bw-imp | qpr -qi300</emphasis> &amp;
</literallayout> <!-- remap='RE' -->
</refsect1>
+2 -2
View File
@@ -31,7 +31,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bw-pix</command>
<para><emphasis remap='I'>Bw-pix</emphasis>
converts a black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format
@@ -47,7 +47,7 @@ is given.</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix-bw</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix-bw3</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix-bw</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix-bw3</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
+5 -5
View File
@@ -34,7 +34,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bw-ps</command>
<para><emphasis remap='I'>Bw-ps</emphasis>
will take a black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file of given dimensions and produce a Postscript file
@@ -68,20 +68,20 @@ selects landscape mode, i.e. rotates the output image by ninety degrees.</para>
</refsect1>
<refsect1 xml:id='examples'><title>EXAMPLES</title>
<para>bw-ps -c <emphasis remap="I">image.bw</emphasis> &gt; <emphasis remap="I">image.ps</emphasis></para>
<para>bw-ps -c image.bw &gt; image.ps</para>
<para>Produces a 6.75 inch PostScript file from an 512 x 512 input image
<para>Produces a 6.75 inch PostScript file from an 512 x512 input image
and centers it on an 8.5 x 11 inch page.</para>
<para>bw-ps -e -w 1024 -n 768 <emphasis remap="I">image.bw</emphasis> &gt; <emphasis remap="I">image.ps</emphasis></para>
<para>bw-ps -e -w 1024 -n 768 image.bw &gt; image.ps</para>
<para>Takes the file image.bw which has the dimensions of 1024 pixels wide
by 768 pixels high, and produces an Encapsulated Postscript version
of it.</para>
<para>bw-ps -L -c -S 5.2 &lt; <emphasis remap="I">image.bw</emphasis> &gt; <emphasis remap="I">image.px</emphasis></para>
<para>bw-ps -L -c -W 5.2 &lt; image.bw &gt; image.ps</para>
<para>Makes a PostScript file of the (assumed 512 square) image, with
the output image 5.2 inches square, in landscape mode, centered
+3 -3
View File
@@ -59,7 +59,7 @@ as a decimal number in the range of 0 to 255.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-s</option> <replaceable>square_file_size</replaceable></term>
<term><option>-s</option> <replaceable>squarefilesize</replaceable></term>
<listitem>
<para>sets the saved image width and height to the indicated
value.</para>
@@ -82,12 +82,12 @@ as a decimal number in the range of 0 to 255.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<literallayout remap='RS'>
bw-rle <emphasis remap='I'>tank.bw tank.rle</emphasis>
<emphasis remap='I'> bw-rle tank.bw tank.rle</emphasis>
</literallayout> <!-- remap='RE' -->
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fb-rle</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>rle-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>rle-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fb-rle</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>rle-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>rle-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='author'><title>AUTHOR</title>
+3 -3
View File
@@ -40,11 +40,11 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwcrop</command>
<para><emphasis remap='I'>Bwcrop</emphasis>
crops any quadrilateral out of an arbitrarily large
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
input file
(<emphasis remap='I'>in.bw</emphasis>),
(<emphasis remap='I'>in.bw</emphasis>)<emphasis remap='I'>,</emphasis>
squares that region to a given height and width output size,
and writes the result to
<emphasis remap='I'>out.bw</emphasis>.
@@ -62,7 +62,7 @@ interpolation is done by this program.</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwrect</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwrect</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='author'><title>AUTHOR</title>
+9 -9
View File
@@ -26,7 +26,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwdiff</command>
<para><emphasis remap='I'>Bwdiff</emphasis>
compares two black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format files in one of several ways,
@@ -72,16 +72,16 @@ This mode is useful for producing masks
showing pixels which satisfy the given condition.
The default background is black, unless the
<option>-b</option>
option is specified, is which case the background is
<emphasis remap='I'>file1</emphasis>, with a
option is specified, is which case the background is file1, with a
lowered intensity.</para>
<para><command>bwdiff</command>
<para><emphasis remap='I'>Bwdiff</emphasis>
accepts
``<option>-</option>''
as a synonym for stdin, and
``<literal>.</literal>''
as a synonym for /dev/null .</para>
as a synonym for
/<emphasis remap='I'>dev</emphasis>/<emphasis remap='I'>null</emphasis>.</para>
<para>Note that this program also produces useful results on
color
@@ -93,13 +93,13 @@ files.</para>
<para>Suppose you ran
<citerefentry><refentrytitle>pixstat</refentrytitle><manvolnum>1</manvolnum></citerefentry>
on a file and found the modes to be red=107, green=93, blue=70.
You could display those pixels whose colors are at these values by:</para>
<para>
gencolor 107 93 70 | bwdiff -e <emphasis remap='I'>file.pix</emphasis> - | pix-fb</para>
You could display those pixels whose colors are at these values by:
<!-- .br -->
<emphasis remap='I'>gencolor 107 93 70 | bwdiff -e file.pix - | pix-fb</emphasis></para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pixdiff</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwstat</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pixdiff</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwstat</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
+3 -3
View File
@@ -33,7 +33,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwfilter</command>
<para><emphasis remap='I'>Bwfilter</emphasis>
applies one of several 3x3 kernel filters to a black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file.
@@ -102,7 +102,7 @@ a laplacian for example is "centered" about zero, thus it
adds 128 to the answer to yield a difference from neutral grey.
The
<option>-O</option>
flag can be used to change this offset.</para>
flag can bw used to change this offset.</para>
<para>The
<option>-v</option>
@@ -114,7 +114,7 @@ flag displays the max and minimum values and the kernel information on standard
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
+1 -1
View File
@@ -24,7 +24,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwhist</command>
<para><emphasis remap='I'>Bwhist</emphasis>
displays a histogram of the pixel values in a
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file. If a file is not given, standard input is read.
+2 -2
View File
@@ -26,13 +26,13 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwhisteq</command>
<para><emphasis remap='I'>Bwhisteq</emphasis>
automatically equalizes the histogram of a black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file.
It reads the file
<emphasis remap='I'>file.bw</emphasis>
and writes a "remapped" version of it on standard output.
and writes a "remapped" version of it on its standard output.
The method used is to distribute the values of the histogram, as
best as possible, in order to
produce a constant average "density",
+1 -1
View File
@@ -27,7 +27,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwmod</command>
<para><emphasis remap='I'>Bwmod</emphasis>
will perform a series of arithmetic operations on each 8-bit pixel
of its input/output stream. This is a
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
+2 -24
View File
@@ -38,31 +38,9 @@
extracts a rectangular region from a black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file. The default input image size is 512x512.
The x,y coordinates of the origin (the default xorig=0, yorig=0 corresponds to the
lower left corner) are passed as
The x,y coordinates of the origin (the defaults xorig=0, yorig=0 correspond to the
lower left corner) and the dimension of the output image are passed as
command line arguments.</para>
<para>The
<option>-w </option><replaceable>file_width</replaceable>
flag specifies the width of each scanline in the input file, in pixels.
<option>-W </option><replaceable>scr_width</replaceable>
does the same for the display device.</para>
<para>The
<option>-n </option><replaceable>file_height</replaceable>
and
<option>-N </option><replaceable>scr_height</replaceable>
flags specifies the height in scanlines of the input file or display device
respectively.</para>
<para><option>-s </option><replaceable>squarefilesize</replaceable>
and
<option>-S </option><replaceable>squarescrsize</replaceable>
set both the height and width to the size given (for input file and display device respectively).</para>
<para><option>-o </option><replaceable>out_file.bw</replaceable> is a way of specifying output
file name.</para>
<para>This utility supports pipes and can read/write from/to them.
</para>
</refsect1>
+1
View File
@@ -36,6 +36,7 @@
<para>
<command>bwscale</command>
<emphasis remap="I">Bwscale</emphasis>
will take a black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file of given dimensions and produce a larger or smaller
+4 -4
View File
@@ -30,7 +30,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwshrink</command>
<para><emphasis remap='I'>Bwshrink</emphasis>
will take a black and white
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file of given dimensions and produce a smaller
@@ -52,15 +52,15 @@ and then scales the image down
to 1/factor the original size in both dimensions.</para>
<para>By default, <command>bwshrink</command> uses boxcar averaging to produce the output pixels from
<para>By default, bwshrink uses boxcar averaging to produce the output pixels from
the input. The
<option>-u</option>
option causes <command>bwshrink</command> to use image undersampling instead.</para>
option causes bwshrink to use image undersampling instead.</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwcrop</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwrect</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwcrop</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwrect</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bwscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='bugs'><title>BUGS</title>
+9 -9
View File
@@ -24,7 +24,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwstat</command>
<para><emphasis remap='I'>Bwstat</emphasis>
will take the given
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format file,
@@ -34,19 +34,19 @@ related to the pixel intensities is produced.
These include:
<!-- .br -->
The number of pixels (and the square root of this which is the
file dimensions if square);
file dimensions if square).
<!-- .br -->
the max and min values;
The max and min values.
<!-- .br -->
the mean;
The mean.
<!-- .br -->
the median (dividing line where half the pixels are above this
value, half below);
The median (dividing line where half the pixels are above this
value, half below).
<!-- .br -->
the mode (most frequently occurring value) and the number of pixels
at this value;
The mode (most frequently occurring value) and the number of pixels
at this value.
<!-- .br -->
the variance, standard deviation, and skew.</para>
The variance, standard deviation, and skew.</para>
<para>The
<option>-v</option>
+5 -5
View File
@@ -25,24 +25,24 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>bwthresh</command>
<para><emphasis remap='I'>Bwthresh</emphasis>
reads from standard input a stream of black-and-white data in
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
format
and thresholds it among the
<emphasis remap='I'>val</emphasis>s,
<emphasis remap='I'>vals,</emphasis>
writing the resulting
<citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
data to standard output.
The
<emphasis remap='I'>val</emphasis>s
<emphasis remap='I'>vals</emphasis>
must appear on the command line in strictly increasing order.</para>
<para>The grey scale 0..255 is divided evenly into
<emphasis remap='I'>n</emphasis>+1
bins,
and each pixel of input is compared to the
<emphasis remap='I'>val</emphasis>s,
<emphasis remap='I'>vals,</emphasis>
to determine which of the
<emphasis remap='I'>n</emphasis>+1
grey levels should be output.</para>
@@ -52,7 +52,7 @@ grey levels should be output.</para>
<para>The command</para>
<!-- .in +5 -->
<para>bwthresh 37 143 &lt; <emphasis remap='I'>file.bw</emphasis> &gt; <emphasis remap='I'>file2.bw</emphasis></para>
<para><emphasis remap='I'>bwthresh 37 143 &lt; file.bw &gt; file2.bw</emphasis></para>
<!-- .in &bsol;-5 -->
<para>performs the following mapping:</para>
+9 -10
View File
@@ -26,7 +26,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>cad_boundp</command>
<para><emphasis remap='I'>cad_boundp</emphasis>
reads from
<emphasis remap='I'>input</emphasis>
(standard input if not specified)
@@ -57,7 +57,7 @@ the output will consist of
line segment data
suitable for input into
another invocation of
<command>cad_boundp</command> .</para>
<emphasis remap='I'>cad_boundp</emphasis>.</para>
<para>Input lines not beginning with a number
are silently skipped.
@@ -86,7 +86,7 @@ erroneous results.</para>
</refsect1>
<refsect1 xml:id='restrictions'><title>RESTRICTIONS</title>
<para><command>cad_boundp</command>
<para><emphasis remap='I'>cad_boundp</emphasis>
may output a polygon
smaller than desired
or produce a
@@ -115,9 +115,9 @@ disjoint parts.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<blockquote remap='RS'>
<para>$ cad_boundp -t 0.1
<para>$ <emphasis remap='I'>cad_boundp -t 0.1
<!-- .br -->
# <emphasis remap='I'>comment</emphasis>
# comment
<!-- .br -->
0 2 0 1
<!-- .br -->
@@ -139,7 +139,6 @@ disjoint parts.</para>
<!-- .br -->
0 1 3 1
<!-- .br -->
<emphasis remap='I'>
^D</emphasis>
<!-- .br -->
1 0
@@ -165,12 +164,12 @@ disjoint parts.</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>cad_parea</refentrytitle><manvolnum>1</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>cad_parea</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
<para>Any error condition causes
<command>cad_boundp</command>
<emphasis remap='I'>cad_boundp</emphasis>
to terminate
with non-zero exit status
after it prints an error message
@@ -184,12 +183,12 @@ produces an appropriate message.</para>
having only one line segment
connected to it
is found on the perimeter,
<command>cad_boundp</command>
<emphasis remap='I'>cad_boundp</emphasis>
produces the message
"degenerate input".</para>
<para>If there is too much data for
<command>cad_boundp</command>
<emphasis remap='I'>cad_boundp</emphasis>
to handle,
the message
"out of memory"
+6 -7
View File
@@ -24,7 +24,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>cad_parea</command>
<para><emphasis remap='I'>cad_parea</emphasis>
reads from
<emphasis remap='I'>input</emphasis>
(standard input if not given)
@@ -56,9 +56,9 @@ traced in both directions.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<blockquote remap='RS'>
<para>$ cad_parea
<para>$ <emphasis remap='I'>cad_parea
<!-- .br -->
# <emphasis remap='I'>comment</emphasis>
# comment
<!-- .br -->
1 0
<!-- .br -->
@@ -80,7 +80,6 @@ traced in both directions.</para>
<!-- .br -->
1 1
<!-- .br -->
<emphasis remap='I'>
^D</emphasis>
<!-- .br -->
4
@@ -88,17 +87,17 @@ traced in both directions.</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>cad_boundp</refentrytitle><manvolnum>1</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>cad_boundp</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
<para>Improperly formatted input
produces an error message
and terminates
<command>cad_parea</command>
<emphasis remap='I'>cad_parea</emphasis>
with non-zero exit status.</para>
<para><command>cad_parea</command>
<para><emphasis remap='I'>cad_parea</emphasis>
outputs "0"
for the area
of a degenerate polygon.</para>
+50 -44
View File
@@ -23,7 +23,7 @@
<refsection xml:id="description"><title>DESCRIPTION</title>
<para><command>cell-fb</command>
<para><emphasis remap="I">Cell-fb</emphasis>
reads a stream of cell-by-cell data
and displays the data, one view at a time, on a frame buffer.
If
@@ -48,10 +48,10 @@ reference, which, through a color map, corresponds to a color.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-F </option><replaceable>fbfile</replaceable></term>
<term><option>-F</option><replaceable>fbfile</replaceable></term>
<listitem>
<para>Write graphics output to
<emphasis remap="I">fbfile</emphasis>,
<emphasis remap="I">fbfile,</emphasis>
which may be any UNIX file (or frame-buffer device).
In the absence of the
<option>-F</option>
@@ -68,67 +68,67 @@ Otherwise, the host's default frame buffer is used
</listitem>
</varlistentry>
<varlistentry>
<term><option>-N </option><replaceable>scr_height</replaceable></term>
<term><option>-N</option><replaceable>scr_height</replaceable></term>
<listitem>
<para>Set screen (frame-buffer) height to
<emphasis remap="I">scr_height</emphasis>
pixels, where
<emphasis remap="I">scr_height</emphasis>
pixels.
<emphasis remap="I">Scr_height</emphasis>
may legally be any integer greater than -2.
See the discussion of autosizing below.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-S </option><replaceable>scr_size</replaceable></term>
<term><option>-S</option><replaceable>scr_size</replaceable></term>
<listitem>
<para>Set screen (frame-buffer) width and height to
<emphasis remap="I">scr_size</emphasis>
pixels, where
<emphasis remap="I">scr_size</emphasis>
pixels.
<emphasis remap="I">Scr_size</emphasis>
may legally be any integer greater than -2.
See the discussion of autosizing below.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-W </option><replaceable>scr_width</replaceable></term>
<term><option>-W</option><replaceable>scr_width</replaceable></term>
<listitem>
<para>Set screen (frame-buffer) width to
<emphasis remap="I">scr_width</emphasis>
pixels, where
<emphasis remap="I">scr_width</emphasis>
pixels.
<emphasis remap="I">Scr_width</emphasis>
may legally be any integer greater than -2.
See the discussion of autosizing below.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-X </option><replaceable>n</replaceable></term>
<term><option>-X</option><replaceable>n</replaceable></term>
<listitem>
<para>Set the local debug flag to the hexadecimal value
<emphasis remap="I">n</emphasis>.</para>
<emphasis remap="I">n.</emphasis></para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-a </option><replaceable>h v</replaceable><emphasis remap="B"/></term>
<term><option>-a</option><replaceable>“h v”</replaceable><emphasis remap="B"/></term>
<listitem>
<para>Do not display the data,
simply print out the frame-buffer coordinates of the grid-plane point
(<emphasis remap="I">h</emphasis>, <emphasis remap="I">v</emphasis>).
(<emphasis remap="I">h, v</emphasis>).
This option is useful for outboard manipulation of the
<citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry>
data created by
<command>cell-fb</command> .</para>
<emphasis remap="I">cell-fb.</emphasis></para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-b </option><replaceable>n</replaceable></term>
<term><option>-b</option><replaceable>n</replaceable></term>
<listitem>
<para>Ignore values not equal to
<emphasis remap="I">n</emphasis>.
<emphasis remap="I">n.</emphasis>
All other cell-data values are mapped to the background color.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-c </option><replaceable>n</replaceable></term>
<term><option>-c</option><replaceable>n</replaceable></term>
<listitem>
<para>Assume a cell size of
<emphasis remap="I">n</emphasis>
@@ -137,10 +137,10 @@ The default cell size is 100 user units.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-d </option><replaceable>m n</replaceable><emphasis remap="B"/></term>
<term><option>-d</option><replaceable>“m n”</replaceable><emphasis remap="B"/></term>
<listitem>
<para>Scale the data values from the interval
[<emphasis remap="I">m</emphasis>, <emphasis remap="I">n</emphasis>]
[<emphasis remap="I">m, n</emphasis>]
into the unit interval [0, 1].
The scaling is performed before values are mapped to colors,
so the
@@ -163,7 +163,7 @@ for which no scaling is necessary.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-f </option><replaceable>n</replaceable></term>
<term><option>-f</option><replaceable>n</replaceable></term>
<listitem>
<para>Display field number
<emphasis remap="I">n</emphasis>
@@ -179,6 +179,13 @@ By default, field 1 is displayed.</para>
<listitem>
<para>Display the grid.
Causes a 1-pixel spacing between cells in the output.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-h</option></term>
<listitem>
<para>Force high-resolution display (1024×1024 pixels).
See the discussion of autosizing below.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -209,7 +216,7 @@ See the discussion of autosizing below.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-l </option><replaceable>az el</replaceable><emphasis remap="B"/></term>
<term><option>-l</option><replaceable>“az el”</replaceable><emphasis remap="B"/></term>
<listitem>
<para>Write log information to the standard output.
When given this option,
@@ -227,19 +234,19 @@ If a single view has not been specified,
this option causes an implicit
<option>-v</option> 1,
which may, of course, be overridden explicitly.
N.B. <command>cell-fb</command>
N.B.—<emphasis remap="I">Cell-fb</emphasis>
makes no use whatever of the values
<emphasis remap="I">az</emphasis> and <emphasis remap="I">el</emphasis>,
it merely writes them to the log.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-m </option><replaceable>n color</replaceable><emphasis remap="B"/></term>
<term><option>-m</option><replaceable>“n color”</replaceable><emphasis remap="B"/></term>
<listitem>
<para>Map cell data value
<emphasis remap="I">n</emphasis>
to
<emphasis remap="I">color</emphasis>.
<emphasis remap="I">color.</emphasis>
The value
<emphasis remap="I">n</emphasis>
will be truncated, if necessary, to
@@ -247,20 +254,20 @@ the nearest lower of the discrete values listed in the description of the
<option>-k</option>
option above.
The background color can be indexed by specifying the value 1.1 for
<emphasis remap="I">n</emphasis>.
<emphasis remap="I">n.</emphasis>
For the meaning and format of
<emphasis remap="I">color</emphasis>,
<emphasis remap="I">color,</emphasis>
see the
<link linkend="definitions">DEFINITIONS</link>
section below.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-M </option><replaceable>color1 color2</replaceable><emphasis remap="B"/></term>
<term><option>-M</option><replaceable>“color1 color2”</replaceable><emphasis remap="B"/></term>
<listitem>
<para>Define the color map
to be a ramp between
<emphasis remap="I">color1</emphasis> and <emphasis remap="I">color2</emphasis>.
<emphasis remap="I">color1</emphasis> and <emphasis remap="I">color2.</emphasis>
This allows frugality with the colors in an image:
if, for example, cell data is plotted in gray scale,
then many other colors remain for use in
@@ -270,14 +277,14 @@ is a typical cold-to-hot, blue-to-red scale,
excepting that the smallest value in the input domain
is mapped to white.
For the meaning and format of
<emphasis remap="I">color1</emphasis> and <emphasis remap="I">color2</emphasis>,
<emphasis remap="I">color1</emphasis> and <emphasis remap="I">color2,</emphasis>
see the
<link linkend="definitions">DEFINITIONS</link>
section below.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-p </option><replaceable>h v</replaceable><emphasis remap="B"/></term>
<term><option>-p</option><replaceable>“h v”</replaceable><emphasis remap="B"/></term>
<listitem>
<para>Offset the picture from the lower-left corner of the frame buffer display
by
@@ -290,13 +297,12 @@ then the horizontal and vertical offsets are both set to this value.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-s </option><replaceable>w h</replaceable><emphasis remap="B"/></term>
<term><option>-s</option><replaceable>“w h”</replaceable><emphasis remap="B"/></term>
<listitem>
<para>Plot each cell as a rectangle of width
<emphasis remap="I">w</emphasis>
pixels and height
<emphasis remap="I">h</emphasis>
pixels.
<emphasis remap="I">h</emphasis>pixels.
This option has the effect of scaling the picture independently in the
horizontal and vertical dimensions.
The default is 10 pixels per cell in each dimension, not including the
@@ -306,10 +312,10 @@ then the width and height are both set to this value.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-v </option><replaceable>n</replaceable></term>
<term><option>-v</option><replaceable>n</replaceable></term>
<listitem>
<para>Display only view number
<emphasis remap="I">n</emphasis>.
<emphasis remap="I">n.</emphasis>
Views are numbered starting at 1.
If
<emphasis remap="I">n</emphasis> = 0,
@@ -317,19 +323,19 @@ all views are displayed sequentially,
which is the default behavior.
The option
<option>-v</option> 0
implicitly turns off logging
implicitly turns off logging.
(see the
<option>-l</option>
option above).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-x </option><replaceable>n</replaceable></term>
<term><option>-x</option><replaceable>n</replaceable></term>
<listitem>
<para>Set the
<citerefentry><refentrytitle>libbu</refentrytitle><manvolnum>3</manvolnum></citerefentry>
debug flag to the hexadecimal value
<emphasis remap="I">n</emphasis>.
<emphasis remap="I">n.</emphasis>
This option is useful primarily in debugging
memory allocation.</para>
</listitem>
@@ -347,7 +353,7 @@ utility such as
</refsection>
<refsection xml:id="discussion"><title>DISCUSSION</title>
<para><command>cell-fb</command>
<para><emphasis remap="I">Cell-fb</emphasis>
determines the appropriate width and height of the frame buffer
independently.
For each there are three methods.
@@ -361,7 +367,7 @@ options,
will use exactly the specified values.
Otherwise,
it performs autosizing for each view.
<command>cell-fb</command>'s
<emphasis remap="I">Cell-fb</emphasis>'s
original behavior is called loose-fit autosizing.
In that case, a frame-buffer dimension will be set to 512 pixels
unless the image will not fit,
@@ -455,7 +461,7 @@ the color key will appear underneath the
grid of cells, and the display will be erased before each view is drawn.</para>
<literallayout remap="RS" class="normal">
$ cell-fb -F fictitious.brlcad.org: -gek -p 20 30 inputs
$ <emphasis remap="I">cell-fb</emphasis>  -F  fictitious.brlcad.org:  -gek  -p  “20 30”  inputs
</literallayout> <!-- remap='RE' -->
</refsection>
+3 -3
View File
@@ -42,12 +42,12 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>chan_mult</command>
<para><emphasis remap='I'>Mult_chan</emphasis>
will multiply all numbers in the specified columns by the given
factor. The <emphasis remap='I'>infile</emphasis> is
factor. The infile is
an ASCII file, with columns separated by white space. The columns are
numbered from 0 to (n-1).
<command>chan_add</command>
<emphasis remap='I'>Add_chan</emphasis>
behaves analogously, but with
addition rather than multiplication.</para>
</refsect1>
+8 -8
View File
@@ -37,25 +37,25 @@ channels or columns. Each word, separated by whitespaces, should be less
than 40 characters long. The channels in each input file are specified
and then mapped to the desired channels in the output file(s). These are
the sort of things that can be done using
<command>cut</command>
<emphasis remap='I'>cut</emphasis>
and
<command>paste</command>,
<emphasis remap='I'>paste,</emphasis>
but when
working on animation tables it's often nice to be able to do it in one
step.</para>
<para><emphasis remap='I'>Infile</emphasis>s
<para><emphasis remap='B'>Infile</emphasis>s
are files to be read from,
<emphasis remap='I'>outfile</emphasis>s
<emphasis remap='B'>outfile</emphasis>s
are files to be written
to, and each
<emphasis remap='I'>id</emphasis>
<emphasis remap='B'>id</emphasis>
is a small positive integer identifying a channel. All of the
input
<emphasis remap='I'>id</emphasis>'s
<emphasis remap='B'>id</emphasis>'s
should be distinct integers, or the results are not guaranteed.</para>
<para><command>chan_permute</command>
<para><emphasis remap='I'>Chan_permute</emphasis>
interprets
<option>-i stdin</option>
as standard input and
@@ -85,7 +85,7 @@ followed by both columns of file1.</para>
more than once for input, but may not be referenced for input and output
together or output and output together. In the latter case, the second
output reference overrides the other. The
<emphasis remap='I'>id</emphasis>'s
<emphasis remap='B'>id</emphasis>'s
must be integers
somewhere between 0 and the number of arguments, inclusive.</para>
</refsect1>
+3 -3
View File
@@ -24,7 +24,7 @@
<refsection xml:id="description"><title>DESCRIPTION</title>
<para><command>cmap-fb</command>
<para><emphasis remap="I">Cmap-fb</emphasis>
loads a colormap into a framebuffer. A colormap
file can be specified on the command line, otherwise standard
input will be read.
@@ -39,9 +39,9 @@ the framebuffer will be retained (one can view this as
"overlaying" the existing colormap).</para>
<para>By default, the display is assumed to be 512x512 pixels;
if the
by specifying the
<option>-H</option>
flag is specified, the size is changed to 1024x1024.
flag, the size is changed to 1024x1024.
This size distinction is important for devices like the Adage
framebuffers which have different operating modes based on the
display size.</para>
+1 -1
View File
@@ -29,7 +29,7 @@
<para>
<command>coil</command> creates a pipe shape within <emphasis remap="I">coil.g</emphasis>
or a user supplied file that implements a coil according to user provided dimensions.
If no dimensions are supplied, defaults are used.
If no dimensions are supplied defaults are used.
</para>
</refsection>
+6 -6
View File
@@ -32,11 +32,11 @@ a GIFT-style input file, convert the geometry into
the internal form used by the BRL-CAD package,
and write an MGED-style binary database.</para>
<para>Each solid is given the name s###, retaining the COMGEOM solid number.
Each region is given the name r###, retaining the COMGEOM region number.
Regions are grouped together into various groups g### based
on the region-id numbers. Group g00 gets all regions with region-id
of zero, g0 gets ids one through 99, g1 gets ids 100 through 199, etc.</para>
<para>Each solid is given the name “s###”, retaining the COMGEOM solid number.
Each region is given the name “r###”, retaining the COMGEOM region number.
Regions are grouped together into various groups “g###” based
on the region-id numbers. Group “g00” gets all regions with region-id
of zero, “g0” gets ids one through 99, “g1” gets ids 100 through 199, etc.</para>
<para>The default input is COMGEOM version 5.
Version 4 can be converted by specifying the
@@ -70,7 +70,7 @@ feature of
</refsect1>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<para>comgeom-g -d1 -v4 <emphasis remap='I'>file.cg file.g</emphasis></para>
<para><emphasis remap='I'>comgeom-g -d1 -v4 file.cg file.g</emphasis></para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
+1 -1
View File
@@ -24,7 +24,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>conv-vg2g</command>
<para><emphasis remap='I'>Conv-vg2g</emphasis>
converts several older forms of binary
<citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry>
databases to the current form.</para>
+3 -3
View File
@@ -41,7 +41,7 @@ Especially for double-precision floating point,
DEC, Cray, and IBM have peculiar formats and byte orderings.
The network-independent byte orderings used within BRL-CAD is
big-endian (most significant bit first, on the left side of the word),
twos complement.
twos compliment.
The network-independent double-precision floating point format used
within BRL-CAD is 64-bit IEEE 754, transmitted in big-endian order.</para>
@@ -59,12 +59,12 @@ format would be "hss", and the output format would be "n32".</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>pix-bw</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>dpix-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>;
<para><citerefentry><refentrytitle>pix-bw</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>dpix-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>bw-pix</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
<!-- .br -->
M. J. Muuss,
``<emphasis remap='I'>Workstations, Networking, Distributed Graphics, and Parallel Processing</emphasis>``
in Computer Graphics Techniques: Theory and Practice,
edited by D. F. Rogers, R. A. Earnshaw, Springer-Verlag, 1990</para>
edited by D. F. Rogers, R. A. Earnshaw, Springer-Verlag, 1990.</para>
</refsect1>
+2 -2
View File
@@ -24,7 +24,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>cy-g</command>
<para><emphasis remap='I'>cy-g</emphasis>
converts the specified
<emphasis remap='I'>input_cy_file</emphasis>
to a BRL-CAD
@@ -38,7 +38,7 @@ scan format. The result of the conversion is a single
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ cy-g <emphasis remap='I'>sample.cy sample.g</emphasis>
$ <emphasis remap='I'>cy-g sample.cy sample.g</emphasis>
</synopsis>
</refsect1>
+3 -3
View File
@@ -35,7 +35,7 @@
<variablelist>
<varlistentry>
<term><emphasis>match</emphasis><option>regular_exp</option></term>
<term><emphasis>match [regular_exp]</emphasis></term>
<listitem>
<para>
Returns a list of all objects in that database that match the list of regular
@@ -45,7 +45,7 @@
</varlistentry>
<varlistentry>
<term><emphasis>get shape_or_path</emphasis><option>attribute</option></term>
<term><emphasis>get shape_or_path [attribute]</emphasis></term>
<listitem>
<para>
Returns information about the primitive shape at the end of the <emphasis>shape_or_path</emphasis>.
@@ -70,7 +70,7 @@
</varlistentry>
<varlistentry>
<term><emphasis>adjust shape_name attribute new_value1</emphasis><option>new_value2 new_value3 ...</option></term>
<term><emphasis>adjust shape_name attribute new_value1 [new_value2 new_value3...]</emphasis></term>
<listitem>
<para>
Modifies the shape named <emphasis>shape_name</emphasis> by adjusting the value of its
+9 -9
View File
@@ -24,14 +24,14 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>dbclean</command>
<para><emphasis remap='I'>Dbclean</emphasis>
operates on the indicated input database
<emphasis remap='I'>in_model.g</emphasis>
and produces a compacter version of the same as
and produces a compacter version of the same
<emphasis remap='I'>out_model.g.</emphasis></para>
<para>The objective is to remove "holes" in the original database which resulted from use of
the <emphasis remap='I'>kill</emphasis>/<emphasis remap='I'>killall</emphasis> commands in
<para>The objective is to remove ``holes" left in the original database by using
the <emphasis remap='I'>kill/killall</emphasis> command in
<citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Note that when a database is compacted in this manner, the compacting is
dependent on the successful completion of the converters
@@ -39,24 +39,24 @@ dependent on the successful completion of the converters
and
<citerefentry><refentrytitle>asc2g</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
The compacting will only be aborted if one of the conversions fails. Thus,
when either converter "skips" solids, <command>dbclean</command> will continue, and
when either converter ``skips" solids, <command>dbclean</command> will continue, and
<emphasis remap='I'>out_model.g</emphasis>
will be written, albeit without the skipped solids. This will also
will be written, albeit, without the skipped solids. This will also
result in a smaller database.</para>
</refsect1>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<para>This section will acquaint the user with the ordinary usage of <command>dbclean</command> .</para>
<para>This section will acquaint the user with the ordinary usage of <command>dbclean</command>.</para>
<literallayout remap='.nf'>
dbclean <emphasis remap='I'>in_model.g out_model.g</emphasis>
<emphasis remap='I'>dbclean in_model.g out_model.g</emphasis>
</literallayout> <!-- .fi -->
<para>This will result in a compacted version of the input.</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
+5 -5
View File
@@ -31,7 +31,7 @@
<para><command>dbcp</command>
is a program for copying data rapidly between devices.</para>
<para>This command is DEPRECATED. Use <command>dd</command> instead.</para>
<para>This command is DEPRECATED. Use 'dd' instead.</para>
<para>While the primary application is to move data between raw devices such as
tape and disk, it can also be used with pipes.
@@ -55,15 +55,15 @@ the number of records processed is printed upon exit.</para>
</refsect1>
<refsect1 xml:id='examples'><title>EXAMPLES</title>
<para>$ <emphasis remap='B'>dbcp 16 &lt; /dev/rdk1a &gt; /dev/rmt0</emphasis></para>
<para>
<para>$ <emphasis remap='B'>dbcp 16 &lt; /dev/rdk1a &gt; /dev/rmt0</emphasis>
<!-- .br -->
<command>dbcp</command>
copies the filesystem on dk1a to tape
with a record size of 8K bytes (16 * 512).
This allows "streaming" tape drives to operate a peak speed.</para>
<para>$ <emphasis remap='B'>tar cf - . | dbcp 20 &gt; /dev/rmt0</emphasis></para>
<para>
<para>$ <emphasis remap='B'>tar cf - . | dbcp 20 &gt; /dev/rmt0</emphasis>
<!-- .br -->
The
<emphasis remap='I'>tar</emphasis>
process runs independently of the
+5 -5
View File
@@ -26,7 +26,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>dbupgrade</command>
operates on the indicated input geometry database
<emphasis remap='I'>input.g</emphasis>,
<emphasis remap='I'>input.g</emphasis>
recognizing the version of the BRL-CAD database provided as input and
then converting it to the current database version. Output is then saved to the specified
<emphasis remap='I'>output.g</emphasis>
@@ -38,7 +38,7 @@ binary-incompatible platform. However, this process may be imperfect - the best
the original platform on which the file was created is available) is to run
<command>dbupgrade</command>
on the file before transferring from the originating platform. Once upgraded the output file will be
platform-independent regardless of the platform on which the upgrade was done.</para>
platform independent regardless of the platform on which the upgrade was done.</para>
<para>Running
<command>dbupgrade</command>
@@ -46,12 +46,12 @@ removes the need to run
<citerefentry><refentrytitle>g2asc</refentrytitle><manvolnum>1</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>asc2g</refentrytitle><manvolnum>1</manvolnum></citerefentry>
on a database to move it between computers (historically this was a way to work around the platform-specific nature of v4 files).
The latest BRL-CAD geometry database format is platform-independent.</para>
on a database to move it between computers (historically this was a way to work around the platform specific nature of v4 files.)
The latest BRL-CAD geometry database format is platform independent.</para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>g2asc</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>asc2g</refentrytitle><manvolnum>1</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>g2asc</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>asc2g</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
+6 -6
View File
@@ -29,7 +29,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>dxf-g</command>
<para><emphasis remap='I'>dxf-g</emphasis>
converts the specified
<emphasis remap='I'>file.dxf</emphasis>
to a BRL-CAD
@@ -78,7 +78,7 @@ will be considered to be the same vertex.</para>
</variablelist>
<para>The
<emphasis remap='I'>file.dxf</emphasis>
<emphasis remap='B'>file.dxf</emphasis>
file is expected to be in the ASCII Autodesk DXF format as defined in the
Autocad 2006 manuals. This converter handles entities of types:</para>
@@ -115,11 +115,11 @@ SPLINE</para>
<para>The POLYLINE entities in AUTOCAD are actually a container for numerous different entity types. The types
of POLYLINE entities converted include:</para>
<para>3D polylines;
<para>3D polylines
<!-- .br -->
3D polygon meshes;
3D polygon meshes
<!-- .br -->
polyface meshes</para>
polyface meshes.</para>
<para>SOLID entities are 2D shapes with a solid fill, but this converter does not do
any filling.
@@ -128,7 +128,7 @@ Each layer is converted to a separate object. Colors are also converted.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ dxf-g <emphasis remap='I'>sample.dxf sample.g</emphasis>
$ <emphasis remap='I'>dxf-g sample.dxf sample.g</emphasis>
</synopsis>
</refsect1>
+2 -2
View File
@@ -29,7 +29,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>enf-g</command>
<para><emphasis remap='I'>enf-g</emphasis>
converts the specified
<emphasis remap='I'>input_enf_facet_file</emphasis>
to a BRL-CAD
@@ -57,7 +57,7 @@ by a tab.
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ enf-g <emphasis remap='I'>sample.enf sample.g</emphasis>
$ <emphasis remap='I'>enf-g sample.enf sample.g</emphasis>
</synopsis>
</refsect1>
+4 -70
View File
@@ -17,14 +17,14 @@
<refsynopsisdiv xml:id='synopsis'>
<cmdsynopsis>
<command>euclid-g</command>
<arg choice="opt" rep="repeat"><replaceable>options</replaceable></arg>
<arg choice="opt">&lt; <replaceable>euclid_file</replaceable></arg>
<arg choice='plain'><replaceable>euclid_file</replaceable></arg>
<arg choice='plain'><replaceable>database.g</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>euclid-g</command>
<para><emphasis remap='I'>euclid-g</emphasis>
converts the specified
<emphasis remap='I'>euclid_file</emphasis>
to a BRL-CAD
@@ -37,77 +37,11 @@ of polygonal faces. Each face may be one of either a simple face (no holes),
a complex face (contains at least one hole), or a simple hole.
This converter creates a region for each object ID number by unioning
together all the objects with the same ID number.</para>
<para>The following options are recognized:</para>
<variablelist remap='TP'>
<varlistentry>
<term><option>-d tolerance</option></term>
<listitem>
<para>
sets tolerance (units of mm); default value is 0.0005
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-v</option></term>
<listitem>
<para>
turns on verbose mode, for debugging; its output is to standard error
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-i euclid_file_name</option></term>
<listitem>
<para>
sets input file name; default is to take standard input
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-o filename.g</option></term>
<listitem>
<para>
sets output file name; default file name is euclid.g
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-n</option></term>
<listitem>
<para>
indicates NOT to write as polysolids; opposite of <option>-p</option>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-p</option></term>
<listitem>
<para>
indicates to write as polysolids (this is default); opposite of <option>-n</option>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-x #</option> and <option>-X #</option></term>
<listitem>
<para>
sets debug flags
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ euclid-g <emphasis remap='I'>sample.euclid sample.g</emphasis>
$ <emphasis remap='I'>euclid-g sample.euclid sample.g</emphasis>
</synopsis>
</refsect1>
+14 -11
View File
@@ -30,7 +30,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>fast4-g</command>
<para><emphasis remap='I'>fast4-g</emphasis>
converts the specified
<emphasis remap='I'>file.fastgen4</emphasis>
to a BRL-CAD
@@ -72,14 +72,14 @@ file.</para>
option allows the user to specify a restricted set of components to process from the
input file. The
<emphasis remap='I'>id_list</emphasis>
may be a comma-separated list of ident numbers and ranges. For example,
may be a comma separated list of ident numbers and ranges. For example,
<option>-c 3002,5678,9213,1002-1100</option>
will convert only the regions with idents of 3002,5678,9213, and everything from 1002 through 1100.</para>
<para>If you have a FASTGEN2 or FASTGEN3 format file, they can be converted by processing them with
<command>rpatch</command>
<emphasis remap='I'>rpatch</emphasis>
and then providing the resulting rpatch file to the
<command>patch-g</command>
<emphasis remap='I'>patch-g</emphasis>
converter. See their respective manual pages for more information.</para>
<para>The
@@ -87,21 +87,24 @@ converter. See their respective manual pages for more information.</para>
file is expected to be in the FASTGEN 4.1 format as defined in the
FASTGEN 4.1 User Manual.</para>
<para><emphasis remap='I'>CCONE1</emphasis>, <emphasis remap='I'>CCONE2</emphasis>,
<para><emphasis remap='I'>CCONE1, CCONE2,</emphasis>
and
<emphasis remap='I'>CCONE3</emphasis>
elements are converted to BRL-CAD truncated right cylinders
(<emphasis remap='I'>TRC</emphasis>). <emphasis remap='I'>CHEX2</emphasis>
<emphasis remap='I'>(TRC). CHEX2</emphasis>
elements are converted to BRL-CAD arbitrary convex polyhedrons
(<emphasis remap='I'>ARB8</emphasis>). <emphasis remap='I'>CLINE</emphasis>
<emphasis remap='I'>(ARB8).</emphasis>
<emphasis remap='I'>CLINE</emphasis>
elements are converted to BRL-CAD cline solids.
<emphasis remap='I'>CQUAD</emphasis>,
<emphasis remap='I'>CTRI</emphasis>, and
<emphasis remap='I'>CQUAD</emphasis>
,
<emphasis remap='I'>CTRI</emphasis>
, and
<emphasis remap='I'>CHEX1</emphasis>
elements are converted to faces of a BRL-CAD BOT (Bag Of Triangles).
<emphasis remap='I'>CSPHERE</emphasis>
elements are converted to BRL-CAD sphere
(<emphasis remap='I'>SPH</emphasis>)
<emphasis remap='I'>(SPH)</emphasis>
solids. BRL-CAD region ident numbers are assigned by combining the
FASTGEN4 group and component numbers:</para>
@@ -116,7 +119,7 @@ elements using an algorithm to create unique BRL-CAD names.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ fast4-g <emphasis remap='I'>sample.fastgen4 sample.g</emphasis>
$ <emphasis remap='I'>fast4-g sample.fastgen4 sample.g</emphasis>
</synopsis>
</refsect1>
+174
View File
@@ -0,0 +1,174 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id="fborle1">
<refmeta>
<refentrytitle>FB-ORLE
</refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo class="source">BRL-CAD</refmiscinfo>
<refmiscinfo class="manual">BRL-CAD</refmiscinfo>
</refmeta>
<refnamediv>
<refname>fb-orle</refname>
<refpurpose>save a frame buffer image in old run-length encoded form</refpurpose>
</refnamediv>
<!-- body begins here -->
<refsynopsisdiv xml:id="synopsis">
<cmdsynopsis sepchar=" ">
<command>fb-orle</command>
<arg choice="opt" rep="norepeat">-CScdHvw </arg>
<arg choice="opt" rep="norepeat"><arg choice="plain" rep="norepeat">-l </arg><arg choice="plain" rep="norepeat"><replaceable>x</replaceable></arg><arg choice="plain" rep="norepeat"><replaceable>y</replaceable></arg></arg>
<arg choice="opt" rep="norepeat"><arg choice="plain" rep="norepeat">-F </arg><arg choice="plain" rep="norepeat"><replaceable>Frame_buffer</replaceable></arg></arg>
<arg choice="opt" rep="norepeat"><arg choice="plain" rep="norepeat">-p </arg><arg choice="plain" rep="norepeat"><replaceable>x</replaceable></arg><arg choice="plain" rep="norepeat"><replaceable>y</replaceable></arg></arg>
<arg choice="opt" rep="norepeat"><replaceable>file.rle</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsection xml:id="description"><title>DESCRIPTION</title>
<para><command>fb-orle</command>
saves a frame buffer image in a file, using the
old University of Utah standard (Edition-2)
Run-Length Encoded (RLE) format.
This program is provided for compatibility with the old RLE image
tools, and generally should not be used for saving new images,
except where compatibility with the old tools is a factor.
The equivalent new tool is
<emphasis remap="I">fb-rle(1)</emphasis>.</para>
<para>The environment
variable
<envar>FB_FILE</envar>
is used to select the display device (see
<emphasis remap="I">brlcad(1)</emphasis>).
If this variable is not set, the default device for your system will
be used.
If
<emphasis remap="I">file.rle</emphasis>
is not specified, the encoded file is written to standard output.
<command>fb-orle</command>
attempts to compress flat-colored areas
as much as possible.
This means that it is generally reasonable to save an entire
image, since in RLE format it will not take up much more file space
than extracting and saving only the
interesting portion of the image.
The default action is to encode only data
pixels and to save the background color separately, so that when the image
is restored all non-image pixels will be set to the background pixel value
stored in the RLE header.
Images saved in this mode may be displayed normally, or in overlay
mode by the RLE decoder program (see
<citerefentry><refentrytitle>orle-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>).
Alternatively, the
<option>-S</option>
option may be used to RLE-encode the background as well (recommended only
if you don't have a flat background).</para>
<variablelist remap="TP">
<varlistentry>
<term><option>-C</option></term>
<listitem>
<para>Convert (crunch) an image with a non-standard color map so that the
RLE file created will redisplay with a standard color map.
Useful to preserve dramatic images created with weird color maps
so that Gamma correction (for film) can then also be applied.
This option is recommended when producing images for export to other
display systems, so that variations in the interpretation of color maps
between different types of display hardware do
not affect the displayed image.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-w</option></term>
<listitem>
<para>Convert the color image to black and white, and RLE-encode that.
The red, green, and blue components of each
pixel are combined via the NTSC transform to get an intensity value (Y) which
is saved. A more versatile tool for this is
<citerefentry><refentrytitle>pix-bw</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-S</option></term>
<listitem>
<para>Save all data in RLE format,
irrespective of whether it is background or not (straight box save).
It is not possible to
restore a file saved with
<option>-S</option>
as an overlay.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-c</option></term>
<listitem>
<para>Only save color map.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-l</option><replaceable> x y</replaceable></term>
<listitem>
<para>Specify the size of the saved box.
This is useful if only a portion of the image is to be saved.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-p</option><replaceable> x y</replaceable></term>
<listitem>
<para>Specify the upper left corner of the saved portion
of the image.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-F</option><replaceable> Frame_buffer</replaceable></term>
<listitem>
<para>Specify frame buffer.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-v</option></term>
<listitem>
<para>Verbose mode.
The program will provide voluminous status information
on its standard error as it proceeds through encoding the image.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-d</option></term>
<listitem>
<para>Debug mode.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-H</option></term>
<listitem>
<para>hi-res flag. Set both the height and width of the framebuffer
to 1024. The default is 512x512.</para>
</listitem>
</varlistentry>
</variablelist>
</refsection>
<refsection xml:id="example"><title>EXAMPLE</title>
<literallayout remap="RS" class="normal">
<emphasis remap="I">fb-orle -H tank.rle</emphasis>
</literallayout> <!-- remap='RE' -->
</refsection>
<refsection xml:id="author"><title>AUTHOR</title>
<para>BRL-CAD Team</para>
</refsection>
<refsection xml:id="copyright"><title>COPYRIGHT</title>
<para>This software is Copyright (c) 1986-2014 by the United States
Government as represented by U.S. Army Research Laboratory.</para>
</refsection>
<refsection xml:id="bug_reports"><title>BUG REPORTS</title>
<para>Reports of bugs or problems should be submitted via electronic
mail to &lt;devs@brlcad.org&gt;.</para>
</refsection>
</refentry>
+1 -1
View File
@@ -35,7 +35,7 @@ The environment
variable
<envar>FB_FILE</envar>
is used to select the display device (see
<citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>).
<emphasis remap="I">brlcad(1)</emphasis>).
If this variable is not set, the default device for your system will
be used.
Alternatively, the framebuffer may be explicitly specified
+1 -1
View File
@@ -37,7 +37,7 @@ The environment
variable
<envar>FB_FILE</envar>
is used to select the display device (see
<citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>).
<emphasis remap="I">brlcad(1)</emphasis>).
If this variable is not set, the default device for your system will
be used.
Alternatively, the framebuffer may be explicitly specified
+1 -1
View File
@@ -80,7 +80,7 @@
to be saved from. If not given, the environment variable
<acronym/><emphasis remap="B">FB_FILE</emphasis> is used
to select the display device (see
<citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>). If
<emphasis remap="I">brlcad(1)</emphasis>). If
<acronym/><emphasis remap="B">FB_FILE</emphasis> has not
been set, the default device for your system will be
used.</para>
+4 -3
View File
@@ -62,7 +62,7 @@ equal intensity.
At this point, all the other color bars will display the correct chroma.</para>
<para>The environment variable FB_FILE specifies
the current framebuffer; see
the current framebuffer, see
<citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Alternatively, the framebuffer may be explicitly specified
by using the
@@ -84,8 +84,9 @@ sets both the height and width to the size given.</para>
</refsection>
<refsection xml:id="inspirations"><title>INSPIRATIONS</title>
<para>Mike Pique, University of North Carolina</para>
<para>Doris Kochanek, National Film Board of Canada</para>
<para>Mike Pique, University of North Carolina
<!-- .br -->
Doris Kochanek, National Film Board of Canada</para>
</refsection>
<refsection xml:id="author"><title>AUTHOR</title>
+1 -1
View File
@@ -36,7 +36,7 @@ is used to change the color map of a frame buffer.</para>
to be saved from. If not given, the environment variable
<acronym/><emphasis remap="B">FB_FILE</emphasis> is used
to select the display device (see
<citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>). If
<emphasis remap="I">brlcad(1)</emphasis>). If
<acronym/><emphasis remap="B">FB_FILE</emphasis> has not
been set, the default device for your system will be
used.</para>
+1 -1
View File
@@ -39,7 +39,7 @@ or HSI (hue, saturation, intensity) space.</para>
to be saved from. If not given, the environment variable
<acronym/><emphasis remap="B">FB_FILE</emphasis> is used
to select the display device (see
<citerefentry><refentrytitle>brlcad</refentrytitle><manvolnum>1</manvolnum></citerefentry>). If
<emphasis remap="I">brlcad(1)</emphasis>). If
<acronym/><emphasis remap="B">FB_FILE</emphasis> has not
been set, the default device for your system will be
used.</para>
+2 -2
View File
@@ -45,9 +45,9 @@ The
<option>-H</option>
option is for editing
1024x1024 or high resolution
(<emphasis remap='SM'>HIRES</emphasis>)
<emphasis remap='SM'>(HIRES)</emphasis>
images; the default is low resolution, 512x512
(<emphasis remap='SM'>LORES</emphasis>).
<emphasis remap='SM'>(LORES)</emphasis>.
The frame buffer's state can be toggled back and forth between
<acronym>HIRES</acronym>
and
+1 -1
View File
@@ -22,7 +22,7 @@
<refsection xml:id="description"><title>DESCRIPTION</title>
<para><command>Fbfree</command>
<para><emphasis remap="I">Fbfree</emphasis>
is used to free any resources associated with a frame buffer.
Its most common use is to close down an
<citerefentry><refentrytitle>fbserv</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+2 -2
View File
@@ -62,9 +62,9 @@ result of this is the ability saturate or desaturate an arbitrary
colormap.</para>
<para>By default, the display is assumed to be 512x512 pixels;
if the
by specifying the
<option>-H</option>
flag is specified, the size is changed to 1024x1024.
flag, the size is changed to 1024x1024.
This size distinction is important for devices like the Adage
framebuffers which have different operating modes based on the
display size.
+1 -1
View File
@@ -26,7 +26,7 @@
<refsection xml:id="description"><title>DESCRIPTION</title>
<para><command>fbgrid</command>
<para><emphasis remap="I">Fbgrid</emphasis>
is used to generate a grid on a frame buffer.
The environment
variable
+6 -6
View File
@@ -22,22 +22,22 @@
<refsection xml:id="description"><title>DESCRIPTION</title>
<para><command>fbhelp</command>
<para><emphasis remap="I">Fbhelp</emphasis>
displays information about the selection of frame buffer devices
available to the
<citerefentry><refentrytitle>libfb</refentrytitle><manvolnum>3</manvolnum></citerefentry>
frame buffer library and the whole family of
<emphasis remap="B">fb</emphasis>
<emphasis remap="B">fb∗</emphasis>
programs in the BRL-CAD package, for the machine
<command>fbhelp</command>
is run on.</para>
<para>The display device used by a program is taken first from the
<option>-F </option><replaceable>framebuffer</replaceable>
<para>The display device used by a program is taken first from a
<option>-F </option><replaceable>framebuffer</replaceable>
option if given, else from the environment variable
<emphasis remap="SM">FB_FILE</emphasis>,
<emphasis remap="SM">FB_FILE,</emphasis>
or finally from whatever the default display is for that system.
<command>fbhelp</command>
<emphasis remap="I">Fbhelp</emphasis>
will tell you what the available choices of frame buffers are,
as well as detailed information about any options the currently
selected device may have.</para>
+18 -15
View File
@@ -24,7 +24,7 @@
<refsection xml:id="description"><title>DESCRIPTION</title>
<para><command>fbpoint</command>
<para><emphasis remap="I">Fbpoint</emphasis>
allows you to move a non-destructive cursor around on the display.
As the cursor is moved around,
<command>fbpoint</command>
@@ -33,7 +33,7 @@ at by the cursor, and the red, green, and blue values of that
pixel, on standard error
<command>fbpoint</command>
also writes the last set of coordinates pointed to on standard out on exit.
The starting position is center-screen unless optional
The starting position is center-screen unless an optional
<emphasis remap="I">initx inity</emphasis>
is given.</para>
@@ -42,23 +42,24 @@ is given.</para>
``<emphasis remap="B">j</emphasis>'',
``<emphasis remap="B">k</emphasis>'',
and
``<emphasis remap="B">l</emphasis>''
``<emphasis remap="B">l</emphasis>'',
commands step the cursor one pixel left, down, up, or right respectively, and
the
``<emphasis remap="B">H</emphasis>'',
``<emphasis remap="B">J</emphasis>'',
``<emphasis remap="B">K</emphasis>'',
and
``<emphasis remap="B">L</emphasis>''
commands step the cursor in the corresponding directions in big increments.
``<emphasis remap="B">L</emphasis>'',
commands step the cursor in the corresponding direction in big increments.
The
``<emphasis remap="B">B</emphasis>'',
``<emphasis remap="B">N</emphasis>'',
``<emphasis remap="B">P</emphasis>'',
``<emphasis remap="B">P</emphasis>''.
and
``<emphasis remap="B">L</emphasis>'',
and
``<emphasis remap="B">^B</emphasis>'' (control-B),
``<emphasis remap="B">^B</emphasis>'',
(control-B),
``<emphasis remap="B">^N</emphasis>'',
``<emphasis remap="B">^P</emphasis>'',
and
@@ -69,9 +70,9 @@ are also little and big (respectively) cursor movement commands.</para>
``<emphasis remap="B">?</emphasis>''
prints a short command summary,
and typing
``<emphasis remap="B">q</emphasis>''
``<emphasis remap="B">q</emphasis>'',
or
``<emphasis remap="B">Q</emphasis>''
``<emphasis remap="B">Q</emphasis>'',
exits the program.</para>
<para>Using this program with grave accents in a shell script in order to
@@ -90,19 +91,21 @@ This is to facilitate passing the output of this program as
arguments to another.</para>
</refsection>
<refsection xml:id="example"><title>EXAMPLES</title>
<refsection xml:id="example"><title>EXAMPLE</title>
<para><command>fbpoint</command>
<!-- .br -->
by itself is used to pick coordinates or pixel values from a display.</para>
<para>fbscanplot `fbpoint -y`</para>
<para>allows you to choose the scanline to plot using fbpoint.</para>
<para><emphasis remap="I">fbscanplot `fbpoint -y`</emphasis>
<!-- .br -->
allows you to choose the scanline to plot using fbpoint.</para>
<para>pix-fb `fbpoint -x-X -y-Y` <emphasis remap="I">file.pix</emphasis></para>
<para>allows you to select an x, y screen coordinate location and then
<para><emphasis remap="I">pix-fb `fbpoint -x-X -y-Y` file.pix</emphasis>
<!-- .br -->
will allow you to select an x, y screen coordinate and then
place the lower left corner of the image
<emphasis remap="I">file.pix</emphasis>
there.</para>
at that location.</para>
</refsection>
<refsection xml:id="see_also"><title>SEE ALSO</title>
+4 -3
View File
@@ -101,14 +101,15 @@ the selected line.</para>
<para><userinput>fbscanplot -v -W512 -o `fbpoint -y` &gt; scan.out</userinput>
<!-- .br -->
will use
<command>fbpoint</command>
<emphasis remap="I">fbpoint</emphasis>
to select a y scanline, then plot 512 pixel values
in overlay mode. These values will also be saved in the file
<emphasis remap="I">scan.out</emphasis>
for closer examination.</para>
<para>A handy C-shell alias is:</para>
<para>alias fbsp 'fbscanplot -r `fbpoint -y`'</para>
<para>A handy C-shell alias is:
<!-- .br -->
<emphasis remap="I">alias fbsp 'fbscanplot -r `fbpoint -y`'</emphasis></para>
</refsection>
<refsection xml:id="see_also"><title>SEE ALSO</title>
+2 -2
View File
@@ -67,7 +67,7 @@ command may be executed by users at a shell prompt, or it may be used as
an inetd remote framebuffer server by specifying
<command>fbserv</command>
as a server program in
<emphasis remap='B'>inetd.conf</emphasis> .</para>
<emphasis remap='B'>inetd.conf.</emphasis></para>
</refsect1>
<refsect1 xml:id='examples'><title>EXAMPLES</title>
@@ -90,7 +90,7 @@ with it. Any access of a framebuffer specifying port 0 will use the already open
<para><citerefentry><refentrytitle>bw-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>cat-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>cell-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>cmap-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>gif-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>plot3-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>polar-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>rle-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>fbcmap</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbcmrot</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbclear</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbcbars</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbanin</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbcolor</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbfade</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbframe</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>fbfree</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbgamma</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbgrid</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbhelp</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fblabel</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbline</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbpoint</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbscanplot</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>fbstretch</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbzoom</refentrytitle><manvolnum>1</manvolnum></citerefentry></para>
<citerefentry><refentrytitle>fbstretch</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>fbzoom</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
+5 -4
View File
@@ -170,16 +170,17 @@ are a good example of this.</para>
<refsection xml:id="example"><title>EXAMPLE</title>
<para>The following procedure enlarges an image,
obtained from a personal computer via the
<command>gif-fb</command>
<replaceable>gif-fb</replaceable>
utility,
to fill a 1280-by-1024 frame buffer.</para>
<blockquote remap="RS">
<para>$ gif-fb <emphasis remap="P-&gt;I">image.gif</emphasis> # displays the 320x200 PC image</para>
<para>$ fbstretch -w 320 -n 200 -W 1280 -N 1024</para></blockquote> <!-- remap='RE' -->
<para><emphasis remap="I">$</emphasis> gif-fb image.gif # <emphasis remap="P-&gt;I">displays the 320x200 PC image</emphasis>
<!-- .br -->
<emphasis remap="I">$</emphasis> fbstretch -w 320 -n 200 -W 1280 -N 1024</para></blockquote> <!-- remap='RE' -->
</refsection>
<refsection xml:id="see_also"><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>gif-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>mandel</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pixscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>libfb</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry></para>
<para><citerefentry><refentrytitle>gif-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>mandel</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>pixscale</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>libfb</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsection>
<refsection xml:id="diagnostics"><title>DIAGNOSTICS</title>
+2 -2
View File
@@ -25,11 +25,11 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>firpass</command> is an interactive program used to create a PRISM ready input
<para>Firpass is an interactive program used to create a PRISM ready input
file (when used in conjunction with secpass), a generic thermal data
file, or a
geometric properties file. The following information about each region
of the mged description may be obtained from <command>firpass</command> when creating a
of the mged description may be obtained from firpass when creating a
PRISM ready file.</para>
<literallayout remap='.nf'>
+2 -2
View File
@@ -32,7 +32,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-acad</command>
<para><emphasis remap='I'>g-acad</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -75,7 +75,7 @@ option specifies the number of CPU's to be used, and also turns on a flag to ena
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-acad -o <emphasis remap='I'>sample.ACAD sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-acad -o sample.ACAD sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+4 -4
View File
@@ -33,7 +33,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-dxf</command>
<para><emphasis remap='I'>g-dxf</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -50,7 +50,7 @@ option specifies an NMG debug flag. The
option may be used to specify an absolute tessellation tolerance (in millimeters). This
requires that the maximum absolute error from the tessellated surface to the actual
surface must not be greater than
<emphasis remap='I'>abs_tol</emphasis>.
<emphasis remap='I'>abs_tol.</emphasis>
The
<option>-n</option>
option specifies a surface normal error tolerance (in degrees) for the tessellation.
@@ -59,7 +59,7 @@ The
option may be used to set a relative error tolerance. This effectively
sets an absolute tolerance for each primitive solid by multiplying the
overall size of the solid by
<emphasis remap='I'>rel_tol</emphasis>.
<emphasis remap='I'>rel_tol.</emphasis>
The
<option>-D</option>
option specifies a calculational distance tolerance (mm). Any two vertices
@@ -84,7 +84,7 @@ option specifies the name of the file to receive the output
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-dxf -o <emphasis remap='I'>sample.dxf sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-dxf -o sample.dxf sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+14 -9
View File
@@ -16,14 +16,14 @@
<!-- body begins here -->
<refsynopsisdiv xml:id='synopsis'>
<cmdsynopsis>
<command>g-egg</command><arg choice='opt'>-v89</arg>
<command>g-egg</command><arg choice='opt'>-8 </arg>
<arg choice='opt'>-xX <replaceable>lvl</replaceable></arg>
<arg choice='opt'>-D <replaceable>calculation_tolerance</replaceable></arg>
<arg choice='opt'>-a <replaceable>abs_tol</replaceable></arg>
<arg choice='opt'>-r <replaceable>rel_tol</replaceable></arg>
<arg choice='opt'>-n <replaceable>norm_tol</replaceable></arg>
<arg choice='opt'>-D <replaceable>calculation_tolerance</replaceable></arg>
<arg choice='opt'>-o <replaceable>EGG_file</replaceable></arg>
<arg choice='opt'>-P <replaceable>number_of_CPUs</replaceable></arg>
<arg choice='opt'>-n <replaceable>norm_tol</replaceable></arg>
<arg choice='opt'>-o <replaceable>EGG_file</replaceable></arg>
<arg choice='plain'><replaceable>database.g</replaceable></arg>
<arg choice='plain'><replaceable>object(s)</replaceable></arg>
</cmdsynopsis>
@@ -31,7 +31,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-egg</command>
<para><emphasis remap='I'>g-egg</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -44,8 +44,10 @@ The
option specifies an RT debug flag and the
<option>-X</option>
option specifies an NMG debug flag. The
<option>-a</option>,
<option>-r</option>, and
<option>-a</option>
,
<option>-r</option>
, and
<option>-n</option>
options specify tessellation tolerances.
The
@@ -54,7 +56,10 @@ option specifies a calculational distance tolerance (mm). Any two vertices
that are less than this distance apart will be treated as the same vertex.
The
<option>-v</option>
option requests verbose output, which goes to standard error.
option requests verbose output.
The
<option>-i</option>
option requests the output file units to be inches (the default is mm).
The
<option>-o</option>
option specifies the name of the file to receive the output
@@ -70,7 +75,7 @@ option specifies the number of CPU's to be used.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-egg -o <emphasis remap='I'>sample.egg sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-egg -o sample.egg sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+2 -2
View File
@@ -29,7 +29,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-euclid</command>
<para><emphasis remap='I'>g-euclid</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -59,7 +59,7 @@ option specifies the name of the file to receive the output
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-euclid -o <emphasis remap='I'>sample.euclid sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-euclid -o sample.euclid sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+11 -11
View File
@@ -33,11 +33,11 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-iges</command>
<para><emphasis remap='I'>g-iges</emphasis>
converts the specified objects of the BRL-CAD database,
<emphasis remap='I'>database.g</emphasis>,
<emphasis remap='I'>database.g,</emphasis>
to an IGES version 5.1 file,
<emphasis remap='I'>file.iges</emphasis>.</para>
<emphasis remap='I'>file.iges.</emphasis></para>
<para>The following options are recognized</para>
@@ -139,8 +139,8 @@ this way).</para>
<para>If neither the -f , -t , nor the -m options are selected,
the default is a CSG IGES file. In this situation, all regions will be
written to the IGES file as Boolean trees with all possible solids
represented by their IGES CSG equivalent. In cases where there is no IGES
written to the IGES file as Boolean trees with all possible solids rep-
resented by their IGES CSG equivalent. In cases where there is no IGES
CSG equivalent, the BRL-CAD solid is tesellated (using the provided
tolerances), and a BREP object is written for that solid.</para>
@@ -148,21 +148,21 @@ tolerances), and a BREP object is written for that solid.</para>
</refsect1>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<para>g-iges -f -o <emphasis remap='I'>gsample.iges sample.g object1</emphasis></para>
<para><emphasis remap='I'>g-iges -f -o sample.iges sample.g object1</emphasis></para>
<para>This command will produce an IGES BREP output file,
<emphasis remap='I'>sample.iges</emphasis>,
<emphasis remap='I'>sample.iges,</emphasis>
from
<emphasis remap='I'>object1</emphasis>
of the BRL-CAD database file
<emphasis remap='I'>sample.g</emphasis>.</para>
<emphasis remap='I'>sample.g.</emphasis></para>
</refsect1>
<refsect1 xml:id='see_also'><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>iges-g</refentrytitle><manvolnum>1</manvolnum></citerefentry>
<para><citerefentry><refentrytitle>iges-g</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
<!-- .br -->
<emphasis remap='I'>The Initial Graphics Exchange Specification (IGES) Version 5.1</emphasis>,
IGES/PDES Organization, September 1991</para>
<emphasis remap='I'>The Initial Graphics Exchange Specification (IGES) Version 5.1,</emphasis>
IGES/PDES Organization, September 1991.</para>
</refsect1>
<refsect1 xml:id='diagnostics'><title>DIAGNOSTICS</title>
+6 -4
View File
@@ -32,7 +32,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-nff</command>
<para><emphasis remap='I'>g-nff</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -45,8 +45,10 @@ The
option specifies an RT debug flag and the
<option>-X</option>
option specifies an NMG debug flag. The
<option>-a</option>,
<option>-r</option>, and
<option>-a</option>
,
<option>-r</option>
, and
<option>-n</option>
options specify tessellation tolerances.
The
@@ -70,7 +72,7 @@ option specifies a file for receiving the error messages.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-nff -o <emphasis remap='I'>sample.nff sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-nff -o sample.nff sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+12 -6
View File
@@ -54,7 +54,7 @@ option is not used.</para>
<para>Specify an absolute tessellation tolerance (in millimeters).
This requires that the maximum absolute error from the tessellated surface to the actual
surface must not be greater than
<emphasis remap='I'>abs_tess_tol</emphasis>.</para>
<emphasis remap='I'>abs_tess_tol.</emphasis></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -87,11 +87,11 @@ surface must not be greater than
<para>Specify a relative error tolerance. This effectively
sets an absolute tolerance for each primitive solid by multiplying the
overall size of the solid by
<emphasis remap='I'>rel_tess_tol</emphasis>.
<emphasis remap='I'>rel_tess_tol.</emphasis>
This allows small objects to be tessellated with small tolerances, while large objects are tessellated with large tolerances.
For example, specifying
<option>-r 0.1</option>
when tessellating an object 2m in size will result in a tolerance of .2m (2.0 * 0.1).
when tessellating an object 2m in size, will result in a tolerance of .2m (2.0 * 0.1).
The same option will cause a 5cm object to be tessellated with a tolerance of 0.5cm.</para>
</listitem>
</varlistentry>
@@ -118,7 +118,7 @@ can be controlled using the tessellation tolerances.</para>
<listitem>
<para>Set librt debug flags.
The definitions of these flags may be found in
<emphasis remap='I'>raytrace.h</emphasis>.</para>
<emphasis remap='I'>raytrace.h.</emphasis></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -126,7 +126,13 @@ The definitions of these flags may be found in
<listitem>
<para>Set NMG routines debug flags.
The definitions of these flags may be found in
<emphasis remap='I'>h/nmg.h</emphasis>.</para>
<emphasis remap='I'>h/nmg.h.</emphasis></para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-(</option></term>
<listitem>
<para>Set the number of CPUs.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -134,7 +140,7 @@ The definitions of these flags may be found in
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-nmg -o <emphasis remap='I'> shell.g sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-nmg -o shell.g sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+2 -2
View File
@@ -33,7 +33,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-obj</command>
<para><emphasis remap='I'>g-obj</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -93,7 +93,7 @@ option specifies a file for receiving the error messages.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-obj -o <emphasis remap='I'>sample.obj sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-obj -o sample.obj sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+2 -2
View File
@@ -37,7 +37,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-raw</command>
<para><emphasis remap='I'>g-raw</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -134,7 +134,7 @@ less than this distance apart will be treated as the same vertex.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-raw -o <emphasis remap='I'>sample.raw sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-raw -o sample.raw sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+6 -6
View File
@@ -35,7 +35,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-shell-rect</command>
<para><emphasis remap='I'>g-shell-rect</emphasis>
converts the specified
<emphasis remap='I'>objects(s)</emphasis>
from a BRL-CAD model
@@ -50,19 +50,19 @@ by specifying a desired initial ray direction using the
option (see below).
The initial shell is constructed using only the first and last
intersections with the
<emphasis remap='I'>object(s)</emphasis>.
<emphasis remap='I'>object(s).</emphasis>
This will typically result in some rather large faces with normals at right angles
to the ray direction. Unless the
<option>-n</option>
option is specified, these faces are then subdivided (according to the
<emphasis remap='I'>cell_size</emphasis>)
and additional rays fired from the other two directions are used to refine their
<emphasis remap='I'>cell_size</emphasis>
) and additional rays fired from the other two directions are used to refine their
shape.
The resulting NMG solid
will be named
<emphasis remap='I'>shell</emphasis>
and will be written to the specified
<emphasis remap='I'>brlcad_output_file</emphasis>.</para>
<emphasis remap='I'>brlcad_output_file.</emphasis></para>
<para>The following command line options are recognized:</para>
@@ -134,7 +134,7 @@ most hits first.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-shell-rect -o <emphasis remap='I'>shell.g sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-shell-rect -o shell.g sample.g sample_object</emphasis>
</synopsis>
</refsect1>
+6 -6
View File
@@ -24,11 +24,11 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-step</command>
<para><emphasis remap='I'>g-step</emphasis>
converts the specified objects of the BRL-CAD database,
<emphasis remap='I'>database.g</emphasis>,
<emphasis remap='I'>database.g,</emphasis>
to a STEP AP203 file,
<emphasis remap='I'>output_file.stp</emphasis>.</para>
<emphasis remap='I'>output_file.stp.</emphasis></para>
<para>The following options are recognized</para>
@@ -63,7 +63,7 @@ to a STEP AP203 file,
<userinput>g-step -o m35.stp m35.g</userinput>
</para>
<para>
Writes out the full hierarchy of the .g file to m35.stp .
Writes out the full hierarchy of the .g file to m35.stp.
</para>
</example>
@@ -86,7 +86,7 @@ to a STEP AP203 file,
<listitem>
<para>
<emphasis remap='I'>Recommended Practices for AP203</emphasis>
PDES, Inc. Industry consortium, April 1998
PDES, Inc. Industry consortium, April 1998.
</para>
</listitem>
</varlistentry>
@@ -95,7 +95,7 @@ to a STEP AP203 file,
<listitem>
<para>
<emphasis remap='I'>Usage Guide for the STEP PDM Schema V1.2</emphasis>
PDM Implementer Forum, Release 4.3, January 2002
PDM Implementer Forum, Release 4.3, January 2002.
</para>
</listitem>
</varlistentry>
+2 -2
View File
@@ -38,7 +38,7 @@
<refsect1 xml:id='description'><title>DESCRIPTION</title>
<para><command>g-stl</command>
<para><emphasis remap='I'>g-stl</emphasis>
converts the specified
<emphasis remap='I'>object(s)</emphasis>
from a BRL-CAD
@@ -144,7 +144,7 @@ less than this distance apart will be treated as the same vertex.</para>
<refsect1 xml:id='example'><title>EXAMPLE</title>
<synopsis>
$ g-stl -o <emphasis remap='I'>sample.stl sample.g sample_object</emphasis>
$ <emphasis remap='I'>g-stl -o sample.stl sample.g sample_object</emphasis>
</synopsis>
</refsect1>

Some files were not shown because too many files have changed in this diff Show More