Z-index, make it work with MVThemeBasedFOI and MVFOI

Question

Hello, I'm using MapViewer with javascript library OracleMaps.js(Ver11_B091229). I'm using circles drawn with the MVCircleTool and some layers using MVThemeBasedFOI.
Circle :
* circle drawn event handler
function circleDone()
     var geom = circleTool[nbrCircle-1].getCircle();
     highlightSelection(geom, true);
     circleTool[nbrCircle-1].getCircleFOI().setClickable(true);
     circleTool[nbrCircle-1].getCircleFOI().attachEventListener(MVEvent.MOUSE_RIGHT_CLICK, rClickCircleFOI);
     circleTool[nbrCircle-1].getCircleFOI().setZIndex(999);
As you can see I have a right click event on it(used for contextmenu).
ThemeBasedFOI :
function addThemeBasedFOI(themeview, maxWholeImgLvl, minClickZoomLvl, clickable)
     var themeBasedFoi = new MVThemeBasedFOI(themeview,themeview);     
     if(clickable==true)
          themeBasedFoi.setClickable(true);
          arrayThemes[cptTheme]=themeBasedFoi.getLayerName();
          themeBasedFoi.attachEventListener(MVEvent.MOUSE_CLICK, foiMouseClickEvent);
          themeBasedFoi.attachEventListener(MVEvent.MOUSE_RIGHT_CLICK, mouseRightClickFOI);
mapview.addThemeBasedFOI(themeBasedFoi);
     //set zoomlevel click and whole img level
     themeBasedFoi.setMinClickableZoomLevel(maxWholeImgLvl);
themeBasedFoi.setMaxWholeImageLevel(minClickZoomLvl);
     cptTheme++;
Things work fine individually but together, the MVThemeBasedFOI is over the Circle(it's an MVFOI).
MVThemeBasedFOI index can be changed(if it works) with the MVMapView's method setThemeIndex(MVThemeBasedFOI, index). On its side MVFOI index can be changed by setZIndex(idx) method.
I tried 999(the maximum value) for the circle and 1 for the layer but it changed nothing, the layer is still over the circle. Layer index doesnt work the same as usual zindex(if you see code of OracleMaps.js it's seems to be index*2+130), if index is 1 it should be(if i'm correct) 132, it's under 999 but it does not work.
Any idea on how I can make it work ?

Answer 1

yes that true, changing it later will be problematic. But if we have the break points already figured out and design finalized we just then have to open it in Muse and then add the features that muse has like scrolling effects and such. life would have been really simpler if that media query handle feature from EdgeReflow is placed in Muse. On the other hand i don't mind if reflow has the scroll effects and all the cool things Muse has. Its possible to do a really nice responsive website with reflow and edge animate and then polish your site with dreamweaver and publish it to BC. Just that i like the features of Muse and the ease of designing but it lacks the true responsiveness we need, i know you can give full width and try make it look like responsive and then you have 2 more websites to finish, the mobile and tablet versions of the website. So its a lot of work, it doesn't really make it easy to keep up with this evolving web design industry. So i think i will stick with edge reflow, dreamweaver and edge animate till Muse becomes responsive fully.