Help with big scripts

Hi

I have 4 items in my wishlist, that could help me find my way in my huge script. Please forgive me if they have already been mentioned:

  1. Line numbers in the script. I am aware that this might cause a problem because one doesn’t expand all nodes at a time.
  2. Another possible option to help navigations in the script is BookMarks like in Delphi where one can put a small mark near some lines (using Contoll K + Number), and then got back to a cpecific mark using Contoll Q + Number
  3. Search doesn’t find your string if it is in : Set Variable New Value. It would be nice to have this.
  4. I have a huge logfile so I normally use “Show Ignores Errors”, but then I only get the Error line itself and I can’t know where it came from (same command appears a few times in my script). Line number in script , like my first suggestion , could help here. Another possibility would be optionally to include a couple of lines that precede this command that caused the error.

Thanks Daphna Levin

Hi

1) Good suggestion, will look into it (not sure if it will be possible).

2) This is something I’d like to see

3) This sounds like a bug.

4) Double click on the entry in the log and it should take you to the action in the actionlist


  1. Thanks, but My main script calls another script so double clicking on the error line does nothing.
    Daphna

3. This is indeed the case. I thought it was by design. If not it would be great if you could fix it.

Posted By Larry Re on 28 Jun 2006 4:03 PM

3. This is indeed the case. I thought it was by design. If not it would be great if you could fix it.



Well, I just had a look at this issue, but wasn't able to reproduce it. Can one of you provide a sample project where this happens?


Hi
I am attaching 2 very simple projects. “Caller” calls “Called” . Called has an error. I run Caller, Show full log and then show all error actions. I double click the error line (set variable…), but nothing happens.
Thanks DaphnaDemo.zip (2.722 KB)

Daphna,

Thanks for the attachment. The issue with double-clicking on the log to see an action is by design and unlikely to change - the action in question is in a different project, and the log is only in the calling project, so loading the called project to see the action for the log entry is extremely difficult.

A feature which could perhaps help would be to keep the selection when clicking back on the “Show All” button? ie you click “Show Error”, select the error action, click on the “Show All” to see it in context? Would that help?

The bug Vincent is referring to not being able to reproduce is this one:

3. Search doesn’t find your string if it is in : Set Variable New Value. It would be nice to have this.