Help on programming

It took a little hunting to find the spots you are talking about. Remember , this is old hat to you, but we are looking at it for the first time. Aft er I played "Where's Waldo" with the Ired.gif image, I realized what you ar e talking about. The HTML looks ok to me, but then I'm no HTML guru.

I do see you are specifying height:59px; width: 837px which you don't do fo r the one that works. What is that for? Try taking it out.

Start by looking at HELP.htm in View:Source and note that the red "I" works and the red "US" does not work. The Div for the "I" then, is a template for what the Div for the "US" should look like.

I don't know what you're intending with that map, as it's a bit messed up. The text for the index is likely intended to be lower on the screen. If the "Map" function only works for a defined X-Y space, you may need to use your image editor and add some white area at the bottom of the image file, such that you can reposition the overlay "letters" bar on top of it and a safe distance from the map image content. Then, one map function in the code, can select any items on the page.

I have a strange feeling you have the skills to make this work yourself. As long as there are no new concepts introduced along the way, just rearrange the goods as they currently stand. You've worked on harder code than this already...

Paul

Compare the working one with the non working one to fix it.

How are you editing the HTML? You might be better off using tools that will let you see the rendered version and HTML source simultaneously. eg

BlueGriffon is freeware. (other brands are available)

Seems like you lost track of which image tag is supposed to present what picture. And because of that, you have an image element which has the same position. The ID attribute is especially useful to identify which is which, or for what purpose.

Backup your `help.htm` file, then replace the contents of the `` tag with below code (long text warning).

Thanks! BlueGriffon.org has screwed us; 64 bit ONLY. ONLY gamers and math mavens have use for even 32-bits; i should know

- i wrote a multi-million digit math package that would run on 16-bit OSes, and pushed to 32-bit then 64-bit environments only when needed. Learned that "memory leaks" are impossible with half-way decent programming, as well as "buffer overflows" being impossible with half-way decent programming.

Got a much older version via CNET; will try it when i get around to it.

Thanks.

Thanks; looks i had some things scrambled, then compounded matters by code messing.

Thanks.

Discovered that image map will not help because of the fundamental problem with the FIND; a href= for FIND in same page does not cut it if one wants this business to "work" over a range of browsers, most especially the Insipid Exasperators.

Found the best way for in-page "jumps" is to use NAV which i new nothing about - not even its existence.

Thanks.

Using a named anchor works best for me for most browsers. For example:

Note: It's best to not use white space in an anchor name in order to accommodate the Insipid Exasperators class of browsers.

------------------------------------------------------------------------

Here's the jump link syntax for your page:

Its anchor:

A:

More info:

------------------------------------------------------------------------

Apparently a Bookmark performs a similar function. But it's unused and untested by me thus far.

The jump link is identical to the anchor method:

Its anchor is simpler:

A:

More info:

Danke,

• Not the same; i needed jumps inside the same page and some browsers did not cooperate; the NAV worked.

• Looks very similar to the NAV thinggie i wound up using.

Thanks,

Within a given webpage either

or

works for me in most browsers so far. Regardless, you have more Insipid Exasperators experience than me. In the end, if NAV works then problem solved.

Danke,