draffutt wrote:Received an error today "Could not check parameters for call to: "file name": file not found. it seems some scripters when creating scripts for uninstall routes put uninstall scripts into a folder called uninstall. can you have exscriptor check for this directory when compiling and/or saving?
This is only a warning to let you know the file isn't callable. I prefer to leave it like it is, that way if you do have a call to a file that's in another directory (and thus cannot be called), it let's you know that it might not work.
draffutt wrote:Is this intended? if i highlight a item in a line for instance {video enchancement goggles} and i want to replace it with something else I.E. {docking computer} rather then replacing it. it does this: {docking computer}{video enchancement goggles}
This is something I kept meaning to fix, so thanks for reminding me! It should be okay now, i.e. it will replace the highlighted text, not just insert it all the time.
draffutt wrote:can you change the close all pop-up to something like this:
Changing the pop-up that much is more effort than it's worth (since it means desigining a completely new one). However, I have changed it so that it asks you if you want to save them all; if you press yes, it saves, press no, it just closes them all, and press cancel and it does nothing.
bunkerprivate wrote: I did have a slight problem where empty comments, when saved by X3, would be rendered as '* ?' in Exscriptor. I'm not positive this has been fixed yet.
I'm pretty sure I fixed it, but it may be that the file is still in a "corrupted" state, so to speak. Try loading it in the Exscriptor, getting rid of the ?, and then resaving it; that should hopefully get rid of it. If not, let me know and I'll poke around a bit more.
bunkerprivate wrote:so it would be good to have a 'compile all; stop on errors' (or optionally on warnings) function which sends you to the tab which had errors.
Good idea; I've implemented this (and it also features as part of a Save All feature too). It doesn't stop on warnings, but it will on any errors.
bunkerprivate wrote:CTRL+F
I have grown to hate that innocent-looking dialogue box. It's a nest of weird bugs. I think I've caught this particular one now (and a couple of others). I also stopped it being on top all the time and also added a "From start" search option, to restart the search from the top. Yet even so I fear I've not seen the last of Find/Replace...
bunkerprivate wrote:Unused script arguments don't seem to get checked any more.
I think I broke this in an earlier bugfix. It should work again now.
bunkerprivate wrote:Commented code is being checked for unassigned variables.
Never thought to check that!

Well spotted - it should now be fixed.
bunkerprivate wrote: ctrl+X then undo, then press an arrow -- cursor is somewhere random
Undo/Redo always does strange things. One day I'll get round to overhauling it. In the mean time it should have stopped doing it now.
bunkerprivate wrote:- in a script call, if you put a parameter as "[TRUE", it will report not enough params instead of a syntax error.
There's actually not a lot of checking on call script parameters at the minute, beyond counting how many there are. It's on my list of things to redo but for the time I'm afraid it's unchanged.
bunkerprivate wrote:- if you remove an argument from a script, then open a script which calls it with the old interface, the extra parameter's name is equal to the first (so it's looping round)
I cannot believe you spotted this! It's actually down to an almost invisible bug where all the called script's parameters were being loaded repeatedly (once for each parameter being passed in) - hence when it ran out, it moved on to the next. Turns out I had a piece of code caught in the wrong for loop. Anyway, it's fixed now!
bunkerprivate wrote:- it would be nice to have a go-to-line function from ctrl+g
Good idea - I've added one in the Edit menu now.
bunkerprivate wrote:- it would be useful if, for scripts which have not enough parameters, it would load the parameter name (only on 'refresh from file'). It saves loading up the script and checking my docs! Perhaps it could load it with a syntax error like <?> as in X3?
I'm not entirely sure what you mean here, but what I've done is get the warning/error to display all the expected parameters so at least you don't need to open the other script to check them. Altering the code itself to display the correct names mid-compile is a bit more difficult...
bunkerprivate wrote:- if you open a script which is already opened, the textbox should ask if you want to select the tab (so the buttons would be "reload", "go to script", "cancel")
I just use a simple built-in MessageBox to do these pop-ups, and as I mentioned to draffutt, it's not really worth the effort of creating an entirely new form for something like this - though maybe in a later version I'll improve this kind of thing. What I did do is get it to go to the already-existing script if you press "no" (for don't reload).
bunkerprivate wrote:- reordering tabs would be nice but I guess that stuff is hard on windows.forms...
You'd think it'd be built in, but apparently not... I did manage to get a fairly clunky solution working though.
bunkerprivate wrote:- doesn't check if you have two goto labels named the same
Good idea - I've included a check for this too now.
As usual, V1.028 is available
here.