08-22-2007, 04:23 PM
A1. I'm sure.
If the cookie exists before the macro runs, the macro deletes it:
2 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
Then, when I click Submit, the cookie is created and immediately deleted:
1 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
8 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
2 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
If i manually delete the cookie file before I run the macro, on Submit it is created/deleted anyway.
After 30-60 seconds works well again, one time:
1 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
8 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
A2. The file monitoring function is not called from code. It simply has file trigger.
A3.
Function AnyName
Trigger:
$f 0x4F "$cookies$"
QM file triggers monitor all file system changes in real time, without polling.
If the cookie exists before the macro runs, the macro deletes it:
2 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
Then, when I click Submit, the cookie is created and immediately deleted:
1 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
8 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
2 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
If i manually delete the cookie file before I run the macro, on Submit it is created/deleted anyway.
After 30-60 seconds works well again, one time:
1 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
8 C:\Documents and Settings\G\Cookies\g@~~local~~[1].txt
A2. The file monitoring function is not called from code. It simply has file trigger.
A3.
Function AnyName
Trigger:
$f 0x4F "$cookies$"
function event $name [$newname]
;event: 1 added, 2 removed, 4 renamed, 8 modified
out "%i %s" event name
QM file triggers monitor all file system changes in real time, without polling.