Old bugs and V4

contact lost
contact lost
in Other

I am using V3.3.0016. Following is a list and description of repeatable bugs I have been complaining about for some time. Most of these go back to V2.2.0010 or earlier. Is there any reason to believe they have been addressed by V4?LEADER dimensioning Bug: With the new leader command (V3.1), where the line is one entity, if you mirror the leader and text the tail (short horizontal line between the leader and text) disappears. If you UNDO the tail is still gone (so it did not really undo). If you use STRETCH to move the dimension to the other side, effectively mirroring it (not always appropriate esp. if you need to mirror a whole part to make a left hand of a right and there are several leaders in the drawing) then the text is not on the desired side of the tail and needs to be moved independent of the STRETCH. And the text justification is technically not right and needs to be edited.Of course it you EXPLODE the leader (thus returning it to how it was before the command was “improved”) the text location, justification and tail mirror just fine.STRETCH command Bug:If you stretch a broken line type (HIDDEN, DASHED, PHANTOM, etc.) and your selection window crosses the line in a broken section, the line is ”moved” instead of “stretched”. One often finds it necessary to use a crossing poly line or a zoom (or both) to insure crossing the solid part of the line.DTEXT Bugs:When you edit a DTEXT entity via ENTITY PROPERTIES and change the text justification there is inconsistent behavior.If the text entity is changed to LEFT it adjusts the insert point relative to the text so the text stays exactly where it was.If the entity is changed to RIGHT, MIDDLE, etc. (not LEFT) it leaves the insert point in the same place and moves the text to suit. If you change text to right then left then right then left it moves across the screen.This inconsistency is irritating but the worst problem is when you edit several entities of DTEXT at the same time and change the justification from LEFT to RIGHT, MIDDLE etc. it reassigns all the insert points to 0,0,0 (some times another common point). This is hardly acceptable!I have not tried all the justification combinations to see if any other odd behavior exists.MTEXT Justification Bug:When an MTEXT entity with “middle center” justification has one line of text, the vertical center is centered with the text (as it should be).When there are two lines of text it is centered between the lines (as it should be).When there are three lines it centers between the first and second lines instead of centering on the second (middle) line of text.When there are four lines of text it is centered between the second and third lines (as it should be).When there are five or more lines it centers between the second and third lines instead of centering on the middle line of text or between the two middle lines (if even number of lines).This forces one to move the text up on a vertical dimension to fit between the dimension lines (which are created with the right gap for the actual number of lines but the text is not centered on them, the insert point is).Some other justifications also behave oddly.POLY LINE/ENDPOINT Snap Bug:When any OSNAP is on (other than ENDPOINT), IntelliCAD acts as though ENDPOINT is on (even when it’s off) so far as multi segment poly lines (any intersection of joined poly line segments) are concerned. DRAWING SETTINGS Bug:The undo controls the (DRAWINGS SETTINGS, DISPLAY, PROGRAM INTERFACE, UNDO CONTROLS) will not save and must be reset from default for every drawing every time you bring it up.TOOLBAR IMPORT Bug:When you import a custom tool bar (.MNU file), IntelliCAD fails to import it correctly. It brings in the bars but all the button icons are the same (custom button 7). Every time a new revision is installed they have to be reconstructed.Icons I created outside IntelliCAD (bitmap) import fine.

Comments

  • contact lost
    contact lost

    Hello Jeff,please read below for the status of the points you mention> I am using V3.3.0016. Following is a list and> description of repeatable bugs I have been> complaining about for some time. Most of these go> back to V2.2.0010 or earlier. Is there any reason to> believe they have been addressed by V4?> > > LEADER dimensioning Bug:> > With the new leader command (V3.1), where the line is> one entity, if you mirror the leader and text the> tail (short horizontal line between the leader and> text) disappears. If you UNDO the tail is still gone> (so it did not really undo).This is fixed> > If you use STRETCH to move the dimension to the other> side, effectively mirroring it (not always> appropriate esp. if you need to mirror a whole part> to make a left hand of a right and there are several> leaders in the drawing) then the text is not on the> desired side of the tail and needs to be moved> independent of the STRETCH. And the text> justification is technically not right and needs to> be edited.I don't understand this part. The mirror command for leaders was partly fixed: in intellicad 3 the original leader followed to the mirrored text, while the mirrored leader did not react.Not anymore, but the mirrored leader stores the wrong(it stores the previously non mirrored coordinates) coordinates to the text. and you have to correct the mirrored leader (once) if you move the mirrored text.> > STRETCH command Bug:> > If you stretch a broken line type (HIDDEN, DASHED,> PHANTOM, etc.) and your selection window crosses the> line in a broken section, the line is ”moved” instead> of “stretched”. This is fixed> > DTEXT Bugs:> > When you edit a DTEXT entity via ENTITY PROPERTIES> and change the text justification there is inconsistent behavior.> > If the text entity is changed to LEFT it adjusts the> insert point relative to the text so the text stays exactly where it was.> > If the entity is changed to RIGHT, MIDDLE, etc. (not LEFT) > it leaves the insert point in the same place and moves the text to suit.> If you change text to right then left then right then left it moves across> the screen.This is not fixed.> > This inconsistency is irritating but the worst problem is > when you edit several entities of DTEXT at the same time > and change the justification from LEFT to RIGHT, MIDDLE etc. > it reassigns all the insert points to 0,0,0 (some times another common point).> This is hardly acceptable!It's not fixed.> > I have not tried all the justification combinations> to see if any other odd behavior exists.> > > MTEXT Justification Bug:> > When an MTEXT entity with “middle center”> justification has one line of text, the vertical> center is centered with the text (as it should be).> > When there are three lines it centers between the> first and second lines instead of centering on the> second (middle) line of text.> > When there are five or more lines it centers between> the second and third lines instead of centering on> the middle line of text or between the two middle> lines (if even number of lines).> > This forces one to move the text up on a vertical> dimension to fit between the dimension lines (which> are created with the right gap for the actual number> of lines but the text is not centered on them, the insert point is).This is fixed > POLY LINE/ENDPOINT Snap Bug:> > When any OSNAP is on (other than ENDPOINT),> IntelliCAD acts as though ENDPOINT is on (even when> it’s off) so far as multi segment poly lines (any> intersection of joined poly line segments) are> concerned.In AutoCAD, vertices of a polyline show up with on intersection snap.These snap points get the intersection snap marker. IntelliCAD shows an endpoint marker instead.This seems defendable, though it does cause confusion if an endpoint marker shows instead of an intersection marker.Another difference is that IntelliCAD also uses these vertex snap points when they are outside the aperture.We're changing this now so IntelliCAD uses the intersection marker for vertices, and only if they fall inside the aperture.> > > DRAWING SETTINGS Bug:> > The undo controls the (DRAWINGS SETTINGS, DISPLAY,> PROGRAM INTERFACE, UNDO CONTROLS) will not save and> must be reset from default for every drawing every> time you bring it up.This is not fixed and it is still not a priority. We mentioned before that it's very easy to handle though: add one or two lines in icad.lsp to set UNDOCTL.You can't set UNDOCTL directly so you have to call the UNDO command with options Auto/Control> > > > TOOLBAR IMPORT Bug:> > When you import a custom tool bar (.MNU file),> IntelliCAD fails to import it correctly. It brings in> the bars but all the button icons are the same (custom button 7). > Every time a new revision is installed they have to be reconstructed.> > Icons I created outside IntelliCAD (bitmap) import fine.> Do you mean the problem that export of toolbar ignored the names of toolbar icons?This problem is fixed.regards, sander

This discussion has been closed.