This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I thought the task would be really quite simple ... Create a WPF base class composed of four TabControls ("Main", "Notes", "ChangeLog", and "Warnings"). Then, create descendent controls that used this base control to build upon. For example, a "Customer" module would have labels and textboxes for "First Name", "Last Name", etc. located on the base "Main" TabControl and there would be associated customer-related notes on the "Notes" TabControl, and customer-related warnings on the "Warnings" TabControl, etc. I started out by creating a WPF application and then adding a Custom Control (called "CCBase"). I chose a custom control vs. a user control because of the "XAML cannot inherit from XAML" argument. So I'm trying to create this base Custom Control with the TabControls on it that I can reference with other controls. Any ideas? Should I add additional Custom Controls to my project in an attempt to build on this base Custom Control with TabControls, or should it be a User Control, or maybe something else entirely? |
|
|
|
|
If I've understood your question correctly, this isn't really an issue with the WPF Elements product, but a general WPF control design question. Questions like that are probably better directed to a general forum such as Stack Overflow or the MSDN WPF forum; this forum is specifically for support and discussion of the WPF Elements product. If I've misunderstood your question and you are having an issue with WPF Elements, then could you maybe clarify the Elements-specific part of the problem? Thanks! |
|
|
|
