Hear, hear. So let's ask Big Brother who's trying to fool whom:
In Version 5 of the page I (ra) added the whole actual content of the page = the bugs, with more than a dozen of them, including three in a section called "Macros bugs (probably)".
In Version 6 you (kko) added comments on the relevance&validity in your opinion of some of these bugs.
In Version 7 you moved two of the three bugs reported as "Macros bugs (probably)" out of this section, you renamed the section to "Macros bugs" and you added the comment "Please report macro issues in the Bugs Forum (kko)" right after the section's title.
Yes, OK. But Big Brother didn't stop watching at Version 7. Why don't you mention what came after that?
Why should I, I responded to "probably
" and fooling.
Mmh, what's the problem? I added the information "Update
: Works flawlessly if the macros
plugin is disabled." to my initial macros bug and moved it to the corresponding section (macros bugs), to the last macros bug you left there in version 7. Did this after I found out by testing that I don't experience this problem if the macros plugin is not loaded, just like I stated in the update (so, not anymore "probably", but rather sure a macros thing). For me that is or was a macros bug then. Now, if you come up with a new or different definition of a macros bug or if you get angry ("WTF" in your first reply) because I updated the bug-report and it's a wiki, then I'm sorry, but you can't - and therefore shouldn't - blame me for that. It's much more important that bugs get reported, looked into and *fixed* in the end, than who wrote what, where, why, did it match some definition of a word, and so on (IMO, but YMMV). So... Can we forget about that now and concentrate on the bug(s)?
Let's not forget about these additional two facts:
1.) The problem doesn't happen if the macros plugin is lot loaded.
2.) The problem doesn'T happen if main.kmm is renamed and the plugin is loaded.
I don't forget so quickly. This is an important aspect.
So, I waited for all windows to finish loading (had a meal inbetween, just in case <g>): Problem was there.
Aha, that's interesting! That's good to know since I didn't expect this. Thank you for waiting!
Honestly, I didn't expect this, too. I suspected a message queue bug or s.th. like that, but K-M proved me wrong.
BTW: After the first file saved to directory x, the second save as dialog came up with the path from status quo, I changed it again to directory x. The third dialog showed x. Changed it again and it was remembered. Now I thought that it might just be the first two dialogs again, but later on K-M forgot to set the last path again...
OK, ra, I think I have enough info to reproduce this. I will check whether this also happens with layers and maybe I can find out more. I will then report to Dorian. Can't promise that this will be fixed in the next alpha (expected soon)...
Thanks for your time and effort!
Thank you for looking into it!
P.S.: I just had a look into my prefs.js. Why are there three prefs that look like they could be there for the same thing..?
kmeleon.download.saveDir - path x
kmeleon.download.lastDir - path x
kmeleon.general.saveDir - [empty]
And just in case, Dorian knows it anyway, I have set the following save options:
P.P.S.: Don't expect any new replies from me before Tuesday.