[HTMLPad] Javascript stopped working

[Anthony]

Hi
First may I say that HTMLpad is a lot of program for
the money. It has the look and feel of Delphi, which I have
worked with since it first came out.

I've struggled through the basics of html and am now adding
javascript to the mix

Trouble is, the rudimentary things I started with (Alert box etc)
functioned for a while, but after I had fiddled with the syntax
highlighting a bit, it stopped working altogether

I just know I've disturbed a setting somewhere,

but what?

Thanks in advance

Anthony

Last edited by Chris on 24 Nov 2006: Changed post title

[chrisjlocke]

Whether Javascript is working or not will be down to the browser, not HTMLPad.
Whats your browser?

Your post looks like you've pressed Enter after each line. Just a little tip that you don't need to do that - just press Enter to start a new paragraph. Everything will look right when it gets displayed - trust me!

Welcome to the forums though...

[Anthony]

Thank you, Chris, for the reply

I have discovered that if I exit HTMLpad and restart it then things begin to work again. This seems to work with a couple of other things as well.

Cheers

[Anthony]

I've noticed that after 2 or 3 F12 tests javascript code stops working and I have no choice but to save all files, exit HTMLpad, restart and reload my files again, after which it's ok again for a bit.

This is a pain - Is there anything I can do about it?

[syrupcore]

that's really odd. I work with js all the time and I've never had that problem. It really does seem like something that has to do with your browser, not HTMLPad.

Try this as a test. Instead of using f12 repeatedly, do it just once. From there on out, hit ALT+TAB to switch to your browser and then hit f5 to refresh the page. Does it still choke after 2 or 3 tries? Try it with different browsers too (make ff your default, then IE, then maybe opera and see if you have the same behavior with f12)

you may also want to uninstall and then reinstall HTMLPad, just to be sure.

Will

[Anthony]

Thanks Will . .

I'll try that

Anthony

[Karlis]

If there is now other way around, you can set up the HTMLPad to remember the files that are loaded and load them on next startup in the same order. This could save a bit of your time. Just hit Save All and reload the program.

Other solution would be to uninstall and re-install the HTMLPad to see whether the settings were to blame. Probably it has something to do with the javascript settings in preferences.

Alternatively you may want to try FireFox preview.

[Anthony]

Karlis, I already have it set up to auto reload all the current files, which is a good thing and saves time as you say

Further to my problem, I have determined that this happens whenever a javascript error is detected

Whether or not the error has been fixed, subsequent f12 tests ignore all javascript in the document, running only the html.

This persists until I do another save - exit - startup(HTMLpad) sequence, after which it behaves normally.

BTW I'm running internet explorer (a newish version)

Anthony

[Anthony]

It seems that after Hpad has detected a javascript error, in subsequent tests it doesn't start at the first instruction on the page

The next time the page is tested (displayed wit F12) the code is acted on from the point where it previously left off

[syrupcore]

are you using IE preview or FF preview? IE might be choking on the doc.

I know preview is really handy but if you're not manually previewing your Javascript in Firefox with the Firebug plugin, you're wasting your time. there is nothing on the planet right now that will help you code better JS than firebug. it's free. it rules.

[Anthony]

I surmise that you are as yet undecided about firefox and firebug then, but I reckon I'll have to try them out anyway.

I am assuming firefox is a browser, and firebug a debugger?

Trouble is I've only given myself til Christmas to get this website up and running, so can't change horses right now.

I'm managing at the moment with this old clunker by dropping out and starting it up again before I do each test (Got the startup icon in the top right corner of the screen, close to the X ) besides, there are lots of things I really like about it.

Thanks for the tip - and have a nice Christmas

[Karlis]

Try this - Ctrl+F5 (full refresh) on the loaded document, does it help?

Have you set the IE caching options to "every visit to the page"?

[syrupcore]

I surmise that you are as yet undecided about firefox and firebug then, but I reckon I'll have to try them out anyway.

yeah, I'm on the fence about it.

I am assuming firefox is a browser, and firebug a debugger?

100% correct. you could have them both up and running in less than 15 minutes. Firebug is really just a marvel of programming. It actually makes html/css/javascript coding fun! Build it in Webuilder, fix it in Firebug.

Seriously, you should get it BECAUSE you only have until christmas.

will

[Anthony]

Ok Will, I've done that

Initially it's both exciting and baffling
Firebug doesn't seem to have any instructions
or help files of it's own - A few pointers here would be
greatly appreciated

Karlis - I'm not sure how to break this to you -

but I've been using F12, not F2, which is why the
F5 gave me nothing.

Still . . Internal testing does throw up errors not
noticed by the real brouser. Pity the locations given
seem to be nowhere near. Or am I missing something
here, too?

[Anthony]

Further to my question about code collapse-

I suppose it's nothing to do with hiding your page source from right-clickers, but more like what happens when you click a triangle in firebug?