| Newsgroups |
gmane.comp.windows.gui4cli |
| Message-ID |
<[email protected]> |
Hi Dimitris,
Yes, it still looks like voodoo and I already didn't expect a "aha, now I know how to fix" reaction
from you on short term :)
Win7 does weird things with paths. It monitors folders which means if you have a shortcut and
rename your folder, the shortcut is automatically updated. That looks nice but if you have two
instances of the same application running in different folders, there's a big chance the one you run
is digging in the sub-folders of the other.
I struggled for example with the reqFile event to open a local sub-folder like e.g. "#$templates".
Couldn't get that to work and because I run more instances, it opened at the same sub-folder
but at another install location. It looks like # doesn't work in Win7 ?
I finally found a solution (or at least it looks like) by explicitly extract the path and adding a slash
at the end of it. No idea why this seems to help.
Chris
---In [email protected], <gui4cli@...> wrote :
Hi Chris,
I've gazed at the code with a dumb expression for many hours and found nothing wrong. That's to be expected since the code works correctly "almost" always.
The fact that it messes up on rare occasions probably means that its a series of things that if done in a particular order sometimes build up to something unexpected. Its the worst kind of bug and very hard to find.
Maybe I'll get lucky one of these days :)
Dimitris
On Thu, Jun 12, 2014 at 8:53 AM, chris.kevany@... mailto:chris.kevany@... [gui4cli] <[email protected] mailto:[email protected]> wrote:
Hi Dimitris,
I went on with my script launching it from the desktop shortcut, then after
some additions I tried the normal launch again and it didn't stop anymore
on the attr font line.
I then compared the scripts from before and after the additions and it
appeared that I added new things "before" the attr font line so it was shifted
to a new position in the script.
So now I think it isn't the attr font line itself that caused the issue but the
"unhappy" position it had in the script. That would declare why g4c stops
at any arbitrary event (xRoutines, loops etc.) everytime there are additions
or modifications to the script.
That's also why I still think it's purely a parsing issue when scripts are loaded.
Still a mystery why it's rare in WXP and persistent in Win7 ?
Chris