|
|
Post by Jo on May 9, 2015 16:48:12 GMT -5
When I try to debug external command calls, I realized some trouble
|
|
|
|
Post by Jo on May 10, 2015 3:14:44 GMT -5
aaargh ... where is all the text? ... the forum doesn't like me anymore ... :-(
and cannot upload a .TXT-file "forbidden" :-((
|
|
|
|
Post by George on May 10, 2015 11:13:14 GMT -5
Jo: I've pasted in the text from the email you sent so that everyone can view it. Note: When I posted this I got a message from some service called CloudFlare. It looks like the forum has signed up with this service to enhance it's security. But it rejected my post for violating the rules. Amazing as this is only simple text, no attachments. So I'm going to try editing the following bit by bit to see if I can make it acceptable.
Jo: I've pasted in the text from the email you sent so that everyone can view it. Note: When I posted this I got a message from some service called CloudFlare. It looks like the forum has signed up with this service to enhance it's security. But it rejected my post for violating the rules. Amazing as this is only simple text, no attachments. So I'm goinf to try editing the following bit by bit to see if I can make it acceptable.
When I try to debug external command calls, I realized some trouble:
1.) FILTER ... DEBUG - the windows is displayed as expected, containing "Echo SPFBatch.BAT entered" followed by the filter-command with parms and redirection.
About 10sec later, the "SPFLite Loop Intercept" popup is displayed. (Reproduceable in (CLIP) with FILTER sort DEBUG.
You must first EXIT the window before continuing with SPFLite.
Ok, I think, SPFlite must wait until the filter command finishes, but the "SPFLite Loop Intercept"-popup allowes only to wait or abend the whole SPFLite.
Therefore I would suggest to display another popup when waiting for an external command, with the option to continue waiting or "assume command complete".
2.) RUN - Even with "/K" setting in Options Submit flags used by SPFLite RUN command" there is no window open after RUN-command processing.
Same setting ("/K") under flags used by SPFLite CMD command" correctly shows an open window with output from my command.
3.) SUBMIT ... DEBUG - there is no window open after SUBMIT DEBUG command, so it's hard to debug.
Now, given that we can all see it now, I've no answers (yet) for you. As I mentioned in other threads, I've had a problem with my system the last week or so and I've only just got myself back to some kind of working system. Stay tuned, I'll start having a look at these.
George
Now, given that we can all see it now, I've no answers (yet) for you. As I mentioned in other threads, I've had a problem with my system the last week or so and I've only just got myself back to some kind of working system. Stay tuned, I'll start having a look at these.
George
P.S. Wow, I had to completely remove Jo's note to get this new security system to accept the post. It sure looks like they have the security settings set WAY TOO restrictive. I'm going to try an Edit of this post now to see if I can re-insert the text.
P.P.S. Double Wow! I'm having a hard time even explaining what I've found, this new security system is so restrictive. It does not like seeing the string C M D (D o t) E X E anywhere in the text. This is way too restrictive I'm going to ask FreeForums about this.
|
|
|
|
Post by George on May 10, 2015 14:39:18 GMT -5
Jo: OK RUN, FILTER and SUBMIT all seemed to have some problems. Slightly different ones but similar effects. So I've poked them all back into working order. Looks like more fallout from the internal restructuring introduced by 8.2. I'm still trying to pin down a nasty problem elsewhere, so I won't be releasing these fixes in an official release till I get that one resolved. But you're welcome to download and use this interim version if you like. Just download the following: www.SPFLite.com/Files/SPFLite825130.EX_ Just rename it to SPFLite.EXE and swap into the normal install folder. George |
|
|
|
Post by Jo on May 10, 2015 20:31:35 GMT -5
Georg, thx for copying my text.
Now downloaded V8.2.5130:
1.) FILTER ... DEBUG - now does not show the "Loop Intercept" popup.
SPFLite is blocked, FILTER results are available only after cmd-window is exited/closed.
2.) RUN - with "/K" setting - blocks SPFLite until cmd-window is exited/closed.
I think, as SPFLite doesn't read any RUN result, it should not wait, analogous to CMD.
3.) SUBMIT ... DEBUG - now leaves a cmd-window open. SPFLite is blocked until cmd-window is exited/closed.
And yes, now I could debug my submit-problem, but
the bad news is: I have a prototype SUBMIT command which executes a .BAT file containing a pause stmt. When using SUBMIT ... (without DEBUG) there is no change to press a key to satisfy the pause-stmt, nor is an cmd-window to close. And now there is even no "Loop Intercept" popup. SPFLite is blocked and must be endex by [x]
Jo
PS: when waiting for an external command completion, SPFLite should not wait forever, but after some timout either giveup waiting or display a popup to ask for "continue waiting" or "assume command complete".
Jo
|
|
|
|
Post by George on May 11, 2015 12:28:18 GMT -5
Georg, thx for copying my text. Now downloaded V8.2.5130: 1.) FILTER ... DEBUG - now does not show the "Loop Intercept" popup. SPFLite is blocked, FILTER results are available only after cmd-window is exited/closed. The blocking is happening as designed for FILTER, that's what it is supposed to do. The loop detect is suspended since SPFLite has no idea how long or involved the FILTER process will be.2.) RUN - with "/K" setting - blocks SPFLite until cmd-window is exited/closed. I think, as SPFLite doesn't read any RUN result, it should not wait, analogous to CMD. RUN is designed to allow quick testing of BAT files, REXX execs, and other scripting type things. Whether run with /C or /K makes no difference. SPFLite is blocked, that isn't going to change. If you need asynchronous running, you will have to save the file and use CMD, which is the only command in this set which always returns immediately. 3.) SUBMIT ... DEBUG - now leaves a cmd-window open. SPFLite is blocked until cmd-window is exited/closed. And yes, now I could debug my submit-problem, but the bad news is: I have a prototype SUBMIT command which executes a .BAT file containing a pause stmt. When using SUBMIT ... (without DEBUG) there is no change to press a key to satisfy the pause-stmt, nor is an cmd-window to close. And now there is even no "Loop Intercept" popup. SPFLite is blocked and must be endex by [x] Well, I guess you have to choose WHO you want to use to keep the window open. Either use PAUSE and run without DEBUG, or remove the PAUSE and use DEBUG, you can't use both. Either way SPFLite will be blocked till the command returns, and again, that is not going to change.
Jo PS: when waiting for an external command completion, SPFLite should not wait forever, but after some timout either giveup waiting or display a popup to ask for "continue waiting" or "assume command complete". Yes, this could be done, I'd have to convert each simple SHELL statement into a Windows ShellExecute, fire up a timer, setup Wait for Multiples, build Popuip prompts, etc. etc. So the answer is no. And for some commands like FILTER, doing an 'assume command complete" if it really wasn't would undoubtedly fail miserably and could just wipe out your edit session. With the corrections here for DEBUG/NODEBUG, I don't think more is needed.
George
|
|
|
|
Post by Jo on May 11, 2015 19:29:13 GMT -5
George: Yes, I agree, with the corrections in v8.2.5130 all external commands work fine and can easily be debugged. More is not needed.
Jo
|
|
|
|
Post by George on May 12, 2015 10:38:56 GMT -5
Jo: Thanks. Not that your suggestions were not good ideas, just hard to justify for the possible benefit.
George
|
|
