Topic: Wipeout. hate it or love it?

[Maverick®]

  *Scratching head*  Why am I always in the lowest percentile?

[CADaver]

  *Scratching head*  Why am I always in the lowest percentile?

http://www.azchords.com/v/ventures-tabs-4628/wipeout-tabs-47830.html

[M-dub]

"Love" might not be the right word, but I think they do have their uses.

[Maverick®]

http://www.azchords.com/v/ventures-tabs-4628/wipeout-tabs-47830.html

  Ooooo, something shiny to play with tonight when I get home.  (although my neighbors will not like you much)

  *ambles off to leave this nice thread to the serious folk*

[MP]

I use 'em similar to Luis (entmaked in lisp driven block definitions/instancing) in spite of the fact they have been somewhat half baked in some versions of AutoCAD (e.g. plotting).

[dubb]

I HAVE SOMEWHAT OF AN IDEA...WHY CAN WE USE A CLIP INSTEAD OF WIPEOUT. I KNOW CLIP ONLY WORKS ON BLOCKS. BUT CANT WE COME UP WITH SOME WAY TO CLIP ENTITIES IN A DRAWING? INSTEAD OF THE WIPEOUT ROUTINE. SO INSTEAD OF SOME WIPEOUT ITS A CLIP. I SAY GET RID OF THIS WIPEOUT AND MAKE IT ACT LIKE A CLIP INSTEAD. JUST A SUGGESTION. BECAUSE WITH A CLIP YOU YOU DONT NEED THE POLYLINE AREA AROUND WHAT YOU ARE CLIPPING. IS THIS POSSIBLE. HOW DOES A CLIP WORK?

[Bryco]

HOW DOES A CLIP WORK?
Good question. I'm gunna go for it acts like a viewport.
You can Clip-xrefs,blocks,images,v-ports,wipeouts.

[MP]

FOR MTEXT, I USUALLY TRY TO USE BACKGROUND MASK, WHICH DOESNT USE WIPEOUTS. BUT IN SOME CASES WHEN I PLOT TO LINES MERGE, IT DOESNT SEEM TO WORK NICELY. IF IT WOULD STILL WORK WHEN PLOTTING WITH LINES MERGE, IT WOULD BE NICE.

Code: [Select]

Private Declare Sub keybd_event _
    Lib "user32" _
    (ByVal virtualKeyCode As Byte, _
    ByVal stubbed As Byte, _
    ByVal flags As Long, _
    ByVal pointerToExtraInfo As Long)

Private Declare Function MapVirtualKey _
    Lib "user32" _
    Alias "MapVirtualKeyA" _
    (ByVal virtualKeyCode As Long, _
    ByVal translate As Long) _
    As Long

Private Declare Function GetKeyState _
    Lib "user32" _
    (ByVal virtualKeyCode As Long) _
    As Long
   
Private Const _
    VKC_CAPSLOCK = &H14, _
    TRANSLATE_TO_SCANCODE = 0, _
    SCANF_KEYUP = &H2, _
    SCANF_KEYEXT = &H1, _
    SCANF_KEYNOTEXT = &H0, _
    NULL_POINTER = 0
   
Sub StopShouting()
    If (GetKeyState(VKC_CAPSLOCK) And 1) Then
        Call keybd_event( _
            VKC_CAPSLOCK, _
            MapVirtualKey(VKC_CAPSLOCK, TRANSLATE_TO_SCANCODE), _
            SCANF_KEYEXT Or SCANF_KEYNOTEXT, _
            NULL_POINTER)
        Call keybd_event( _
            VKC_CAPSLOCK, _
            MapVirtualKey(VKC_CAPSLOCK, TRANSLATE_TO_SCANCODE), _
            SCANF_KEYEXT Or SCANF_KEYUP, _
            NULL_POINTER)
    End If
End Sub

Sub Main()
    Call StopShouting
End Sub

[whdjr]

I voted hate it. I actually would love to use it, but until they get the drawing order to work correctly i can't use it.  Many a time it's hidden stuff it was meant to show.

I couldn't have said it any better myself.
I agree 1000%!!!

[ronjonp]

I voted hate it. I actually would love to use it, but until they get the drawing order to work correctly i can't use it.  Many a time it's hidden stuff it was meant to show.

I couldn't have said it any better myself.
I agree 1000%!!!

Agreed....draworder is very unpredictable in AutoCAD.

[M-dub]

I voted hate it. I actually would love to use it, but until they get the drawing order to work correctly i can't use it.  Many a time it's hidden stuff it was meant to show.

I couldn't have said it any better myself.
I agree 1000%!!!

Agreed....draworder is very unpredictable in AutoCAD.

Good point, folks...
adjusting scorecard...
(Hate) ... 1 ... 2 ... 3 ... 4 ... 5 ... (Love)
(Hate) ... 1 ... 2 ... 3 ... 4 ... 5 ... (Love)

[dubb]

FOR MTEXT, I USUALLY TRY TO USE BACKGROUND MASK, WHICH DOESNT USE WIPEOUTS. BUT IN SOME CASES WHEN I PLOT TO LINES MERGE, IT DOESNT SEEM TO WORK NICELY. IF IT WOULD STILL WORK WHEN PLOTTING WITH LINES MERGE, IT WOULD BE NICE.

Code: [Select]

Private Declare Sub keybd_event _
    Lib "user32" _
    (ByVal virtualKeyCode As Byte, _
    ByVal stubbed As Byte, _
    ByVal flags As Long, _
    ByVal pointerToExtraInfo As Long)

Private Declare Function MapVirtualKey _
    Lib "user32" _
    Alias "MapVirtualKeyA" _
    (ByVal virtualKeyCode As Long, _
    ByVal translate As Long) _
    As Long

Private Declare Function GetKeyState _
    Lib "user32" _
    (ByVal virtualKeyCode As Long) _
    As Long
   
Private Const _
    VKC_CAPSLOCK = &H14, _
    TRANSLATE_TO_SCANCODE = 0, _
    SCANF_KEYUP = &H2, _
    SCANF_KEYEXT = &H1, _
    SCANF_KEYNOTEXT = &H0, _
    NULL_POINTER = 0
   
Sub StopShouting()
    If (GetKeyState(VKC_CAPSLOCK) And 1) Then
        Call keybd_event( _
            VKC_CAPSLOCK, _
            MapVirtualKey(VKC_CAPSLOCK, TRANSLATE_TO_SCANCODE), _
            SCANF_KEYEXT Or SCANF_KEYNOTEXT, _
            NULL_POINTER)
        Call keybd_event( _
            VKC_CAPSLOCK, _
            MapVirtualKey(VKC_CAPSLOCK, TRANSLATE_TO_SCANCODE), _
            SCANF_KEYEXT Or SCANF_KEYUP, _
            NULL_POINTER)
    End If
End Sub

Sub Main()
    Call StopShouting
End Sub

Excuse me for being a Noob but what is this code for?

[MP]

Excuse me for being a Noob but what is this code for?

If I answer that you're going to hate me. Have another read, favour the latter part.

 :whistle:

[dubb]

it looks like my CAPS are on...ahhaha...right?

[RbtDanforth]

I use a lot of wipeouts and xclips, any autocad before 2005, wipeouts are very problematic as I don't think they got draworder right.

Dino-you might checkout the masking in the text editor itself, the express tool adds a freestanding wipeout but when they redid the advances in the text (2005?) the masking is included in the text definition. as such when you erase the text the wipeout goes with it. It also is a lot more docile in that it stays under the text, something the express wipeout doesn't always do.

The only control issue I have is that when blocks are inserted they come in backwards. I have noticed this before with attributes (an old bug that seems to be cleaned up) but a block with a wipeout will come in with the wipeout on top and it is necessary to refedit it to push the wipeout to the back. This only seems to occur when the block is initially brought in or redefined.

As noted elsewhere I find them particularly useful in doors and windows in plan as well the sectionmarks etc that the text  is readable. Also in elevations, particularly with porch columns and railing, I used to xclip around columns but xcliping around railing can get tedious. And folk are seemingly always moving doors and windows "just over a few inches", easy with wipeouts, a real pain if someone has exploded the block and trimmed out all the stuff that now must be redrawn.