Ident wrote:Anasky wrote:Modifying Falagard does sound like a tougher solution than I initially thought though... I'm assuming you don't have experience in this? (And if you do, got any starting point for me?)
I do have experience in this and the reason I initially advised against it is that it is not very intuitive to work with it and it gets more complicated once you add so called child "auto" windows in falagard, in which case it is often better to add actual real windows, especially if it is just about looks and not functionality related to the parent widget. I wrote a base for a Look N Feel editor for CEED to make it easier to create and edit skins but in its current form it will not help you much either yet, it is also not tested enough.
Can you explain what you mean by "The issue with it though is the AlwaysOnTop=true property. "
Who has this property and why cant you turn it to false ?
Apologies for my slow reply rate. Doing this in my spare time alongside my actual job...
What I currently have:
-> A FrameWindow with the 9 images defined.
-> Code creates a new FrameWindow
-> A separate StaticImage defined
-> Code creates a new StaticImage, with as parent the FrameWindow
-> The StaticImage gets hidden and cropped by the frame of the FrameWindow
-> To solve this I set the property AlwaysOnTop to true, along with ClippedByParent to false.
I am fine with disabling ClippedByParent, but the AlwaysOnTop (which is required to be above the FrameWindow's frame) means it's on top of EVERYTHING instead of just the frame.