Ask a Question related to Macromedia Dynamic HTML, Design and Development.
-
O'Shanahan webforumsuser@macromedia.com #1
Re: Some layers become visible, others refuse!! help!!
wow, thanks for your in-depth reply with such attention to detail...I really appreciate your help! I will go and look at the code now with your comments in mind and see if I can change things for the better. One immediate point....surely for this problem it doesnt matter at all about the mmShowhideLayers functions in any layers other than 'main' because it is this layer ('main') that is initially functional and visible. Therefore surely the mistake must lie in this layer (unless there is some sort of "onLoad" behaviour in the 'HOME' layer that hides the layer on load after the button"HOME" is clicked in the "main" layer)....but where I dont know!!
I will amend the code in the initially invisible layers to ensure that each of the mmShowHideLayers functions shows AT LEAST one layer.
Pete
O'Shanahan webforumsuser@macromedia.com Guest
-
Sites refuse to serve
Recently, our extranet and intranet servers have been dying 2-3 times a day. There is no response from any browser either by URL or IP. The IIS... -
WU-FTP Q?: How to refuse users with an invalid home dir
Hi, is there a way that WU-FTP can be configured to disallow users to connect that have no valid home dir? We had some trouble with permissions... -
Can I refuse all connections except replication?
Informix 9.30 running on AIX 4.3.3 I have two instances running EDR in update anywhere mode. All connections are usually made to the "primary"... -
2.6.0-test1: some modules refuse to autoload
My apologies if this is a repeat... I originally sent it yesterday evening, and haven't seen any sign of it on the list. --- I'm starting to... -
Datagrid events refuse to fire (pt 2)
Further to my earlier post the following events DO fire - ItemDataBound ItemCreated DataBinding Load PreRender UnLoad and the following... -
Murray *TMM* #2
Re: Some layers become visible, others refuse!! help!!
Pete:
You're welcome!
At the end of it all, I am pretty sure your problem stems from duplicate
names. Check that first....
--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]news://forums.macromedia.com/macromedia.dreamweaver[/url] - THE BEST WAY TO GET
ANSWERS
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.DreamweaverFAQ.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================
"O'Shanahan" <webforumsuser@macromedia.com> wrote in message
news:bdcmc8$hi5$1@forums.macromedia.com...really appreciate your help! I will go and look at the code now with your> wow, thanks for your in-depth reply with such attention to detail...I
comments in mind and see if I can change things for the better. One
immediate point....surely for this problem it doesnt matter at all about the
mmShowhideLayers functions in any layers other than 'main' because it is
this layer ('main') that is initially functional and visible. Therefore
surely the mistake must lie in this layer (unless there is some sort of
"onLoad" behaviour in the 'HOME' layer that hides the layer on load after
the button"HOME" is clicked in the "main" layer)....but where I dont know!!each of the mmShowHideLayers functions shows AT LEAST one layer.>
> I will amend the code in the initially invisible layers to ensure that>
> Pete
>
>
Murray *TMM* Guest



Reply With Quote

