LOL, thanks, I'll forward the release to the bosses. Yeah the best time to ask for modifications is early in the morning, before I've had my 2nd cup of coffee and get all rational :D
Printable View
LOL, thanks, I'll forward the release to the bosses. Yeah the best time to ask for modifications is early in the morning, before I've had my 2nd cup of coffee and get all rational :D
So this would be a good time to ask for the "Random Reply" button?
Next to last post, we should have a Random Reply for those questions that make absolutely no sense. It would work like the last post button, but just reference a post at random. For instance, I click the button and it would grab the contents from:
http://www.vbforums.com/showpost.php...80&postcount=5
If it's easier, I'm ok with making it so it doesn't just grab things you've said. :)
Sorry, already on the 4th cup by now. Usually by 9am I'm able to distinguish objects (and arrays) and words. Once that happens it's too late.
This would fall under the cateogory of "spamming a thread" and some humorless, power hungry moderator (we all know how "they" can be :mad: ) would be forced to delete the post.Quote:
Originally Posted by sevenhalo
On serious note, are we supposed to be reporting threads that don't have code tags? It was brought up a while back and suggested (with the intention that the humorless, power-hungry mods can add them), but I wasn't sure if it became a practice. :confused:
I add them when I find a post that needs them, but I don't necessarily think it needs to be reported. By in large, the new folks that don't know about the tags and the ones that don't use them, and once it gets pointed out that they should, that generally takes care of things until the next new person comes along.Quote:
Originally Posted by sevenhalo
If you really want to take the time to report this, then I would send a link to the thread to the section mod rather than report the entire thread to the whole Mod staff. Whenever we get one of those global thread reports, our first inclination is that something serioulsy wrong is going on in that thread.
Hack is correct. When I get one of those reports I look for spam or something that seriously needs immediate attention. If I show up and find it's just in the wrong forum or is missing some proper posting protocol, I tend to leave it be.
I sometimes copy/paste the code and add the tags in the next post....
Better to report em to a mod. Duplicating the posts just makes threads really long
good point.. I will refrain from doing that again ;)
and thanks for fixing my issue
I rock! (just ask me LOL)
Re:CharsLeft
It is gone ! :(
Yes, it broke the undo feature of the editor for some reason. Had to remove it. Wasn't that useful anyway
Sorry to hear that.
It wasn't a very useful feature but it was 'cool' :cool:
Hey I worked on it for.............................ok only for half hr or so, but still I didn't wanna ditch it either :D
Send me the code. I'll fix it for you.
Post edited. :)Quote:
Originally Posted by JPnyc
It's fixed. Undo works again
http://www.vbforums.com/images/ieimages/2006/04/1.gif http://www.vbforums.com/images/ieimages/2006/04/1.gif http://www.vbforums.com/images/ieimages/2006/04/1.gif http://www.vbforums.com/images/ieimages/2006/04/1.gif http://www.vbforums.com/images/ieimages/2006/04/1.gif http://www.vbforums.com/images/ieimages/2006/04/1.gif http://www.vbforums.com/images/ieimages/2006/04/1.gifQuote:
Originally Posted by JPnyc
Apparently IE doesn't like MS's own methods. I changed the code to conform to the DOM and now IE is happy again.
See - the standards work better even in IE :D
Makes no sense. It's THEIR method, and it worked so well all the other major browsers also support it. I tend to use it because it's shorter. All other things being equal, shorter code is better code, to me. But in this case for some unknown reason, all other things were not equal, so DOM it is.
Out of curiousity - what was it?
innerHTML, their method of accessing a text node (or actually much more than just the text node). Also supported by gecko browsers and Opera. I just changed that to DOM code instead. I think I also changed the call from keyup to keypress event.
I know setting innerHTML is faster. I could well imagine retrieiving it could be slower due to having to construct the code from the DOM tree.
It's also easier. With the DOM if you want to add a node as well as a textNode, you must do it in separate statements because they each have their own method (createElement() and firstChild.data) but with innerHTML you can make it all one string, which makes more sense to me. After all it's ALL just text, and the browser knows which to parse and which not to.
Yuh, but the DOM methods are safer as regards to well formed code.
Adding a node with a text node isn't too hard:
I converted a JS project from using innerHTML to DOM a while ago - made it a lot more managable when I had to change the DOM structure at all. But I know what you mean, it's more work to set up initially.Code:p = document.createElement('p');
p.appendChild(document.createTextNode('Some text'));
I know how to do it, just that it's an extra statement. I have issues with quite a few things the w3c has recommended. I have a few recommendations I'd like to make to them too.
Remember w3c DOM is not meant to be for HTML. It was designed for XML in general; often however, individual implementations have methods such as the saveXML which returns the node and its containing XML as a string.
Quote:
Originally Posted by JPnyc
Just sent them to a mail to Tim JB, and say hello from me (please don't mension that I stole his office) and they will gladly listen to as many requests as possible. It is not only Microsoft, Opera and Firefox that can come with suggestions. Just look at the automatic search. It was an open standard, and are now already adopted by two of the biggest browser vendors. But don't expect JS to make sense any time soon...
The function doesn't count quite properly. I type the first characer and it still shows 10000. I type another and it shows 9999. I press backspace and it shows 9998.
In Fx...
Well I guess it wasn't the innerHTML after all that broke the undo. Seems to not like the onkeyup event handler.
Now it's counting correctly. You found the problem?
That problem yes, but it creates another. If I use the proper event handler, which is how I originally had it, it breaks the undo function in IE, even using the DOM methods. Undo is broken in IE
I found another problem. Not sure if it was there already...
If you paste multiple strings and then try to undo by pressing ^Z (I'm using Opera), just pressing and holding ^Z doesn't work. You have to prerss the buttons multiple times.
I removed it, permanently. Too small a feature to bother about.
Your best option woluld have been to have a function that counts the length of the string at regular intervals, say every 2 seconds and subtracts that form the maximum number of characters. setInterval() or setTimeout :)
Nah, we'd have had complaints about that too, that it didn't change with each character typed. It's just not that important a feature to bother about any further, at least I don't think it is. I could probably get around the IE issue by registering an event listener but that's a pain for a little piddly thing like this
I tried that too and it didn't work either.