Jump to content

ctoz

Members
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ctoz

  • Rank
    Newbie
  • Birthday 03/17/1941

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Location
    blackwattle bay NSW
  • Interests
    degrading gracefully
  1. yesbut if one puts in padding it's usually for a reason never mind the code, thanks all for straightening my head.
  2. ... thanks. I remember now. And "_target", which I also tried at some point, didn't work either. Muddled thinking.I only need the page to return to the top from a link at the bottom, in this case about three window-heights down. Reloading the page is ok. (I t also gets Safari to the very top, whereas Safari only seems to go to the first element with <a href="#top">. )
  3. Yup. Well no, the above will do: but it obviously wouldn't do if I wanted to link to #somewhere_else in the page.To recap: IE6 (not standalone, it's on same pc as IE7) would not respond to<body><a name="top"></a><a href="#top">...</a> So I went looking for something that worked for IE6 too. I didn't then think my code was a problem.I found in the W3Schools tutorials pages a version with the underscore hack: <a href="#top" target="_top">top of page</a> which works for them, and confirmed me in thinking there was a problem with IE6. But that didn't work on my page either. It gave an error message on both 6 and 7.And essentially, after two round with Opera, that puzzle still exists. Except I've changed the code on the page to the "reload version" above. So I guess I should run the css and the code thru a validator, and try again. There's a lot of layers and clunky js on links at present, which logically shouldn't be a problem but u never know. I'll make a fresh post if I can't solve it.
  4. The Browsers (ie6, ie7, ff, opera, safari, and mac ff, opera, safari) seem to like this:at the top of the page: no anchor at all;and at the bottom: <a href="filename.htm">top of page</a> beats me
  5. Sorry, I was looking for "name=" and missed the "id". I did an offsite test with "id" and I think sOK now....Except IE6.
  6. hmmmyours works all round, with no anchor. I'll try that. Cheers.
  7. That ws the problem I referred to. Take of the target and IE6 didn't respond.Never mind, I just took it al back to a href="#" and seems ok all round. Except Opera. What does Opera like?Scratches head: Opera likes <a href="#top" target="_top">
  8. However, the code I posted works for w3schools in IE6 and 7, but not for me, so I'm none the wiser: and your suggestion, tested offsite, gives the same error messages as the code I posted. The link is absolutlely positioned, maybe that's the problem? Have a look for it: "bad jokes I love 'em" on the bottom right of the page
  9. <body><a name="top"></a><a href="#top" target="_top"> For the above link and target (copied from your typical W3schools tutorial, "top of the page" link) I'm getting eror messages in IE6 and IE7: but when you follow the eror message suggestions ("back" for 6, and "refresh" for 7) you do get back to the top of the page.I originally had the problem of 6 being dead to href="#top".Any suggestions?
  10. Many thanks! a a big credit... I won't get time to work on it for a couple of days. I was in two minds about launching into an explanation.best wishesctozi have the randomising function and a series of splits scripted: they'll be the next test.
  11. came across this, might be useful:http://www.simplebits.com/notebook/2004/07/18/clickable.html
  12. I agree it looks wrong: do you have a suggestion? Bear in mind you're dealing here with a cut'n'paster rather than a writer. I think this is what's needed. Multiple classes would have been one simpler way: I did try two getbyClass scripts, but each caused a conflict with other essential scripts based on getbyID, which I couldn't solve/get responses on... so I decided to do all manipulations (essentially there are three manipulations, this being the third) using IDs. It's clunky, but it works.As to what it's trying to do (apart from keeping Alzheimer's at bay ): if I said, "keeping track of the moving lines as you build a hexagram", that would be a short description. I could give you several links (google "I Ching"), but it's also useful for me to try to describe the process. Here goes:A "hexagram" is a diagram with six lines, one above another; each line is either solid ----- or broken -- -- . There are 64 combinations. You arrive at one of these fortune-cookies by making a random choice, six times, one for each line. Your random choice has only 4 outcomes: 6,7,8,9.6 and 8 reduce the field to a specific set—hexagrams with the first line broken; 7 and 9 to the complementary set. After six iterations, a single hexagram remains.I've set up the 64 hexagrams as a field, with each iteration reducing the possibilities, accomplished by manipulating a series of arrays. The arrays allow progressively turning off the unwanted hexagrams, rather than just switching them all off at once, which one could do using classes... We haven't gotten to the script in question yet.As well: At any iteration, an outcome of 6 or 9 changes the potential of that line, so that it will subsequently become its opposite, thus generating a second hexagram. In the parlance, 6 and 9 are "moving lines". Now, switching on and switching off the symbol associated with the moving lines requires as much specificity as the arrays associated with the hexagrams; but assigning 64 x 6 ids and then divvying them up into arrays looked a bit over the top. Instead I've coded the structure of the hexagram into the id of each of its moving-line-symbols, as well as having that id identify which line it relates to... hence, "charAt" as a way to turn the symbol on and off. The test page doesn't incorporate the randomising function: it just allows each outcome of each iteration to be tested, by clicking on the appropriate link. Each iteration will appear to grey out half the hexagrams (actually there's a layer of grey hexagrams beneath); then mark the line by turning it red; then mark if it is a moving line by placing a red dot (the script in question) to the right of the line.The final link, "second hexagram", shows the hexagram made when the moving lines change into their opposites. It's on a separate layer hitherto unseen. It's very slow tonight.
  13. [sigh] On a mac, I'm getting a white box with a big black border, in three browsers, nothing else. This is after having replaced the < with an opening < at the script tag (otherwise the script shows at the top of the page in grey), using a substitute image, and separating the 'no-repeat' from the background url closing bracket. So, there's still a problem somewhere.What I did see, although I don't understand why it might affect the background-image, is a mis-match between the css #navigationcontainer ul li { display: inline;} and having <h2>, which is a block element, wrapping the <a> tag.There are several css errors, check athttp://jigsaw.w3.org/css-validator/cheers
  14. background: #000000 url(images/buttona.png)top left fixed no-repeat; should work, but better with a space after the bracket: #000000 url(images/buttona.png) top left fixed no-repeat; Note that you can apply colour to "background", but not to "background-image"—but this is not a lot of help. Put it through a validator: you need to be spot-on, no errors, if you're using a strict DTD. The opening of the script tag looks wrong.
  15. I have this function — some here will recognise their input — which twice looks at a collection of elements and each time does something different with them, depending on a particular character in the ids: function dot0() {for (i=0;i<document.getElementsByTagName("span").length; i++) {if (document.getElementsByTagName("span").item(i).id.charAt(6) == "1") { document.getElementsByTagName("span").item(i).style.display = "inline" }if (document.getElementsByTagName("span").item(i).id.charAt(0) == "b") {document.getElementsByTagName("span").item(i).style.visibility = "hidden" }}} I need to use variations of this twelve times on the page, so it's worth trying to make it generic. You can see the variations operating here, with its linked "/engine.js"where they progressively show and hide the little red dots to the right of the red lines (yup, it's obscure... ) I can describe in English, but getting it into script may be beyond my current knowledge level. There's an attempt below.In the first "if" statement, it's always "charAt(6)", but the identifer at 6 changes:eg, charat(6) == 1, charat(6) ==2, etc; and it is always "display= inline".In the second call, both the charAt() number and the identifer at that number both change: eg, charAt(0) == a, charAt(0) == b, charAt(1) == a, charAt(1) == b. etc; and in this call, it's always "visibility= hidden".What I'm most uncertain about is how to treat the charAt() part of the "if" statements: function dot(char6, DIS, charWhich, VIZ) {for (i=0;i<document.getElementsByTagName("span").length; i++) {var char6 = document.getElementsByTagName("span").item(i).id.charAt(6); DIS = char6.item(i).style.display;var charWhich = document.getElementsByTagName("span").item(i).id.charAt(); // stumped here ! VIZ = charWhich.item(i).style.visibility }} and the call would be something like dot(char6,'inline','0' (or whatever number), 'hidden'). Grateful for anyone with the patience to follow this thru !
×
×
  • Create New...