Petri

quote: Originally posted by ApocHalyptic: [ Being able to simply select an object and adjust its transparency is a major bonus when tracing over AirPhotos. A transparency slider is the simplist means of acomplishing this. Try layer transfer modes for this. Very simple and works for me for the exact purpose. quote: 3. Linking objects to their position in 2D space.Sounds very problematic considering the overall design of the coordinate system - can't really follow your thought (although I do a fair bit of mapping. In essence, a User Coordinate System is what you are after, or? quote: No, Azimuth is not the answer to mapping on VW. UTM and meter coordinates are not supported by Azimuth and they have no wish to support this tremendously popular grid system in resource industries. Are you saying that Azimuth does not work with metric units? (I'm not a geographist, just need to produce "mapping" as a part of my work, so I may not know what you refer to.)

Instead of the silly and incomprehensible 'Style-1' etc., one can and SHOULD change the pop-up menu items to suit their particular way of working. So, for glass, I for instance have 'Mat[erial]Glass-Clear', 'Mat-Glass-Grey' and 'Mat-Glass-Opaque' and for frames 'Mat-Timber', 'Mat-Aluminium' etc. Well, along these lines. This is done via menu command 'Create Polug-in': - scroll to the PIO in question and select it - click 'Parameters' - scroll to the field in question - click 'Edit' - click 'Values' - replace the list with your own list - click 'OK' - select 'Default' to be what you want - click 'OK', 'OK' and 'Done' (unless you want to make similar changes to other PIOs. Note that you can also edit the default dimensions here, like from Imperial to metric. Then I have standard classes with those names and the appropriate graphic attributes. In addition, quite often, instead of changing the glazing style, I use 'canned' class definition files to change the class attributes eg. so that all glazing is about 70% transparent - or whatever. These class definition files are easily created by my free utility on the VectorDepot. (http://www.vectordepot.com/PlugIns1.shtml - 'Cloning around') [ 01-30-2004, 08:12 PM: Message edited by: Petri ]

quote: Originally posted by jan15: No equivalent to AC Attributes Knowing very little about AutoCAD... The (superior) equivalent is, AFAK, the data record (or format, in the current lingo.) A very informative post, Jan15!

quote: Originally posted by Andrew Bell@NNA: Conceivably we could tag the last one used, however, until you perform some action that is incompatible with that sheet transition. I think this would be quite an improvement, especially when one is generating a large number of prints. Now one has to jot down notes manually and all too often, I print two sets of one sheet. With, say, 10 copies, it is 'slightly' irritating...

Have you tried a rotated snap grid?

The layer scale you use in VW has no effect in AutoCAD export. Unless you actually scale objects, you always work in 1:1 scale in VW. I have exported hundreds of VW documents to AutoCAD and never had this problem.

Hmmmm - when was it when I requested it? Probably right after moving back to MiniCAD after a few years with ArchiCAD - so that is close to 10 years now. At the time, Rich himself was occasionally present on the CompuServe MiniCAD forum...

Answer received, but the problem still has not been solved. There is something strange in this: the test script works, but in the real thing, long file names still fail.

(Sorry for cross-posting, but this is really an important & urgent thing!) In a very specific system for a client, I need to generate a series of text files, automatically named. The syntax & circumstances may result in quite long names and on the Mac OS9 platform (my development platform), I realise that they exceed the maximum allowed length. Unfortunately, the same seems to be the case on the Windows platform (the client's platform.) When the name string exceeds the Mac filename limitation, export fails. Is anyone on Windows kind enough to run this script and report how many 'abc's they get? This is really puzzling! PROCEDURE test; VAR i, n : INTEGER; output, fName, addition : STRING; BEGIN PUTFILE('Data set name', GETFNAME, output); addition := ' abc'; FOR i := 1 TO 10 DO BEGIN REWRITE(output); output := CONCAT(output, addition); WRITELN(i); CLOSE(output); END; END; RUN(test); TIA!

The easy way is to use my free 'Cloning around' utility from http://www.vectordepot.com/PlugIns1.shtml

I realise that this topic is old and long already. No offence to anyone, but trying to reduce complexity by adding more complexity does not sound good. As has been noted, the Saved Sheets almost provice a third dimension to the layer/class matrix. Pity that editing this dimension is so awkward to use in unpredictable projects where you create new layers and classes. For some expressed and implied 'needs' for added functionality, there is another solution that I have advocated for years: each creation tool should have its own default (user-defined) class - perhaps also other preferences. The former already exists for PIOs, well, after a fashion, as it is in the Create Plug-in, not in Preferences of the object tool. So, text would automatically go to the designated class, lines to another, polygons perhaps to a third.

I'm afraid it's not possible. Can you use other formats (like EPSF)? The support for vector PICTs was ever good or broad. Apart from Apple/Claris, everyone considered it as a raster format. Can't really remember what Claris CAD (and the Claris CAD Translator) did, but what you say seems likely. What you can then do with the vector PICT is another story.

AEC - well, I would never have thought of that. It is not a plug-in which really did not make things easier. Thanks!

Curiouser and curiouser. Can't find it anywhere (not even with a Sherlock search.)

No, not even with VectorScript as long as we are talking about symbols. PIOs are an entirely different pot of tofu.

The issue was brought up on the Architosh forum - and now I am more than slightly curious. Whatever happened to the Number Stamp tool? Is it still there, and if so, where?

The issue was brought up on the Architosh forum - and now I am more than slightly curious. Whatever happened to the Number Stamp tool? Is it still there, and if so, where?

I did try - in fact, before my first post in this thread. No joy. Copied and pasted the data into a new document, based on the template and still nothing but blue.

Hmm - quite a few interesting (even to me) additions. Some aspects are puzzling: SymbolToGroup says that it "Converts referenced symbol to group using the specified conversion options." I can't find these options anywhere.

Although a few times* I was able to generate a DTM in VW 9, slope analysis never worked. Tested just with VW 10 demo version and the same still applies. Regardless of settings, the only colour is blue (I tried down to 1 degrees - and there are slopes to 1:6!) Has anyone ever been able to do a slope analysis, with any version of VW? *) more often than not, I got nothing. Data were good.

Hello, jnr! While I am definitely frustrated with the lack of built-in ODBC support (and even more so with the fact that the 3rd party solutions only support Windows), I can't really relate to your comments about the unreliability of the database component of VW. Besides, if your database structure would actually be ODBC-compliant (containig a unique ID), with a couple of relatively simple scripts, you could generate fully editable reports. I don't want to let NNA off the hook - it would be lovely to be able to edit data in a standard report. However, unique object names should still be required. The UI for these could be improved - as I understand, objects do not have an intrinsic, permanent object ID. This may be a serious shortcoming in VW.

Stevie Wonder made some very pertinent comments about this some 30 years ago... However, I have expericenced exactly the same problem, but - oddly enough - not every time / in every file. I can't even establish a correlation between the 'real' origin and page centre - a lot of my files have origins millions of miles (almost) from the page centre and some behave OK, some behave badly. Not much of a solution... commiserations.