Topic: the Swamp Block Library Manager?

[Hugo]

Hallo jbuzbe

Ein Vorgabe von Layer und Skalierung wäre noch eine Tolle sache.
sonst super Super.


One target of scaling layer and would be even sache a madwoman.
otherwise super super.

Danke

[jbuzbee]

Thanks Hugo, glad you like it.  I'm going to work on the tree performance issue.

Kerry, I added the form definition to your lisp file so you won't have to load the odcl file seperately.  That'a a nice little feature Owen added.  Really cleans up deployment!

[pkohut]

Possible speed ups - Looking at the source code and the picture at this link
http://www.theswamp.org/index.php?topic=32081.msg377241#msg377241

I think you can get rid of the file modification dates and sizes without loosing functionality, as it's just visual noise. 1) For those rare occasions when a user wants the info they can get it by other means.  2) The code to retrieve and format the display info is fairly involved. 3) How efficient are vl-file-size and vl-file-systime?  Do they do a file open and close for each operation (don't know)? If they do then this can be a very expensive operation, and more so over a network.

Having not run the application or knowing anything about OpenDCL and such, I can only guess that the directory tree is being fully populated at startup.  If this is the case then you will get a huge performance boost by only retrieving directories/sub directories info when needed, ie. by expanding a sub directory leaf.

[t-bear]

OK...minor problem.  This keeps resetting ATTREQ and FILEDIA to "0".   

[Kerry]

< .. >

Kerry, I added the form definition to your lisp file so you won't have to load the odcl file seperately.  That'a a nice little feature Owen added.  Really cleans up deployment!

Yes James I know about the ability to add the ASCII dialog to .LSP source. I don't do it for developments or sample code .

For anyone who wants to use this I remind you that Post #21 has the attachments for the supporting Library File and .INI Configutation File and ALSO  the Source .ODCL file if you want to make changes to the dialog.
Also note Reply #56 : the changes I've noted in that post should be made if your attributes are NOT preset and require confirmation .

I'll call this Build _08 since _07 has been used.

[jbuzbee]

Which one tbear, mine or Kerry's?  Mine shouldn't set any variables at all.

This is why hijacks are so problematic . . ..

[Kerry]

OK...minor problem.  This keeps resetting ATTREQ and FILEDIA to "0".   

Which one tbear, mine or Kerry's?  Mine shouldn't set any variables at all.

This is why hijacks are so problematic . . ..

Well that's not mine
Any changes I make I restore, even after errors
... and I don't set ATTREQ and FILEDIA to "0".   

[CAB]

I smell a command call.  he he he

[CAB]

When you use the command to insert a block with attributes you must address the following system variables.

Code: [Select]

;|
ATTDIA
Controls whether the -INSERT command uses a dialog box for attribute value entry. See "INSERT Command Line."
0        Issues prompts on the command line
1        Uses a dialog box

ATTMODE
Controls display of attributes.
0        Off: Makes all attributes invisible
1        Normal: Retains current visibility of each attribute: visible attributes are
                displayed; invisible attributes are not
2        On: Makes all attributes visible

ATTREQ
Determines whether the INSERT command uses default attribute settings during insertion of blocks.
0        Assumes the defaults for the values of all attributes
1        Turns on prompts or dialog box for attribute values, as specified by ATTDIA

TEXTEVAL
Controls the method of evaluation of text strings.
0        All responses to prompts for text strings and attribute values are taken literally
1        Text starting with an opening parenthesis [ ( ] or an exclamation mark (!) is
            evaluated as an AutoLISP expression, as for nontextual input
|;

(setq sysattdia (getvar "ATTDIA"))
(setq sysattreq (getvar "ATTREQ"))
(setq systxteva (getvar "TEXTEVAL"))
(setvar "ATTDIA" 0)
(setvar "ATTREQ" 0)
(setvar "TEXTEVAL" 0)


<do your lisp>


(setvar "ATTDIA"   sysattdia)
(setvar "ATTREQ"   sysattreq)
(setvar "TEXTEVAL" systxteva)

;;================================================================
;|
Alternately you can use the sys var EXPERT

EXPERT
Type: Integer
Not saved
Initial value: 0
Controls whether certain prompts are issued.

0 Issues all prompts normally.
1 Suppresses "About to regen, proceed?" and "Really want to turn the current layer off?"
2 Suppresses the preceding prompts and "Block already defined. Redefine it?" (BLOCK) and "A drawing with this name already exists. Overwrite it?" (SAVE or WBLOCK).
3 Suppresses the preceding prompts and those issued by the LINETYPE command if you try to load a linetype that's already loaded or create a new linetype in a file that already defines that linetype.

4 Suppresses the preceding prompts and those issued by UCS Save and VPORTS Save if the name you supply already exists.
5 Suppresses the prompt, "That name is already in Use, redefine it?" issued by the -DIMSTYLE Save option when you supply the name of an existing dimension style.

When a prompt is suppressed by EXPERT, the operation in question is performed as
though you  entered y  at the  prompt. Setting  EXPERT can  affect scripts, menu
macros, AutoLISP, and the command functions.

|;

[Kerry]

As can be seen from post  Reply #56

(acet-error-init (list (list "CMDECHO"   0
                                "expert"    5              ;;<<==                           
                                "ATTREQ"    1            ;;<<==
                                "ATTDIA"    1             ;;<<==
                                "BLIPMODE"  0
                                "INSUNITS"  0
                                "OSMODE"    0
                                "PICKADD"   1
                                "PICKBOX"   5
                                "SNAPANG"   0
                                "SNAPMODE"  0                                                             
                                "SORTENTS"  1
                          )
                          0
                    )
   )

The variables noted are stored, changed to the value nominated for the duration of the routine and the previous values are restored on termination or error.

I don't set either ATTREQ or FILEDIA to "0".
 

[CAB]

That a slick trick Kerry, haven't been following this thread much so I missed #56. 

[Kerry]

That a slick trick Kerry, haven't been following this thread much so I missed #56.  

Yes, I like the idea.
I have my own custom routines for that and error trapping routines ... but chose not to post them, so used the ExpressTools routines instead.


added:
if you add
"CLAYER"(getvar "CLAYER")
or
something like "CLAYER" "MySpecialTextLayer"


to the list any layer changes during the procedure will nullified at termination when CLAYER is reset to the initial value

[t-bear]

I am using what I believe is jbuzbee's original build....might be the problem.  I kinda got lost with all the builds ans stuff.  Will have to hunt up the latest installment of this and try again.

[jbuzbee]

The latest is in the original post - I finaaly figured out how to fully edit a post 

I'm still working on the whole tree thing . . . could use some help.

[t-bear]

The latest is in the original post - I finaaly figured out how to fully edit a post 

I'm still working on the whole tree thing . . . could use some help.

Thanks amigo, I'll reload it.
As far as helping you with this, you might have noticed....I'm worthless.....sorry.