Jump to content

WhoCanDo

Member
  • Posts

    402
  • Joined

  • Last visited

Posts posted by WhoCanDo

  1. I want to create an object:

    repeat

    if (MouseDown(x1, y1)) then

    begin

    moveto(x1, y1);

    x2 := x1 + 580;

    y2 := y1;

    closepoly;

    poly (30,#90,x2,#0,30,#-90);

    h := lnewobj;

    end;

    until (h <> Nil);

    and after h := lnewobj; I want to pick the object and free rotate it with the mouse around x1,y1 until I pick a second point with the mouse.

    I've tried

    repeat

    getmouse (x3, y3);

    rotatepoint (x1, y1, AngleOfRotation);

    redraw;

    until (MouseDown (x3, y3));

    but I think I am on the wrong track.

    Any suggestions please?

  2. Sorry to let this slide for such a long time. I get busy spells.

    When creating a worksheet and adding Database line and formula such as

    =('Record Name'.'Field Name')

    I would normally turn the database headers off.

    After adding serveral database lines to the worksheet and then adding the records to the objects on the drawings you can "Recalculate" the database.

    All objects on the drawing with records will list and the database lines that don't have records recorded on drawing objects are invisable (don't list).

    These empty (invisable) lines are made visable when exporting to .dwg which is not correct. Only the visable line items should export.

    When I have a worksheet that includes 20 database lines but only one record is used, the result shows a number of items on the drawing with different lengths & widths on different lines correctly.

    After export the line items appear as well as the other 19 unused (normally hidden) database lines.

    SP1 didn't allow metafile export and import to get around this but SP2 does. However this is not the solution to the problem.

    If anyone else can emulate the problem then I can report it as a bug to VW.

  3. I'm not totally clear on what you guys are arguing about or what you are actually saying (95017 ????) but has anyone answered my question yet?

    All I am asking VW to do is pick the double line tool, show the setup window and then let me use the tool as normal.

    I am guessing from above that you can't do this so utilising your expert VW skills instead of your expert arguing skills can someone give me a suggestion (without being rude).

    Maybe this should not be a tool type?

  4. This simple macro, which makes it easier for me to draw parallel lines throughout the day, works as a macro in Vectorscript Palettes but does not work properly as a tool.

    1. I want the StrDialog question before the tool activates. Why in Vectorscript Palettes does the StrDialog activate first but as a tool it activates after the first point is selected?

    2. Hovering over an object vertex and then moving away shows extension lines. In the Vectorscript Palettes if the mouse moves slightly off the extension line and then pick a point, the picked point is actually along the extension line (ie. correct). Why doesn't a tool work in the same way? Picking a point slightly away from the extension line with the tool actually picks the point under the cursor.

    How can I resolve these problems?

    procedure Parallel_Line_Tool;

    var

    Line_Separation : real;

    begin

    Line_Separation := GetDLSeparation;

    Line_Separation := Str2Num (StrDialog ('Spacing?',Num2StrF (Line_Separation)));

    SetDLOptions (0);

    SetDLSeparation (Line_Separation);

    CallTool (-216);

    end;

    run (Parallel_Line_Tool);

  5. Kool Aid,

    I have AutoCad 2006 and it opens as many files as I have tried with only one instance of the program running.

    You can batch print because you have something other than the Fundementals version that I have. I cannot justify a version change at this time.

    Ray,

    Each tile has a class number. Each tile that is similar has the same class number and each tile that is different has an individual number.

    I draw on layers so class visablity is not currently in use.

    I have tried Viewports but the only reasonable way of detailing the tiles is to copy and past them to another drawing.

    Duplicating any tile in the same drawing will double the data (ie weight, qty, etc) attached to the panel so detailing the panel in the same drawing does not seem feasible.

    I would normally only have two drawings open at a time during this process since I will save the detail sheet as another drawing name before pasting another tile for dimensioning.

    Only after all the tiles a detailled will I open the detail sheets to print them all.

    Do you have a different method in mind?

  6. What are obsolete functions if they still work.

    eg. DoubLines is obsolete after VW12.5 but it still works in VW2010

    If VW takes the time to mark a function obsolete then why don't they add a cross reference to the replacement function?

    eg. What is the replacement function for DoubLine?

  7. This is what I have so far if anyone else wants it..

    procedure Layer_Visability;

    label 1, 2;

    const

    DialogWidth = 300;

    DialogTextBoxHeight = 30;

    var

    WorkLayer : string;

    i, Event, ItemID, LayerCount : integer;

    sx1, sy1, sx2, sy2 : real;

    dx1, dy1, dx2, dy2 : real;

    h : handle;

    LayerName : array [1..100] of string;

    begin

    { Record all layer names }

    LayerCount := NumLayers;

    h := FLayer;

    LayerName [LayerCount] := GetLName (h);

    for i := LayerCount -1 downto 1 do

    begin

    h := NextLayer (h);

    LayerName := GetLName (h);

    end;

    { Create Dialog }

    GetScreen (sx1, sy1, sx2, sy2);

    dx1 := sx2 / 2 - DialogWidth / 2;

    dy1 := sy2 / 2 - (LayerCount / 2 + 5) * DialogTextBoxHeight;

    dx2 := dx1 + DialogWidth;

    dy2 := sy2 / 2 + (LayerCount / 2) * DialogTextBoxHeight;

    if (dy1 < 0) then { if the dialog box is too long }

    Goto 1;

    { Begin Dialog }

    BeginDialog (1, 1, dx1, dy1, dx2, dy2);

    AddButton ('OK', 1, 1, (dx2 - dx1) / 2 - 102, dy2 - dy1 - 45, (dx2 - dx1) / 2 - 34, dy2 - dy1 - 15);

    AddButton ('Cancel', 2, 1, (dx2 - dx1) / 2 + 34, dy2 - dy1 - 45, (dx2 - dx1) / 2 + 102, dy2 - dy1 - 15);

    AddField ('LAYER VISABILITY', 3, 1, (dx2 - dx1) / 2 - 70, DialogTextBoxHeight, (dx2 - dx1) / 2 + 70, DialogTextBoxHeight * 2);

    AddField ('Choose layers to be unsnapable.', 4, 1, 20, DialogTextBoxHeight * 2, DialogWidth - 20, DialogTextBoxHeight * 3);

    ItemID := 4;

    for i := 1 to LayerCount do

    begin

    ItemID := ItemID + 1;

    AddButton (LayerName , ItemID, 2, 40, DialogTextBoxHeight * (ItemID - 2), DialogWidth - 20, DialogTextBoxHeight * (ItemID - 1));

    end;

    EndDialog;

    { Start Dialog }

    GetDialog (1);

    repeat

    DialogEvent (Event);

    if (Event > 4) then

    SetItem (Event, not (ItemSel (Event)));

    until (Event = 1) or (Event = 2); { OK or Cancel }

    WorkLayer := GetLName (Actlayer);

    { Change selected events }

    if (Event = 1) then { OK }

    begin

    for i := 5 to LayerCount + 4 do

    if (ItemSel (i) = True) then

    begin

    Layer (LayerName [i - 4]);

    DoMenuTextByName ('Standard Views', 2);

    end

    else

    begin

    Layer (LayerName [i - 4]);

    DoMenuTextByName ('Standard Views', 1);

    end

    end;

    { End Dialog }

    ClrDialog;

    { Return to working layer }

    Layer (WorkLayer);

    ReDrawAll;

    Goto 2;

    1:

    AlertCritical ('Too many layers.', 'A second column may be necessary.');

    2:

    end;

    run (Layer_Visability);

  8. I would like to see greyed made unpickable or another layer option to do this.

    I am often workings on multiple layers and want to see support or design layers but not be able to pick things on them.

    One example is when I have a floor outline that I wish to manufacture in smaller segments. I need to know where the support structure is and work on the other layers without selecting objects on the support layer.

×
×
  • Create New...