Thanks for the feedback. There are several great ideas, and I look forward to tackling some of them. Let me add a bit of feedback on some...

setTimeTrigger - This is already implemented, using an event trigger. For Example:
seteventtrigger loginTrig :doLogin "TIME HIT" "11:59:50 PM"
Time must be in Sytem Time format, i.e. HH:MM:SS AM/PM.

When scripts are loaded, they are compiled... or they're already compiled if they are .cts files. I don't see where integrating scripts into the app itself will improve speed. Further, if speed is an issue, you are either doing heavy calculations or your script needs optimization. Not to say that there isn't tons of room for improvement in TWX itself, but that will have the same impedence whether the script is external or internal.

A bubble finder written in native Delphi would be much faster than a TWX script, but that is an apples-to-oranges comparison when talking about scripts. A natively written bubble finder isn't a script, nor does it resemble anything like one. Ask rev to paste his pascal bubble code... friggin scary. Very fast, but takes weeks or more of study to understand. Heh, rev probably couldn't explain it without hours of study. Course plots have been optimized in 2.04, and now have the ability to plot with avoids. Bubble searches was a driving force behind those improvements. Perhaps I just need to publish one of my bubble scripts. I *think* it will have reasonable performance with the 2.04 improvements. I had once conceived a highly efficient bubble search... I'll have to see if I can recall the method.

[EDIT: I remembered the technique, scripted it, and it takes 45 secs for a 5K... I'll post it on Grimy.]

The next source release will be compilable with Turbo Delphi, as this has been a primary goal with this release. I'm also committed to having interim builds available through a versioning system like Subversion, hosted publicly. But I'm not trying to tackle that until the next release is ready. Don't hesitate to hit me up if you need help in the mean time though.

Keep the ideas coming.
+EP+

Laff, the single bubble approach? Didn't that never work? Or did you just use the BFS approach?

The thing is, TWXproxy HAS a bubble feature in it. Right click, export bubble list. That works pretty well last I checked, there's just no way to do anything (atleast not automatically) with it. Seems weird to have such a cool function so poorly used.

i just put up a subversion server on a raid machine. lets talk about it.

Thanks rev, I'll hit you up on that.

I'm still working on that unified theory of mine... the one where I believe that all single and multi-gate bubbles can be found using a single BFS search. Perhaps I'll pick that up in another thread soon. This latest approach is still much better than those before it.

The bubble export from TWX is useless as far as I can tell. The $db display is great, but the gate info isn't in the export, which is the most important part. I'll look into what it takes to fix that, and to make the data exportable or accessible programatically, from within a script. Sooner if I don't get distracted with that unified theory

+EP+

Not sure if there's a way to do this, but it would be nice to have a DeleteSectorParam command.

Not sure if there's a way to do this, but it would be nice to have a DeleteSectorParam command.

There already is it is in DeleteSectorVar in Database.ps

IIRC SectorVar and SectorParam are essentially the same thing.

And Lonestar let me be one of the few that will thank you for letting M()MBot out in the open source world.

Now the challenge is to come up with something better. It is gonna be VERY Difficult to do, I've just been perusing the code this afternoon and it looks very professional and well written. KUDU'S to you and anyone else that contributed code, or ideas or even dumb ideas. Even contributing a dumb idea helps that shows us how NOT to do something.

To get this back on topic What do you people want out of TWXProxy that might help you out in scripting that we might implement in the actual source code.

One Suggestion that came to mind was a Quickstats routine but that is also relatively simple to script.

Another idea would be a nearfig routine that people have also written in scripts that might be able to be provided through delphi/TWX.

here is a wish: import port data. currently you can only import warp data or a twx database. since i don't use twx, i often want to send a port cim to someone and have them import it into their twx.

There is something that I've ran into that I really can't figure out why it is that way. When you ask a user to load a file name, the user has to enter the correct file name. Just wondering if there is a way or a routine that will open a directory window such as windows explorer so the user can select from a list of files instead of typing in the file name to select a data file.

got this again today:

whats up with that?

Rev, it looks like you didn't get a command line in between proceedures,(in this case computer line). Could have been caused by CN9 being set to all keys.

A simple version is posted in the scripts forum.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

hehe. didn't you see the computer line in the screen cap?

Thanks for the report Rev. I didn't see an immediate issue with the Port Report code in TWX, but I'll keep looking. Is it a repeatable bug when it occurs?

Big D, there is the tray icon that can be double-clicked to open the 'Load Script' dialog window. I don't see how it can get any simpler than that. If you prefer, right-click and select 'Load Script'.

it is not repeatable. i can't seem to figure out what the trigger is.

any love on the import port cim request?

You're not on the same page as me. I mean when you are coding a script to ask the user where the data file (sector data, port data, etc...) is located. Only way I see do get that information is by typeing in file name that may or may not exist in the twx directory. Not even sure it is possible, but with rexx/zoc, I can program the script to open up a window with all the files in a selected directory, and the user can switch between directories to select a data file for the data that script needs. Not sure how to explain it any better than that.