FoxInCloud
Re: pageframe webactivecolors
Messages
Reply
Edit
Delete
Jan. 7, 2013
08:30 am
3OQ0I8S6P![Show this entire thread in new window]()
08:30 am
3OQ0I8S6P
| From: | Thierry Nivelet (FoxInCloud) |
| To: | Tuvia Vinitsky |
We fixed that recently, just update your FiC package from our server (still 1.26 ...).
like this?
IF NOT thisform.wlHTMLgen thisform.pageframe_1.ActivePage = 1 thisform.pageframe_1.page1.ForeColor= RGB(0,255,0) thisform.pageframe_1.page1.BackColor= RGB(0,0,255)ENDIF
BTW, in 1.26 when I set a page of a pageframe to enabled = .f., the mouse becomes the wiaint cursor when I am over that page tab, and yet I can still click the page tab and access it. It seems to be spinning in some sort of loop.
Please note that, for this mechanism to work, pgf.Init() should activate a default page and set its .ForeColor and .BackColor accordingly
IF .wlActivePageColors, color differences between active and non-active pages are (should be) reflected in the browser.
This applies to .ForeColor and .BackColor.
demo'd here:
foxincloud.com/CTBtest/
login: demo
pass: demo
http://foxincloud.com/CTBtest/analyse.bsw
That property seems to have no effect on the appearance of the active or inactive colors.
Thierry Nivelet (FoxInCloud)
Never explain, never complain (Queen Elizabeth II)
