Please Help ! A most stubborn bug with custom variable

[kresten]

Please Help ! A most stubborn bug, forcing me to postpone and postpone publishing the last version 18.1.5 of the freeware electronic diary program "Phenomenalog"
I am stuck with one little problem: a button on a substack ("parseviewer")refuses to answer a well identified folder ("Parsings"), defined with a custom property("parsepath" = ../../Parsings) of another substack "phenomenalog", although another handler(in substack "Phenomenalog" finds - and uses - the folder defined with the same custom property.
Experiments with placing the parsepath as custom property of substack "Parseviewer" and placing it as custom property of main stack results in same error.
In debugging I have tried to to create a variable with "LongFilePath": this gives the most absurd result: reversing the hierarchy of folders, so the higher level folders are placed under the lower level folders !!!
The problem persists both on win and on mac.
A further trouble is, that LiveCode, although closed down with the forget all, and even after restart of livecode, and even after restart of windows, seems to "remember" the previous parsepath, which looks like an unsurmountable obstackle, - could there (also) be an error in LiveCode ?
I have been fighting with this for weeks . and both Mark Schonewille and Klaus Major tell me they are too busy.
Can I tempt somebody in this most relevant group to help solve the mystery.
Here I just attach a link to the site for standalone downloads, but shall of course send the full code and folder-hierarchy to any of you, who email me, that they might give it a try.
Kresten.bjerg@psy.ku.dk
http://www.phenomenalog.dk

[mwieder]

A further trouble is, that LiveCode, although closed down with the forget all, and even after restart of livecode, and even after restart of windows, seems to "remember" the previous parsepath, which looks like an unsurmountable obstackle, - could there (also) be an error in LiveCode ?

Custom properties *are* persistent by design. Is there a difference in the code that accesses the custom property between the code that works and the code that doesn't?

[dunbarx]

Are you sure you are defining the pathNames among your various substacks? These might need to be very explicit, since you could be anywhere when you call them. The same goes for the reference to the custom property as well (the yourProp of object "yourObject" cd "yourCard" of stack "yourStack"). You may not need all of that, but it sounds like there is missing information somewhere.

As Mark says, custom properties are remembered. Thank goodness. You can always clear them if you really need to on closeStack. But again, remember where you are, and where they are, when you do.

Craig Newman

[mwieder]

Also... your pathname "../.." is very dependent on the stack position. Are you changing the defaultstack somewhere in your code?

[kresten]

Hi
Thank you for "clarifyng" questions.
Unfortunarely I am very, very unprofessional, - although having developped this program with its many substacks and folders over a period of 15 years (started in hypercard) and use it daily in a mac-version, without the mentioned problems. I am afraid I cannot answer your questions , but as the use of all substacks and the relevant custom property works without problems in my mac livecode version, I am almost sure those questions doesnt point toward a solution.
The problem is the turning upside down of the folder hierachy for the custom-variable in one single button (Load file), and the fact that it tends to relates to the folder with same name and function in the folder of another version of the program.
The fact that this memory persists inspite of restart of computer and restart of live-code sounds rather absurd.
I realize, that both of you must be busy, but.....let me ask:
Is it possible that one of you could be convinced to receive and open and have a look at the full Phenomenalog live-code application?????????
The problem is clearly located in one single button "Load file" in parseviewer substack (directly acessible through go-to-parseviewer menu of substack "Phenomenalog" - but also (without problem) opened and showing parseresults (correctly placed in the ../../Parsings folder) from use of parsebutton in substack Phenomenalog.
I am sorry to ask such a demanding question, but I see no other way out of my dilemma

If none of you can take the time, maybe you would have an idea of somebody else, who might take the time ?

Best regards
Kresten
Kresten.bjerg@psy.ku.dk
http://www.phenomenalog.dk

[SparkOut]

Hi Kresten

I can’t promise to magic a result for you, but I can take a look if you haven’t already had a better offer of help with your problem.

I will email you off the forum.
S/O

[SparkOut]

Hi Kresten
If I have understood your problem correctly, I've emailed you a Q&D* solution. If that's not what you need, then let me know.

*Quick and Dirty

(involved interrogating the custom property, and the effective filename of the stack to then create a fully qualified folder path to the target folder, rather than "../../<target>". Not sure why "open file" works with a relative path, but answer file with "../../Parsings" certainly doesn't.)