Messages
Reply
Edit
Delete02:07 am
3OT04KLT4
| From: | Thierry Nivelet (FoxInCloud) |
| To: | Tuvia Vinitsky |
or
ifthis.serverVersion < 1.xxx) or this.FiCStyle && new prop in xxx.jselse&& CSS stylingendif
But as I think about it, probably that would be a duplicate effort, just do in CSS.
But use the form props to auto-gen css to keep the functionality.
This looks like an excellent idea, we'll try that ... of course it'll remain subjected to the 'dynamic CSS' issue in dev mode ...
If it works, we'll have to ignore all the automatic styling code from foxincloud.js!FoxInCloud.pgfMake().
Thus Server and foxincloud.js will have to be in sync:
if (this.serverVersion < 1.xxx) {automatic styling}else {CSS styling}
Can you add an attribute "active=active" like you did with disabled? Then you could just let your developers have to deal with the tab CSS and you could not deal with the js of adjusting the tab appearance. Between hover, active, and disabled, CSS could cover it.
Thanks. I was of course running in debug mode. I see what you mean.
However that does not seem to affect the color switching not working. Should all the props appear correctly first drawing in development mode? I will check again.
As you know, in dev mode, FiC generates a dynamic CSS:
(function(){var o = $$('link[type=text/css][href^=/ucsTest/awDefault_]')[0];if (o && !o.href.endsWith('/ucsTest/awDefault_3OS0R5UW2.css')){var p = o.previousSiblings()[0]; o.remove(); o = Object.extend(document.createElement('link'), {href:'/ucsTest/awDefault_3OS0R5UW2.css', type:'text/css', rel:'stylesheet'}); p.insert({after:o}); } })();
Until now, we've found no way to make this dynamic CSS file taken into account immediatly;
So, when pageFrame widget executes, the page styles (defined in the dynamic stylesheet) are not up-to-date, thus the 'weird' effect you see.
When reloaded the same form looks OK.
Please note that this happens only in development mode: production mode uses the global 'awDefaultAll.css' stylesheet generated by xxxProd.css.prg, which is defined once for all.
Also, the height of tabs where enabled=.f. is always drawn only a few pixels high. It does not matter if the other tabs are drawn with FiC default or with specific size.
Not even close. Also the tabs start out raising and displaying poperly, but after switching to any other than the iniial tab, all the tab fonts revert to a small font and stay that way and no more special effects. I have
wlactivepagecolors = .t.
wlactivepagehighlight=.t.
wnactivetabraise = 2
wntabmargin=2
pgf.init:
IF NOT thisform.wlHTMLgen
*this.ActivePage = 1
this.Pages[1].activate()
RETURN DODEFAULT()
ENDIF
in each page.activate:
IF m.thisForm.wlHTMLGen
RETURN .T.
ELSE
THIS.PARENT.setAll('BACKCOLOR', RGB(116,189,46) , 'PAGE')
THIS.BACKCOLOR= RGB(255,255,255)
ENDIF
But when it loads I get this (two tabs are disabled):
Then when I click on the middle "leave info" tab I get:
should be close to that
PROCEDUREpageframe.Initthis.Pages(1).ActivatereturnDoDefault()ENDPROCPROCEDUREpageframe.somePage.activateIF m.thisForm.wlHTMLGen RETURN .T.ELSETHIS.PARENT.setAll('BACKCOLOR', inactivePageRGB, 'PAGE')THIS.BACKCOLOR=activePageRGB ...ENDIFENDPROC
Still unclear what code goes in pgf init to get that appearance.
Thierry Nivelet (FoxInCloud)
Never explain, never complain (Queen Elizabeth II)