|
|
|
Page 1 of 1 |
[ 6 posts ] |
|
 ImportScript feedback : Developer's Corner
|
|
Posted: May 22nd, 2004, 2:09 pm
|
|
|
|
asl18fs
asl18fs's Reps:
|
While ImportScript is useful it currently suffers from some VERY BIG problems.
1) Error is popped up in a dialog box.
2) Error dialog is improperly sized.
3) No feedback is given to the user to indicate what went wrong. <-- THIS IS EXTREMELY IMPORTANT.
4) There's no entry in the log about what went wrong.
In it's current state it's useless for all but the one making the script. I'm thinking of releasing a special version of XUFish without ImportScript calls simply to reduce the number of people who can't get it working because of this command.
|
|
|
|
|
Posted: May 22nd, 2004, 7:41 pm
|
|
|
|
psgama
psgama's Reps:
|
I agree completely. Import Script is quite touchy at times, but it is very usefull to me anyways. Just needs some error feedback((logfiel dump?) and maybe to pop up the error message in the script window status bar instead of a msg box.
|
|
|
|
|
Posted: May 22nd, 2004, 9:51 pm
|
|
|
|
Admin
Admin's Reps:
|
Can you give me an example of the pop up message?
|
|
|
|
|
Posted: May 23rd, 2004, 10:19 am
|
|
|
|
asl18fs
asl18fs's Reps:
|
Suggested error messages would be:
1) ImportScript failed! File "xyz.vbs" not found!
2) ImportScript failed! Error when pasing file "xyz.vbs"!
The log file should preferrable include a detailed description with full path, line and column of error etc etc.
|
|
|
|
|
Posted: May 23rd, 2004, 10:46 am
|
|
|
|
WyvernX
WyvernX's Reps:
|
I think he means an example script that would cause the pop ups.
|
|
|
|
|
Posted: May 23rd, 2004, 11:21 am
|
|
|
|
psgama
psgama's Reps:
|
sure. use the importscript function with anyfile that has an syntax error in it and you'll get the popup.
|
|
|
|
|
Who is online |
|
Users browsing this forum: No registered users and 6 guests |
|
|
|