[TYPO3-dev] Strange behavior of tx_overlib

Joerg Schoppet joerg at schoppet.de
Sun Mar 26 22:39:16 CEST 2006


Hi list,

I've a strange behavoir with the implementation of tx_overlib in my 
extensions.

In one extension everything works fine, I included class.tx_overlib.php, 
called "tx_overlib::setDefaults;" and "tx_overlib::includeLib();" and in 
the frontend I see the following javascript:
<script type="text/javascript">
	/*<![CDATA[/*
	function T3_onmousemoveWrapper(e)	{	overlib.mouseMouse(e)	}
	function T3_onloadWrapper()	{	overlib.init();	}
	document.onmousemove=T3_onmousemoveWrapper;
	document.onload=T3_onloadWrapper;
	/*]]>*/
</script>
<body onload="T3_unloadWrapper();">

On another site this doesn't happen. If I debug a little bit I see the 
following strange behavoir.

In my extension after the "tx_overlib::includeLib();" call I made 
"t3lib_div::debug($GLOBALS['TSFE']->JSeventFuncCalls);" (call intern)
and in class.t3lib_pagegen.php in made the same in the function 
"JSeventFunctions()" (call extern).

On the site where everything works I get the debug in the following order:
- call intern
- call extern
=> everything is ok

On the site where it doesn't works I get the debug in the following order:
- call extern
- call intern
=> IMHO it is clear, that it doesn't work, because the javascript output 
is made before overlib sets the necessary information. But why?

What can I do?

Joerg




More information about the TYPO3-dev mailing list