Hello,

I am using the following css

..hiddenDiv2 {
display: none;
}

..visibleDiv2{
display: inline;
}

which works fine after one of the first set of mypitch1 and
notmypitch1 images has been clicked, in that the titles and images for
Tests 2, 3 and 4 all appear in the same place on the page.

After Test 1 though Test 2 appears lower down the page - how can I get
all 4 sets in the same position?

Cheers

Geoff

<div id="test1" class="visibleDiv2">
<h3>Test 1:</h3>
<IMG alt="image" id="a10" src="../assets/images/play1.gif"
onclick="musicSelect(this);">
</div>
<div id="test11" class="hiddenDiv2">
<IMG alt="image" id="a11" src="../assets/images/mypitch1.gif"
onclick="checkThisFirst(this);">
<IMG alt="image" id="a12" src="../assets/images/notmypitch1.gif"
onclick="checkThisSecond(this);">
</div>

<div id="test2" class="hiddenDiv2">
<h3><em>Test 2:</em></h3>
<IMG alt="image" id="a20" src="../assets/images/play1.gif"
onclick="musicSelect(this);">
</div>
<div id="test21" class="hiddenDiv2">
<IMG alt="image" id="a21" src="../assets/images/mypitch1.gif"
onclick="checkThisFirst(this);">
<IMG alt="image" id="a22" src="../assets/images/notmypitch1.gif"
onclick="checkThisSecond(this);">
</div>

<div id="test3" class="hiddenDiv2">
<h3>Test 3:</h3><IMG alt="image" id="a30"
src="../assets/images/play1.gif" onclick="musicSelect(this);">
</div>
<div id="test31" class="hiddenDiv2">
<IMG alt="image" id="a31" src="../assets/images/mypitch1.gif"
onclick="checkThisFirst(this);">
<IMG alt="image" id="a32" src="../assets/images/notmypitch1.gif"
onclick="checkThisSecond(this);">
</div>

On Sat, 26 Apr 2008 18:11:12 +0100, Geoff Cox <gcox@freeuk.notcom>
wrote:


sorted - the problem was in another part of the code!

Cheers

Geoff

Geoff Cox wrote:
> On Sat, 26 Apr 2008 18:11:12 +0100, Geoff Cox <gcox@freeuk.notcom>
> wrote:
>
> sorted - the problem was in another part of the code!

That's one reason why you should always post a URL instead of code snippets.

--
Berg

On Sun, 27 Apr 2008 13:27:52 -0500, Bergamot <bergamot@visi.com>
wrote:

>
>Geoff Cox wrote:
>> On Sat, 26 Apr 2008 18:11:12 +0100, Geoff Cox <gcox@freeuk.notcom>
>> wrote:
>>
>> sorted - the problem was in another part of the code!
>
>That's one reason why you should always post a URL instead of code snippets.

Berg,

the difficulty there is that the site is password protected until
finished ....

Cheers

Geoff

On 29 Apr, 13:30, Geoff Cox <g...@freeuk.notcom> wrote:
> >That's one reason why you should always post a URL instead of code snippets.
>
> Berg,
>
> the difficulty there is that the site is password protected until
> finished ....

I've uploaded your answer, but I'm afraid that Homeland Security
prevents me from posting its location.here.

Geoff Cox wrote:
> On Sun, 27 Apr 2008 13:27:52 -0500, Bergamot <bergamot@visi.com>
> wrote:
>>
>>That's one reason why you should always post a URL instead of code snippets.
>
> the difficulty there is that the site is password protected until
> finished ....

And that stops you from making a test page and uploading it somewhere
that is *not* password protected? Yet you expect us to do that for you...

Not very conducive to getting the you seek, dontcha think?

--
Berg

On Tue, 29 Apr 2008 08:37:26 -0500, Bergamot <bergamot@visi.com>
wrote:

>
>Geoff Cox wrote:
>> On Sun, 27 Apr 2008 13:27:52 -0500, Bergamot <bergamot@visi.com>
>> wrote:
>>>
>>>That's one reason why you should always post a URL instead of code snippets.
>>
>> the difficulty there is that the site is password protected until
>> finished ....
>
>And that stops you from making a test page and uploading it somewhere
>that is *not* password protected? Yet you expect us to do that for you...
>
>Not very conducive to getting the you seek, dontcha think?

You are right - will do that the next time. All is well now - I found
an error in another part of the code.

Thanks

Geoff