|Message: Re:||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I'm reposting to question here as it may be useful to others:
Hi Ben, Thank you very much for your help, I edited the PATH environment variable, and that error was gone. However, the application didn't execute saying "the application stopped working". I suspect I am giving the command wrongly. Since in my simulation I have a macro file to be executed with my executable, I used to execute my application as : "myapplication fullRun.mac" where fullRun.mac is the name of my macro file. When I couldn't run it this way, I thought may be I should put a copy of my macro file under Debug folder, again the same result! Could you please advise me how to get my application executed? Thank alot Leila
I'm not sure of the exact pattern you've used to run, but if your application accesses macros in the same way as the examples, then they need to be supplied either as a full (i.e. absolute) path to the macro file, or as a relative path from the directory you are working in to the macro file.
If you haven't done so already, I would try starting the application in a directory where a copy of the macro resides. Running
|Inline Depth:||Outline Depth:||Add message:|