| T O P I C R E V I E W |
| Miksteele |
Posted - May 21 2003 : 5:16:10 PM
The 'user script list' "filter" could be enhanced like the 'drawing file selector' "Filter".  By that I mean...the ability to "save" certain combinations of letters & wildcards would allow a user to find what they need pretty quickly.
Maybe just turn the word "filter" into a button like the 'drawing file selector' filter  |
| 8 L A T E S T R E P L I E S (Newest First) |
| Admin |
Posted - June 29 2003 : 05:17:13 AM
Ok Miksteele,
(I know we've been going on a bit in e-mail, but I figured I'd open this up to the rest of the users here)
I've added a few more META-COMMANDS. Here is the complete list, so far:
SAVEAS=FALSE
SAVEAS=TRUE
ABORT=FALSE
ABORT=TRUE
NOSAVE=FALSE
NOSAVE=TRUE
SAVEAS.PREFIX=""
SAVEAS.SUFFIX=""
SAVEAS.SAMELOCATION=TRUE
SAVEAS.THISLOCATION=""
SAVEAS.OVERWRITE=TRUE
SAVEAS.OVERWRITE=FALSE
If anyone has a comment on the format of the meta commands, please let me know... I figure with the feature.function approach, just about everything can be referenced in a fairly straight-forward manner.
Also, see "how to install a patch" new Faq entry.
http://www.74mph.com/faq/FAQ00129.html
Here is the new BETA exe:
Download Attachment:  hurricane-6.1.01.zip
120.66 KB
There have been a number of other changes...
-The "Editor" is resizable (and saves last position)
-The "Editor" has been updated to include a pulldown to list these, and when clicked, they get inserted with a ";" in front, and carriage return.
-A tab added to the OPTIONS screen for GUI control (just to keep everything from being cluttered)
-On this new tab, META Command Enable/Disable as well as "Live META", which makes the interface changes, AS SOON AS THEY ARE TYPED in. (This makes for easy debug, but can bring up an error prompt if you format incorrectly)
Best Regards,
Bill |
| Miksteele |
Posted - June 16 2003 : 5:45:47 PM
WOW !!!
It seems it could almost be limitless!!
This leads me to your 'USER STATIC TAGS'...
At first I had a hard time using 10 different tags, then you gave us 40! ...Plus the ability to save them under a template file. Which really gives anyone all they would ever need,(quantity wise). (I have about 50 setup for current projects.)
Now... I have noticed that when you go into the "CONFIGURE TAGS' window for the first time in each session the 'TEMPLATE' name is blank. It will retain the last set of tags used of course, but you need to first select the 'TEMPLATE' you want... to be sure you got what you want.  Especially if you plan to save over one of your templates.
It makes me think that maybe METACOMMANDS would allow you to automatically load a particular 'TEMPLATE' with each script.
For Example...Instead of the script calling for:
"$TAG27$$FILENAME$$TAG28$.plt"
It would call for something similar to:
"$TAGTEMPLATE=MIKSTEELE$$TAG27$$FILENAME$$TAG28$.plt"
It should probably default to a MASTER 'TEMPLATE' in case the script just calls for:
"$TAG27$$FILENAME$$TAG28$.plt"
To me a MASTER 'TEMPLATE' being the default seems to make more sense than just using the last 'TEMPLATE' used. But...
Would this affect someone who doesn't save 'TEMPLATES' in the first place? |
| Admin |
Posted - June 16 2003 : 4:54:31 PM
Great...
I will add that one right away...
I'll also have in store...
;saveas=r14,r2000 ...etc
;saveasprefix=" "
;saveassuffix=" "
;saveasfolder=" "
;saveasoverwrite=true/false
I guess I could go nuts and put all the "Settings" tab stuff in there too... (I would hope though, that once those are setup, then the user wouldn't change them from script to script 
Thanks!
Bill |
| Miksteele |
Posted - June 16 2003 : 12:59:19 PM
Your METACOMMANDS:
;abort=true
;abort=false
Come in very handy...
I would also be able to use:
;saveas=true
;saveas=false
Any plans to add those as well
|
| Admin |
Posted - May 27 2003 : 5:39:22 PM
Hi Miksteele,
You have some really good points... I will consider your suggestions... This is the first incarnation of MetaCommands, so the exact format/logic will have to be worked out.
Yes, Hurricane will only process the MetaCommands when the script is "clicked-on" in the UserScript window, I suppose I could have it scan the script each time an edit is made (like just after you press the SAVE button, which would work for me), but you don't need to "clear" the script and reload. Just click on the script with the existing MetaCommand.There is a larger picture here, actually... this is all in preparation of a "novice" user mode, but I will keep things under wraps until I finalize how it will be laid out)
Yes, the opposite MetaCommand should be put in each of the other scripts to force them to default to whatever you wish. Remember, the user can still change the checkbox, even after the MetaCommand is invoked (when the script is loaded). This is an "advanced" user sort-of thing... so I would suspect that any sys-admin that is controlling scripts, will set the MetaCommands appropriately. Whoever uses them will quickly realize (as you did), that they are for "suggesting" a setting, but can be changed before the script is compiled. (I have a feeling though that 95% of users won't even care about this feature, let me know otherwise!)
Actually, there is a MAJOR difference between the two commands, NO SAVE and ABORT, and you are correct... it's those AutoCAD prompts (errors) that it deals with when moving on to _OPEN the next drawing in the queue...
NO SAVE - This just discards the _QSAVE command at the end of the script. This command won't help you much if your script changes the drawing in any-way, because you will be presented with the "Are you sure you want to discard changes?" prompt... But, it made plotting with default settings in R14, blazingly fast...
ABORT - This allows you to properly test a script that makes changes to the drawing, and EXITing properly to the next drawing WITHOUT COMMITTING THE CHANGES while inserting a delay (so you can witness/doublecheck the changes before the next drawing is loaded). I use this when debugging a LONG script, or when APPENDING many scripts together... just to make sure I don't mess up a bunch of files. (You can set the delay to a minimum if you wish) Basically, this was intended as (it WAS called "TEST RUN" or "TRIAL RUN"), as a debugging setting. At this point with A2K2, I generally use ABORT when plotting, because I really don't need to save the drawing... that just takes time! I also use this for running all files in a batch, just to see if it makes it through without any errors... if all files work, then I will run it and allow the save to take place. I HATE getting half way through a batch and have one odd-ball drawing (that wasn't created with the same limits, or layers etc... mess things up.
I hope this answers everything... ?
Regards,
Bill
|
| Miksteele |
Posted - May 27 2003 : 4:58:59 PM
'Script Filter' works great! THANK YOU!
I like the MetaCommands too...What an excellent idea!
Since I only use 'SAVE OPTIONS' on certain scripts, the new ability to save that type of information within the script makes perfect sense. I only see a few issues...
I noticed that after a script is remarked with…
;abort=true
1.) The script must be saved
2.) The script cleared
3.) The script must be reloaded
…then the checkbox is “checked” and the script runs fine.
Now, when it’s time to run a different script, (one without the ‘abort’ mode checked)…
4.) I need to remember to uncheck the abort box…or , wait a minute…
5.) I could remark an “abort=false” on all the other scripts…hmmm
Is that the only way to make this work? If it is, I’m thinking that for every MetaCommand I end up using…I’ll need to set up “ONs” & “OFFs”, (“…=true” & “…=false”), for each and every script I have. (or resort to my # 4).
Would it be possible for the MetaCommand’s to be assumed “false” if not remarked “true” in the script? That may also have some drawbacks…just throwing it out there.
Also, I’ve been wondering something for a while, it’s not related to the updates but…As far as 'Abort' and 'No Save' I think I'm confused. The 'No Save' checkbox just skips the QSAVE. The 'Abort' checkbox actually runs AutoCAD's "delay" command which delays the start of execution of the next command. Neither of them QSAVE the drawing.
What does the 'delay' actually do?
What difference is actually reached between the two? (maybe eliminate closing-errors or something along those lines?)
|
| Admin |
Posted - May 25 2003 : 7:17:43 PM
Here you go!
Thanks again for pointing that out!
I also added a little something... if you double-click the Script Filter now, it CLEARS the filter (previously you could just click on the word "Filter" and it was cleared)
Both filter files have been renamed, and moved into the DATA directory (why they weren't stored there in the first place, I can't explain...)
They are now called...
FilterDWG.dat - The drawing file selector filter
FilterSCR.dat - The user script file selector filter
Created a new standard directory called KEYS, this is where the DMO, SN, and KEY files will be stored.. the root directory was cluttered for some users, with many KEY files). This way all the registration information files are stored in their own directory.
Moved both the Drawing Filter file, and the new SCR Filter file into the DATA directory. These too should have been accessed from the DATA directory in the first place. BTW - The files have been renamed. The Drawing File Selector Filter text file has been renamed to FilterDWG.DAT, and the User Script Filter text file has been renamed to FilterSCR.DAT.
So if you want to upgrade just by replacing the EXE file, and have valuable data in the old filter.dat file, you can rename it to FilderDWG.DAT and move it into the DATA directory and all should function as before.
Added a horizontal scroll-bar to the "Favorites" selector. Some user directories are VERY long, and the option to scroll to the end seemed necessary.
Added the ability to control the "Abort" checkbox from the user script. I will be adding many more "MetaCommands" to control the Hurricane interface from within the user script. This one is particularly helpful, as in a plot script, the user may need this checkbox to be "automatically" selected each time the user script is selected. Just add the remark to your script
;abort=true if you want the Abort Checkbox to be forced checked and
;abort=false if you want the Abort Checkbox to be forced UNchecked
This is especially handy for sysadmins that want to make sure that the ABORT checkbox is checked by default for a particular script (i.e. plotting)
Download Attachment: hurricane6019.zip
117.29 KB |
| Admin |
Posted - May 21 2003 : 11:42:40 PM
Sounds good...!
I missed that inconsistency!! Consider it done...
I'll let you know as soon as it's done!
Regards,
Bill |
|
|
