patman

Hi Peter, Why are you wanting to use the DMTBN call? If you want to work on objects within a group then get a handle to the group you want and use FInGroup() to get to the first object. With that handle you can scroll through the list of objects within using NextObj(). Once it returns NIL then your at then end of the list of objects inside that group. Does this make sense? I would avoid using DMTBN if there is any other way to do it. If you spell out more clearly what you want to do I may be able to help you further... Patrick

Hi Jeff, I too am wanting to make the switch but am a little worried about the complexities of moving from VS to the SDK. I hope to do this soon with a comitment to getting CW. Is there or can you give me a sample of a path object to get started? I have experience with using C and CW in the past so I feel good about doing it...Just looking for a little push with a working example. Can you help me out? Are there any plans to support Xcode dev environment? Hi Raymond, Have you taken the plunge? Thanks! Patrick

The slow OIP happens when you make an edit and then move the mouse. If you you wait to move the mouse until after the OIP has updated it will take far less time. NNA is aware of the details of the slow OIP problem and I expect a fix soon. As for the other issues of slow screen redraws. Here's the scoop. OS9 uses the processor to calculate the position of pixels on the screen. This rasterization of the file is not a simple task. Plotter software is slow for the same reasons, it is not a simple task. OSX asks the video card to perform this task. Most video cards processors are not as fast as the main CPU so the switch will affect the performance. What it boils down to is if you are running large files with new software on an old video card then you will have issues. I recommend using class or layer visibility to filter down the number of objects your trying to display and get a fast video card. As for the G5 not performing: the 1.8Mhz G5 is only 28% faster than my 1.4Ghz G4. That is not a perceivable difference. VW is not a 64 bit app or written for DP. So I am not sure why you would expect to be blown away. Once VW is compiled specifically for the G5, becomes multi-threaded and then you test it on a fast G5 like the 2.5Ghz you will notice an improvement. HTH Patrick

I do not show doors and windows on the RCP. So I turn those classes off. That leaves an unsightly gap in the wall as the wall break does not have a class. So my solution was to write a simple linear PIO that I call the Header Tool. It draws a centerline that can be used by the framing sheet and a polygon that can infill the wall break on the rcp. Each part is classed. You can do the same thing with a group containing the same things. Let me know if your interested in the tool... Patrick

Hi Larry, I have written a Parapet Tool. It is a path PIO that draws parapets and canales in 2D and 3D. You can specify the profile of the parapet and class all the objects so that they can be textured. If you want more info on this tool please email me off list. I am looking for beta testers for a 1.0 release of this tool scheduled for next month. Thanks Patrick patman@cybermesa.com

What is the point of gray layers. There usefulness ecapes me. They can't be selected, plotting is variable and the same thing can be accomplished with simply using light line weights. I think grayed layers and classes should be gotten rid of.

If you have a cantainer object who's class is visible but where the contents are not visible you can Select, Delete and Trim to these objects. This makes absolutly no since to me...

I have a simple 'Print B&W' command that does what you want. It sets up some prefs including B&W only and also updates any stamps you have. I can send you a copy of it and your welcome to use it as a starting point...