I tried the provided WinLift sample in FireFly and noticed that checkboxes do not display correctly with Winlift.
It seems as if the background color is the same as the foreground color (black). The sample shows Option Buttons properly, so I don't know what the problem is. I suspect it has to do with 'how' the default checkbox is built.
Perhaps it's just my machine P4 and Win XP Pro (latest SerPaks)
--Bob
I also have problems on WindowsXP with checkboxes and WinLift, and not just when using Firefly. The checkbox displays normally unless it is in a disabled state, in which case it has exactly the same appearance as the non-disabled state. I have confirmed this in my own code and also in the sample code provided with WinLift Lite (Chrome skin).
There is also some trouble with disabled textboxes and WinLift. They appear completely black until the window is repainted once. This problem, it seems, can be solved by not using native WindowsXP skinning (WindowsXP manifest) and WinLift at the same time.
Checkboxes on the Sample WinLIFT example in FireFly seem to display correctly in a W2K (SP4) OS.
Here is what I see here using the default skin:
(https://www.planetsquires.com/protect/forum/proxy.php?request=http%3A%2F%2Fwww.megapathdsl.net%2F%7Erdrines%2Fimages%2Fwinlift%2Fwinlift-firefly-sample.png&hash=9175bf8c59a773c1d58782bfbf5c2dc16917d23b)
This sample also looks fine in W98-SE so the issue might be XP related.
For sure using WindowsXP skinning (WindowsXP manifest) and WinLift at the same time is not a good idea, you have to choose between the two :dance:
WinLIFT is designed to provide the same look on all windows platforms.
Patrice,
Perhaps we could devise a function that would 'automatically' delete the manifest file, if the system is using Winlift on Windows XP?
Regards,
--Bob
Bob,
About WSA itself it is "passive code" it can do no change in your source code. It acts on the application on the fly once it is running.
Thus, I would rather think it is the programmer's responsability.
FF as a resource option to let you choose if you want to include XP's manifest support or not.
Normally when talking to a highly esteemed programmer, such as yourself, I would agree but... :)
For the WinLift-FireFly combination to work, one program or the other should point out to the user (us) that this combination will produce unexpected results.
I suppose that Paul could simply "uncheck" the environment checkbox when his program see's the user loading the SKSDKAPI.INC
I'll leave this for the experts to determine the best method, only don't leave it up to me, because I'll forget. :P
Best Regards,
--Bob
Hi Bob,
I apologize if my answer sounds a little rough.
To say the truth I never try myself Manifest with any of my WinLIFT applications because I know from my subconscious that it won't work :wink:
Moreover, so far I had only checked FF and WSA on Windows 98 !
No try on W2K nor XP...
My guess was, if it works fine with the limited 64K GDI stack of this pseudo 32-bit OS (98/ME), then it would work like a charm on modern OS.
So far what I can say is that all the provided WSA demos work fine on 98, ME, W2K, XP (without manifest), 2003.
Also at this time there is no real integration between FF and WSA, I mean Paul must first focus on FF specific issues before he could work on this, perhaps he could put this on the list.
No offence taken, Patrice. You sounded just fine to me.
I want to learn to use Winlift properly with FireFly because I see this as the way to build professional looking applications.
While I believe applications must first work well, I would prefer them to look stunning. WSA can provide that, once I get comfortable with it's needs.
From FireFly's viewpoint, good looking apps will sell more FF products. :wink:
Regards,
--Bob
I have just read through this thread and used it to get the check box's displaying correctly in my application, thanks. Maybe Paul could move the 'Enable WinXP Theme Support' to the project level.
I've thought about that too, as I feel it's a bit more logical place to look for it. I've got a few suggestions/comments on the user logic for Paul, but I ain't gonna bother him with it until he's done with the current version changes. He's got enough things flying around simultaneously.