|
Hi,
I am developing WPF custom control. I need unquie control_Id for each Control in the XAML. when a user drags and drops a control into the XAML window , I can generste the unique identifier in the control constuctor. But when a user copy & paste a control. the CtrlID which is generated in the Constructor is overwritten by previous control's(which is copied) CtrlID in the XAML.
e.g. -
<Window x:Class="TestDemo.xml.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Title="Window1" Height="600" Width="800" Resources="TestDemo.xml" xmlns:my="clr-namespace:Philips.PmsMip.Private.Tools.Services.FSF.StudioNew.Controls;assembly=Philips.PmsMip.Private.Tools.Services.FSF.StudioNew.Controls">
<Grid>
<big> <my:FSFComboBox Height="23" HorizontalAlignment="Left" Margin="257,202,0,0" VerticalAlignment="Top" Width="120" ControlID="ComboBox633632137614182049" />
<my:FSFComboBox ControlID="ComboBox633632137614182049" Height="23" HorizontalAlignment="Left" Margin="10,10,0,0" VerticalAlignment="Top" Width="120" />
</Grid></big>
</Window>
Is thr any way I can know in constructor or anywhr in custom control's code that this control is being created by Copy an already existing control.
|
|
|
|
|
I am essentially running an application that creates a thread to run a Form, say Form1 by calling...
Application.Run(new Form1());
Then, the application runs another process. This creates a Form, say Form2 in the same way that Form1 was created, by calling Application.Run(). The problem is that Form1 is on top of Form2, even though right before the Application.Run() call of Form2, I call BringToFront(), which is supposed to place it at the front of the z-order. Why is Form1 on top of Form2 even though Form2 was created afterwards, and explicitly brought to the front? I would like to do this without having to call SendToBack() on Form1, since I don't want to send it all the way back, I just want it to be behind Form2.
|
|
|
|
|
Wrong forum. This is for WPF, WCF and WF - not Windows Forms.
|
|
|
|
|
Woops, I thought WF == Windows Forms.
I'll re-post in that forum then.
Thanks.
|
|
|
|
|
No problems - and an easy mistake to make.
|
|
|
|
|
I'm developing an app with a tree control in the left 'pane' and a dialog in the right. As the user selects items in the tree, the contents of the dialog in the right pane changes.
In my C++/MFC apps, I made the contents of the right pane modeless child dialogs. As the user selected items in the tree, I would destroy the current dialog and create a new one of the requested type.
My question: What's the best way to do this in a C#/.NET/WPF application?
I've found the following method that seems to work.
I can make the right-hand pane a System.Windows.Controls.Frame. Each 'dialog' is a System.Windows.Controls.Page. I can switch dialogs using frame.Content = new DetailPage();. I can also switch dialogs using frame.Source = new Uri("pack://application:,,,/DetailPage.xaml");.
Is this approach okay, or is there a simpler/better way to do this? I'm a newb at .NET, so I have no idea what the 'best practices' are.
Software Zen: delete this;
|
|
|
|
|
Gary - this sounds like an ideal candidate for a bit of juicy two-way databinding and synchronisation. Can I suggest that you take a look into the Composite UI Application Block here[^]? The samples and concepts will really help you.
|
|
|
|
|
Hmm. I took a quick look. The 'CAB' appears to be fairly complicated, and may be overkill for what I'm doing. Also, the mix of WinForms and WPF is a little off-putting. I thought that WinForms has been 'deprecated' now that WPF is available?
My application is actually a touch-screen control panel for some machinery. The 'tree control' in my example may actually be a picture of the machine. When you click on parts of the picture, you see detail information related to that component.
I'm not too worried about the architecture of the application. I was mostly interested in the mechanism I was using for changing the content of the detail view. It seemed like there were several ways to accomplish what I was after, and I wasn't sure if there were any I should avoid.
For example, instead of using a Frame as a container and Pages for the contents, I could use a Grid and set the appropriate Grid entry to a UserControl. Each detail view would then be implemented as a UserControl.
Thanks for the info; I'll keep it in mind.
Software Zen: delete this;
|
|
|
|
|
Gary - you don't have to use the WinForms parts, however, if this architecture is too much you might want to consider using MVVM. The idea of using UserControls is a good one, and is a good basis for doing this. Obviously, you would want to bind to the selected item on the treeview to decide which usercontrol to load.
|
|
|
|
|
That's pretty much the outline I had in mind. We've developed this sort of application before using an MVC pattern. MVVM sounds like MVC with some of the serial numbers ground off  . Thanks for the feedback, Pete.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: MVVM sounds like MVC with some of the serial numbers ground off
Shh. You're not supposed to notice that.
Gary Wheeler wrote: Thanks for the feedback, Pete.
You're welcome.
|
|
|
|
|
I wouldn't use a frame for this. Have a look at ContentControl it can be a 'host' in a Grid for the user controls you create for the right hand panel.
|
|
|
|
|
Hi everybody. I've had EB2 SP1.
Whenever I wanna create an event in SilverLight 2 I receive this[^] error What's wrong with it ?
How can I solve it ?
( By the way I have VS2008 SP1)
Thanks in advance.
|
|
|
|
|
The error occurred because I didn't have VS2008 SP1[^] with SL2 tools[^].
When I downloaded and installed them , my problem solved.
|
|
|
|
|
i have created a user control Dynamically and added it to a Wrap Panel as a child. now if i remove it from panel but it still remains in memory.
i want it to be permanently removed from memory. There is no Dispose method available. and i also tried by implementing idisposable interface and overwriting the Dispose() method for my control but it still remain in memory.
Is there any way to remove this object(User Control) from memory
Regards
Rishi
|
|
|
|
|
RishiKasnia wrote: Is there any way to remove this object(User Control) from memory
Nope. WPF uses MIL handles internally, and the garbage collector is called as and when it is needed. When you think about it, this makes perfect sense - the whole point of WPF is that it doesn't need you to access unmanaged resources to do things (you can, but you aren't required to) so you don't actually need to Dispose controls.
|
|
|
|
|
Thanks Pete for reply
but in my case i need to remove this user control from memory . becoz after removing it from canvas or panel , if i try to fire some event then this Control also respond the event (Though it has been removed).
for a workaround i detached the Event Handler for user control(when i remove it from canvas/panel). but it still resides in memory and remains throughout the program execution (becoz this control is not local to any Block) thus degrading performance .
Regards Rishi.
|
|
|
|
|
Unfortunately you can't automatically remove the control deterministically. You could, possibly, remove the control by forcing a garbage collection, but this really is a bad idea.
|
|
|
|
|
Hi,
I have created service in which I am fetching data from database write that in xmldocument and returning XMLDOCUMENT.
But it raised error in client page
"System.Xml.XmlDocument" can not serialized.
is anybody have any solution.
Thanks,
Nagraj
|
|
|
|
|
|
This sort of thing really pi**** me off ...
|
|
|
|
|
Dude, calm down. You should pity these fools for being both stupid enough to need this type of help to start with and being desperate enough to spam all sorts of forums to find it. 
led mike
|
|
|
|
|
You really need to start doing the Mr T voice here. "Pity this you crazy fool" 
|
|
|
|
|
Pete O'Hanlon wrote: You really need to start doing the Mr T voice
I did. Apparently you did not hear my post correctly. 
led mike
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
