Jump to content

TiTaNiuM sAMuRai

  • Posts

  • Joined

  • Last visited


Everything posted by TiTaNiuM sAMuRai

  1. "object snapping identifies 'arc' at the arc ends, BUT it also indicates 'centre' at the (get this):midpoints of theoretical lines which would define the curve of a bezier, exactly what happens when you Add Surface with an arc (i.e. the arc turns into a couple of beziers)" I agree that it's likely a design change, yet I'm not complaining about IT, per se (there are ups and down to both 'arc vertex' and 'corner vertex-but-rounded-sorta'). I just want to know why it says 'Centre' where it does. THAT item doesn't appear to be deliberate...
  2. ... sure, if you want to do it the 'easy' way... %-P (just came across 'Compose' this week)
  3. Unwanted bezier curves? Like a drunk person who thinks the entire world is spinning, VW thinks that your hand is moving at the time you click. Dragging a bit while you click (even during corner vertex creation) will automatically create a bezier point. An acquired subconscious micro-pause gives VW time to catch up. Or the computer. Whatever. You'll get consistent corners then. The cubic polynomial curve is not a circular arc, so the curve you make will not follow the circle exactly. You have two options:1) With corner vertices at the intersections of the circle, make a new vertex between them of type 'arc' (fillet), then drag the vertex to the centre of your circle to suit. However, this works for subtended angles of less than 180.2) With corner vertices at the intersections of the circle, slap in some beziers. The exact next step or two depend on your case, but to understand what's happening, do the following.Draw a circle. Draw a regular hexagon w/ same centre, with faces touching the circle. Draw a polyline using beziers, snapping to the hexagon's corners. ( or just convert all the hexagon's corners to bezier points). The result is a simulated circle, essentially what VW does with Add Surface.
  4. Rounded rectangles now snap (per Object constraint) to the ends of the arcs / beziers that make up the rounded corners, instead of the theoretical _corners_.Along the same line, there is an odd and inconsistent behavior from snapping to a 'composed' polygon comprised of an arc in between -- and tangent to -- two lines. Whereas the reshape command shows a theoretical corner, and I can draw out that handle as though it was an arc, and the object snapping identifies 'arc' at the arc ends, BUT it also indicates 'centre' at the (get this):midpoints of theoretical lines which would define the curve of a bezier, exactly what happens when you Add Surface with an arc (i.e. the arc turns into a couple of beziers). Why the half-half behavior? Why doesn't Compose turn an arc into an arc vertex? Does this have to do with tangency?
  5. Um, not so awesome if it doesn't help, though, right? If you need some VectorScript samples, Vector Depot has stuff, and I have a few well-commented PIO's.
  6. ... and the $ 64 000 answer is? "64k should be more than enough for everyone"
  7. You have to find the plug-in first (assuming NNA hasn't locked it). Select 'Create Plug-in' under the 'Organize' menu. Scroll down until you find the name of the PIO (simple door whatever, in this case). Click on 'Scripts...' Where there is a Rect (x1,y1,x2,y2); statement (x1 etc. are some numbers), take note of the numbers. You'll have to replace the rect( ) parameters with an expanded list in this format: Poly (x1, y1, x2, y1, x2, y2, x1, y2, x1, y1); Make sure that you have all five pairs values. I just tried it with my homemade door, and it works as I hoped it would. You end up with 2 lines instead of 1, though.
  8. Use the Enter key on the number pad instead of the Return key on the main board.
  9. I don't know if ResEdit will edit icons itself, but I can tell you it's an editor of a mac file's header information. If you don't already know, a mac file has two sorta-parallel parts (forks). The Resource fork contains all the non-data information, including icons. You can paste from the clipboard to the icon window, but I'm not sure you can edit that image within RE.
  10. The plug-in object is drawing a rectangle. There is a problem with snapping to rectangles and circles (maybe others) inside symbols (PIO's are treated much like symbols). The only sure temporary solution is to modify the PIO code (most folks wouldn't want to bother) to change the Rect( ) to a Poly ( ).
  11. 2x256. I'd be very interested to see if the DU fixes Hugo's problem, since no other apps have that problem.
  12. You can't blame the monkeys, necessarily, Joe. As with any team project, it's a team effort and is susceptible to problems all along the chain. As for my problem, it's basically as I posted.In a doc with all classes set to 'Use at Creation', and the default attribs set to ByClass, draw a line. Force the colour. Change the class of that line through the PIO. If this is the first time, you'll get a popup. Yes Always. I believe that line will pick up the colour of the new class (not sure). Later on, objects will definitely NOT pick up the new colour (i.e. will not set their colour back to ByClass -- I must do this manually). Is this something you cannot duplicate?
  13. Hey, Joe. Speaking of class attributes, try some attrib painting (eyedropper tool) while editing the 2D component of a symbol. Pick up, then paint. How many of the 4 attribs is copied? Pick up again, then paint again. One or two more attribs copied, but still not everything. Does it do the same thing for you?
  14. I'm not trying to be antagonistic, but I wonder if the dev strategy has actually addressed these issues in more than an expository manner. Improving development systems is one thing, but if you don't first identify the nature and source (the type of codewriting flaw, not just a particular line or two), how can you expect to eliminate any bug for good? I'm not sure that NNA actually has answers, even internally, to my questions.
  15. Yeesh. Buying more RAM will not solve the problem, but it will alleviate it temporarily. If a city gets too crowded, and the population is then spread out over a wider area, the people run into each other less frequently. Eventually, the population growth will result in the first problem re-appearing later. The error appears to be along the lines of a memory protection fault, meaning that the app tried to write to a location in memory that it shouldn't have. I don't know if it was system memory, memory used by other tasks or processes, or just memory already used by VW. In OS9, you'd get a type 2 error (or -2?), I think but the issue is the same. Bad code.
  16. What are the types of mods made to the vw core from 9 to 10? What sorts of bugs can we expect? What components have been switched to use native MacOS services? Will there be a difference for Windows users? Why is vw10 being made? How is NNA's dev team split between fixing 9.5 and making up 10? Who's testing 10? Will ALL fixes made to 9.x (now and onward) be incorporated (and double-checked) in 10?
  17. This appears to be an old post, but... I've seen this happen for two reasons:1) a drawing started on a PC, then continued on a Mac2) a drawing started in vw8, then converted to vw9 In either case, copy-pasting to a new document fixed the issue.
  18. PeterT: It's a problem with VW's 'speed' of working with the floating point values. It's most noticeable when watching the random numbers generated by the tape measure tool. There's the issue of out-of-synchronism between the cursor and the coordinate field updating, but the same asynchronism may have something to do with the snapping problem...
  19. Let's focus on the dialog that comes up when changing an object's class via OIP. All class attribs are set to ByClass. Then I force one attrib. Actually, someone else forces this attrib (or two or three). All classes are set to 'Use at Creation'. Without going through ALL the objects in the drawing (not quite all -- let's say Select All is not an option nor is a Custom select), HOW can I get these objects to take on (and set themselves to Byclass) the attribs of a new class, without manually setting that attrib back to ByClass? Right now, a line I drew will not change that forced attrib unless I set it back to Byclass. There are other times when a line with forced attribs would set its attribs to ByClass (and thereby take on the attribs OF that class). I'm not getting a dialog, since this drawing has likely already popped up the dialog, but I would have answered 'Yes Always'.
  20. Hm... maybe I was overlooking something... IF A AND B BUT NOT C, THEN D. ELSE IF A AND C BUT NOT B THEN E. UNLESS L. THEN F. UNLESS it's Monday...
  21. ... and there's an 'invisible' grid (possibly some 'reference' grid) that crops up when drawing a polyline, after the third point or so. It doesn't occur nearly as often as it did in 8.5.2, though...
  22. Geez! I ask the question, submit a report, but get no answer. Paranormal Joe gets one though. Unfortunately, it doesn't appear to be correct. Matt's explanation makes sense, but VW is inconsistent; sometimes it follows this, sometimes it does not. I think the same thing applies to applying attributes to groups (2 objects selected counts as a group, apparently, and sometimes a group counts as a group). A month or so ago, I thought that the 'Use at Creation' would be the key, but turning that on didn't necessarily fix the problem.
  23. "One or more operations was aborted due to lack of memory. Increase partition size." Why is this message popping up in OSX?I was trying to import a AutoCAD 200x dwg (8MB; it contained all four sheets) and the first 3 layouts (came in as paper space layers) appeared to import, more or less, but conked out on the fourth (maybe partway through the third). Oddly enough, all the model space things came across fine in the ms layer.
  24. Why doesn't the trim command work with polygons?
  • Create New...