Jump to content

Petri

Member
  • Posts

    2,011
  • Joined

  • Last visited

Everything posted by Petri

  1. quote: Originally posted by MullinRJ: Hi Zero, Posted by the Self-appointed Non-modal Editing Advocat: You wanted to say NameClass(GetClass(FSActLayer)); No variables, just one line of code, with object-verb syntax. Beeewdiful! [ 02-28-2004, 05:32 AM: Message edited by: Petri ]
  2. Obviously you first chose the 'Entire drawing' option in 'Scale object' (by default, it is not done) and then saved your file. If you happen to remember (or can deduct) what the scaling factor was, you can of course rescale.
  3. In many cases, yes, but it requires very careful planning & lots of discipline - often also some custom programming.
  4. quote: Originally posted by ApocHalyptic: I wonder, how do you deal with import another .dxf file into an existing map file? Do you simply import the NEW .dxf file into a blank document and paste the objects "in Place" in the existing map file? Do you use any layer linking? Copy & paste is the correct method. Importing DXF/DWG into a non-blank file can cause all sorts of problems.
  5. quote: Originally posted by ApocHalyptic: Moving the objects records them at a different x,y position, thus my reason for all the extra steps insuring I do not lose the x,y information. Well, if you move the objects, of course their coordinates are changed! Don't lower the river, raise the bridge: move the print page instead.
  6. Groups are put in class 'None' regardless of the class(es) of their elements or your active class. Well, not to worry: the matter was discussed over a year ago and yours truly offered a solution in the form of a script: - the group is placed in the current active class unless - all its members are in the same class in which case the group inherits that class. If you have groups with over 1000 members, you will need to change the array limit from [1..1000] to, say, [1..10000]. Old habit from the time when MiniPascal did not release memory used by arrays: I have as small arrays as possible. Don't ditch the normal Group command if you handle very large groups: this script may be a tad slow, because it needs to do a lot more work. Hope it works! Copy between the {----------} lines, say 'Create Plug-In', click 'New', type a name (eg Super Grouper); choose 'Command', click 'Script', say 'Paste', click 'OK', click 'Done'. Then use the Workspace editor to install the command (it is in category Menu commands/Miscellaneous) and possibly a keyboard shortcut. {------------------------} PROCEDURE SuperGrouper; { ? Petri Sakkinen 2002-2004 } { -- This is freeware but you may not remove the ? notice. Use at your own risk.-- } VAR i, n : INTEGER; theClass, currentClass, prevClass : STRING; objClass : ARRAY[1..1000] OF STRING; obHd, gHd : HANDLE; allTheSame : BOOLEAN; PROCEDURE StoreObjectClass; BEGIN i := i+1; currentClass := GETCLASS(obHd); objClass := currentClass; IF NOT(prevClass = currentClass) THEN allTheSame := FALSE; prevClass := currentClass; END; PROCEDURE RestoreObjectClass; BEGIN SETCLASS(gHd, theClass); obHd := FINGROUP(gHd); WHILE obHd <> NIL DO BEGIN i := i+1; SETCLASS(obHd, objClass); obHd := NEXTOBJ(obHd); END; END; BEGIN i := 0; allTheSame := TRUE; theClass := ACTIVECLASS; obHd := FSACTLAYER; prevClass := GETCLASS(obHd); WHILE obHd <> NIL DO BEGIN StoreObjectClass; obHd := NEXTSOBJ(obHd); END; GROUP; i := 0; gHd := LSACTLAYER; IF allTheSame THEN SETCLASS(gHd, currentClass) ELSE RestoreObjectClass; END; RUN(SuperGrouper); {-------------------------------} [ 02-10-2004, 07:05 AM: Message edited by: Petri ]
  7. Instead of combining, you may also use 'clip surface'. The choice depends on the overall situation, but I have had situations when 'combine' has not worked or was not convenient to use. So, you start with a simple poly that covers the entire area of the desired poly. Now, one by one, bring the other polys 'on top' (or send the new poly 'to back') and do the clipping, until you have the set of points that are not members of any of the original polygons, so to speak... well, that is the sought poly in set theory-parlance! .
  8. quote: Originally posted by ApocHalyptic: It is certainly the best means of dealing with this problem in VW, but nothing beats a live adjustment from 100% to 0% Transparency for best visualization when overlaying. Airphotos can be tricky, and there have been many errors in the past due to subtle changes in Forest Cover. Tricky indeed - I have on occastion found 'invert' to be useful for (again) the exact purpose. Also sometimes it helps to preprocess the aerial in PhotoShop. Addition: also the colour of the poly you draw has to be carefully selected. Tasteful colours often don't work... quote: The problem is, that moving the 'class' objects destroys the x,y meter positional information imported into VW. Reposition of imported objects is often necessary since objects are placed center of the document. Still not sure what happens there. In our maps, everything is geo-referenced in the Australian Mapping Grid (flat earth x/y projection). The largest area we've dealt with was over 6700 square kilometres, centroid (pseudo-centroid!) at x=1094469.298, y=5954623.723 (metres). We've moved this and that, including the print page, changed scale, imported new data sets, copied and pasted this boundary poly to yet other data sets - you name it, we've done it - and the polygon stays put in the coordinates, so the spatial information is not destroyed. In VW 8 and earlier it was a different situation (I think), not to mention the good old MiniCAD (I know). But in VW 9, everything is hunky dory. We even copy and paste aerial photos. Not sure what your 'class objects' are. You aren't importing DXF into a file that already has data, are you? That can stuff up things seriously. [ 02-08-2004, 08:12 AM: Message edited by: Petri ]
  9. 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.)
  10. 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 ]
  11. 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!
  12. 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...
  13. 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.
  14. 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...
  15. 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.
  16. (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!
  17. The easy way is to use my free 'Cloning around' utility from http://www.vectordepot.com/PlugIns1.shtml
  18. 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.
  19. 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.
  20. AEC - well, I would never have thought of that. It is not a plug-in which really did not make things easier. Thanks!
  21. Curiouser and curiouser. Can't find it anywhere (not even with a Sherlock search.)
  22. No, not even with VectorScript as long as we are talking about symbols. PIOs are an entirely different pot of tofu.
  23. 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?
  24. 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?
×
×
  • Create New...