Quote
siria
Oh my, that's just way too long and complicated to discuss everything...
But I guess the main problem is just that you insist on using stoneage macros.cfg for all eternity, struggling for hundreds of hours and getting a hundred gray hears, instead of finally giving in and spending some ten hours in transfering your macros.cfg into a JohnHell.kmm file
Again, and it's the last one. Old macros = new macros with different definition styles. They do exactly the same. So I'm not going to discuss on this topic anymore
Quote
siria
Oh well. Lets still see some of the points: Those little bugs that you mention like needing to click in a page or such, that's just that, beta bugs. Due to new gecko. First dorian fixed some, then desga, currently deadlock. You know yourself this is still a slightly buggy beta version, so no reason to condemn all KM versions younger than 1.0 generally as unhandable. Those bugs are due to beta state, wait with condemning until the next stable version is out, if it still contains those bugs :cool: But frankly, I have hardly ever trouble with that stuff. It happens rarely and I know how to work around in seconds, so no stress. BTW my mouse does not disappear when typing in the URL bar.
I know, and that is why I find less than funny to find asking what reasons are to still using old versions.
But I find interesting how people don't have problems with it and find workarounds. When K-meleon gets stuck at 100% CPU load and the only way to continue using it is close it... what is the workaround? Please, tell me, because, right now, this is the most annoying thing with 1.6b2.
About the URL bar typing, I'm going to make a video, as I did in the past to compare a bug from one to other version. Then, tell me.
Quote
siria
What I changed to enable javascript? Really nothing. What I tried to tell 3 times already: there is nowadays a built-in exception rule for the injectJS command. JS is toggled automatically if an injectJS is fired. But with those exceptions allowing only less dangerous commands, like zooming or changing css styles, page titles and such. You can simply delete the JStoggle lines for the given example script. Well, this goes of course for my "current" macro system, no idea if it also goes for sort of "legacy macro emulation" on new KM versions. That may not work anymore 100% perfect 5 years later.
The first time I hear there is no need to enable javascript to use injectJS. Really, it's not a joke. In 8 years, the first time.
And, hey!, it's true. How is that no one told me before?!?!
I know the answer, and I don't want to hurt the feelings of anyone,
seriously: the lack of a good documentation and the lack of the people who know how it works that don't change the documentation accordingly, what doesn't help. (Sadly, a lot of people disappeared from this page/project/piece of software
)
If this (injectJS working without javascript enabled) is being said somewhere, please, tell me. I'll admit any error by myself.
Quote
siria
About CAPS policies: Yep, as James said too, if you don't use Policy Manager, it's almost sure you don't need to think about CAPS stuff.
Okay, I digged up an old 1.0x version of mine and looked inside macros.cfg, to see which pref it really toggles. And it's still the same as today. No caps, no worries. So forget that I mentioned caps.
But you told me. You assumed I was using it. Why?
Quote
siria
Quote
why now is not accepted "javascript:whatever_function_to_run();" as URL?
Sure it is :cool: But only if you have javascript fully enabled, otherwise "javascript:" in URL bar is blocked. And it also doesn't work from urlbar if the setting to "open Typed URLs" is set to open "in a new page".
I also suspect, if you have the "define kmbody" and the "execute kmbody" split up into two separate actions, and JS is toggled on-off-on-off, the script may well be killed in the middle, and the definition of kmbody forgotten again. So would much rather leave it "in one piece" in one injectJS line.
But I don't toggle on-off continuously. Have a look, again, to my code. I just toggle on, inject code, let run code, toggle off.
Never, never, can this kill a script. Unless the toggle off is being run before wait until script finishes. This behavior is correctly made by 1.1.x, why not in 1.6b2?
Quote
siria
So, the question is what happens if you only keep the extended js-line, delete the toggle lines, restart KM, allow JS manually, then run the macro? Does it work at all if JS is fully allowed?? If not, I'm going to blame your legacy mode
No, not the single commands in it, but the whole system in itself with macros.cfg and such. You'd really save a lot of time and gray hairs the quicker you switch to the modern macro version, and get tons of *working* new macros at that ;-)
Again, this is not with macro version (is not even macro, but definition).
What do you have against old macro definition if they do exactly the same?
I know, when I try to search for help you can get confused. I accept it. But, in the other hand, I don't get why the main macro definition (that, indeed, are inside main.kmm) got changed by the developers. What's wrong with them????
Well, let's make the video about mouse disappearing when you type in the URL bar.
EDIT: ummmm not video, looks like this happens on previous version but I didn't noticed before LOL... Probably my bad eye over 1.6b2, blinded me over the truth
But I found 1.6b2 closed while I was typing in the URL bar LOL. Do you like to see that video?
EDIT2: It is a documented crash, but just for the fun:
http://www.megaupload.com/?d=XAF2ZMO6
Edited 2 time(s). Last edit at 08/29/2011 09:38PM by JohnHell.