TiTaNiuM sAMuRai

You will notice the same thing with other programs with floating tool palettes, such as Illustrator and Photoshop. This behaviour has been standard for the past four years at least, regardless of how many monitors you have.

The font worked okay, but doesn't respond to lineweights. In other words, the text strokes have a fixed width for any given text size. Applying bold helps only a little. I need something with adjustable weight, or I need a couple more fonts for different lineweights of the romans.shx. Anyone else have an idea?

send an email to me, and I'll shoot them over. email is d_clarke, then the '@' symbol, then aciarchitecture, then dot com.

That would be great! Please email it to me; I believe that Mac OS X handles any .ttf; the .ttf should be just a single standard, right? email is: d_clarke, then the '@' symbol, then aciarchitecture, then dot com.

We need a font that looks just like Roman Simplex. I'd like a TrueType, since we'd need it on both our Macs and on the prime consultant's PC's. X.3.5, regretfully VW9.5.3

I have one that will do what you want.

Set up your classes so that the lineweights and colours are in sync, then draw with all entities set to lineweight byclass.

Thanks, guys!! Kevin: I have a very simple door (fairly simple) PIO that you can have. The code is readable and shouldn't be too tough to deconstruct, if you want it.

Still looking for feedback from others, especially with respect to compatibility between v9 and v11, and between v10 and v11.

upskill? When did was this buzzword invented? One thing you'll have to think about is how much of your drafting staff is dedicated drafting staff. Many here do some drafting, but only 3 or so are real production staff. The production people may take a little time to acquaint themselves with the new way of drafting and the significant (YES it is, if you're moving from 9) differences in input. Other people who spend less time with the program, will require much more time to 'upskill' (a.k.a. 'learn new program' yeesh). If they're design staff, they'll be frustrated and want to slough off more of their small work to the production staff as a result. Food for thought. I'm in the same boat and holding off as long as I possibly can.

After doing a search, I encountered a heap of questions, a cupful of discussion, and a teaspoon of links. CADViewer is apparently $1000 to $12000 per copy, and is no longer available as a demo. (Tailor Made Software) There is a plugin available for AutoCAD, which imports dwf files to a .dwg, but it is an AutoCAD plugin only. Is anybody aware of a cheap viewer / converter that runs on the Mac?

Thanks to a list of whines -- relatively short, I'll admit -- from fellow users here about VW 10, longer than the list of relevant or important features, I've skipped VW10. I've had peace in the office with VW9.5.3 for almost 2 years. So far, I've read the following: - misbehaved preferences - non-functional wordprocessing inside text blocks - weird-ities in image imports Please add confirmed bugs (i.e. if other users note the same behaviour) here. Doubtless, there are other admins who want to be prepared when they deploy VW11, even if it isn't until 11.5.2.

VW9.5.3, MacOS 9.2.1 I remember some time ago when the office was still using OS9, that there was an issue with VW9.5.x: the 'a' key would not show up in the Workspace Editor as an assigned key. I also remember some time ago when I was trying to program the extra buttons on my Logitech: the programmability didn't quite jive with modifier keys in VW. On the OS9 computer, using the programmed button -- be it set to just the cmd key, or to maybe the cmd key + 'b' -- in VW sets the programmed back to 'a', plus any modifier key that was assigned. I checked Caps Lock, and toggling the key had no effect. I'm trying to pick the brains of fellow users. I've fixed so many problems over the past few years that I can't remember which ones I actually solved and which ones I found workarounds for. Any ideas?

If you did most of your work in version 7, you will notice slower performance. Period. From v8 to v9, there was a change in the math of the program (integers to floating point) which is, arguably, worth the slowdown.

My Panther guinea pig tells me that OS X.3.2 appears to fix the printing issue that VW9.5.3 has with X.3.0 and X.3.1. Can others corroborate (sp?) this?