|
By definition, a "modeless" dialog is not a dialog; it's just a window. A dialog is a dialog when it's "modal".
And if there's a window "hanging around", it means the app is NOT "closed". In fact, you can hide all the windows, and the app is still not (automatically) closed.
You should "close" a window when you no longer need it.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
I wrote an article:
WPF - Modeless Window Manager[^]
This code will automatically close any modeless windows that are open when the app is closed. Kinda handy...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I wrote an article:
WPF - Modeless Window Manager[^]
This code will manage the modeless window for you, and provides several handy features.
In my own code, I instantiate all windows from the UI, but if it's more handy for your app to instantiate a view from the viewmodel itself, go forth and break tradition.
Remember, all of the "rules" you read are actually just guidelines. Yes, you should strive to follow industry best-practice, but you should also be flexible enough to know when you can step outside the box.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Visual Studio 2019 --- Windows Forms App (.NET Framework) C# ... Toolbox => Data => Charts provides the ability to create xy plots.
This does not exist in WPF APP (.NET Framework).
I've found multiple sites that demo a variety of shapes using .xaml and .cs. But none that demo a combo of both for an xy plot (not predefined shapes), where the .xaml defines the location and the .cs provides the data.
How do I create xy plots with WPF APP (.NET Framework)?
-- modified 18-Oct-21 11:00am.
|
|
|
|
|
Google will find you lots of WPF chart controls, both free and commercial.
I haven't used it, but this one looks good, and is both free and open-source:
GitHub - beto-rodriguez/LiveCharts2: Simple, flexible, interactive & powerful charts, maps and gauges for .Net, LiveCharts2 can now practically run everywhere WPF, WinForms, Xamarin, Avalonia, WinUI, UWP, MAUI (WIP), Blazor-wasm (WIP)[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Windows Forms has an "MS Charting control"; WPF doesn't (have an "MS" charting control).
However, you can host the MS Chart control in a WPF window.
Using Microsoft Chart in WPF
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Do you have a code example? Thanks!
|
|
|
|
|
Something wrong with the link / sample?
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Sorry. I did not recognize that as a link.
When I add to .xaml
<pre>
<Grid>
<WindowsFormsHost>
<wf:MaskedTextBox x:Name="mtbDate" Mask="00/00/0000"/>
</WindowsFormsHost>
</Grid>
</pre>
I get this message "WindowsFormsHost is not supported in a Windows Presentation Foundation (WPF) project."
[not sure how to properly format code for this forum]
|
|
|
|
|
Ignore the chart, look up how to paint yourself in WPF. Simple hint, you use a for-loop to draw dots.
Was bloody easy in WinForms, so WPF should be easier.
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I don't believe that's what the message said because you are not trying to host a "chart" as you posted; that's a "masked text box" you're fiddling with. Focus should be your primary objective.
xmlns:dv="clr-namespace:System.Windows.Forms.DataVisualization.Charting;assembly=System.Windows.Forms.DataVisualization"
<WindowsFormsHost x:Name="uxHost"
Grid.Row="1"
Grid.Column="0"
VerticalAlignment="Stretch"
HorizontalAlignment="Stretch">
<dv:Chart x:Name="uxChart" />
</WindowsFormsHost>
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Solution:
Using the template on this web site - stackoverflow.com/questions/33756255/create-a-math-plot-in-c-sharp-xam
.xaml
<Canvas x:Name="gCanvasPlot0"
HorizontalAlignment="Left"
VerticalAlignment="Top"
Margin="0,0,0,0"
Width="500"
Height="150" />
.cs
//------------------------------
private void AddPlot()
{
double dPI = Math.PI;
Polyline poXY = new Polyline {
Stroke = Brushes.Red
};
int iNumOfCycles = 3;
double dDeltaX = 0.01;
int iNumOfPoints0 = (int)(iNumOfCycles / dDeltaX);
for (int ii = 0; ii < iNumOfPoints0; ii++) {
double dX = ii * dDeltaX;
double dY = Math.Sin(2 * dPI * dX);
poXY.Points.Add(CorrespondingPoint(new Point(dX, dY), iNumOfCycles));
}
gCanvasPlot0.Children.Add(poXY);
}//AddPlot
//------------------------------
//------------------------------
private Point CorrespondingPoint(Point pt, int iNumOfCycles)
{
double dXmin = 0;
double dXmax = iNumOfCycles;
double dYmin = -1.1;
double dYmax = 1.1;
double dPlotWidth = dXmax - dXmin;
double dPlotHeight = dYmax - dYmin;
var poResult = new Point {
X = (pt.X - dXmin) * gCanvasPlot0.Width / (dPlotWidth),
Y = gCanvasPlot0.Height - (pt.Y - dYmin) * gCanvasPlot0.Height / (dPlotHeight)
};
return poResult;
}//CorrespondingPoint
//------------------------------
This works.
-- modified 18-Oct-21 11:02am.
|
|
|
|
|
Right. Now you can start thinking about axis labels, legends, titles, data sources, etc.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
(shrug, should have posted this here before, newbie error)
I have a UI with a scrollviewer like this:
I want to scroll the viewer to the top when the ItemSource changes.
<ScrollViewer x:Name="Scroller" Grid.Row="2" Margin="0,0">
<StackPanel>
<ItemsControl x:Name="containers"
ItemsSource="{Binding Whatever, NotifyOnTargetUpdated=True}"
TargetUpdated="Containers_OnTargetUpdated">
</ItemsControl>
<StackPanel>
<ScrollViewer>
public partial class MyPage: UserControl
{
public MyPage()
{
InitializeComponent();
}
private void Containers_OnTargetUpdated(object? Sender, DataTransferEventArgs E)
{
var MyScroller = (ScrollViewer) this.FindName("Scroller");
MyScroller.ScrollToHome();
}
}
This works but it's probably not the best way to do it (ie. finding a control by name).
Can I pass the ScrollViewer "object" to the TargetUpdated callback/event ? so that I don't have to referencing it by name?
It seems clunky.
I don't know exactly what magic incantations I need to google for.
Thanks. M.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Already answered in the C# forum:
Re: (xaml, wpf) ScrollViewer Binding confusion (beginner) - C# Discussion Boards[^]
private void Containers_OnTargetUpdated(object? sender, DataTransferEventArgs e)
{
var current = sender as DependencyObject;
var scroller = current as ScrollViewer;
while (scroller == null && current != null)
{
current = VisualTreeHelper.GetParent(current);
scroller = current as ScrollViewer;
}
if (scroller != null)
{
scroller.ScrollToHome();
}
}
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I don't understand your apprehension about the "direct" approach ... or is this another "MVVM" thing?
private void Containers_OnTargetUpdated(object? Sender, DataTransferEventArgs E) {
this.Scroller.ScrollToHome();
}
The compiler recognize the name you gave to the ScrollViewer in the XAML (for that page / control); you don't need "reflection" in this case.
For other "public" cases, add a public "getter" for the control in question.
I assume you have some idea when the ItemsSource to the list is changed; set the scroll then if event handling is too confusing.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
I'm working on a piece of UI where the user enters a dollar amount. The field is bound to a decimal.
Whenever I press the decimal point, here's a pic of what I get
Here's the xaml:
<TextBox Grid.Column="5"
Text="{Binding Entity.InvoiceAmount, StringFormat=C, Mode=TwoWay, UpdateSourceTrigger=PropertyChanged}"
Margin="2"
Width="200"
Style="{StaticResource textBoxStyle}"
TextAlignment="Right"
IsEnabled="{Binding AreFieldsEnabled}"/>
The only way I can seem to change the decimal portion is to arrow over to it.
What's wrong here?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
It's the same problem you had entering a percentage back in April:
Re: Format Percentage - WPF Discussion Boards[^]
Change UpdateSourceTrigger to LostFocus instead of PropertyChanged.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
How did you remember that?? I totally forgot I posted that.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I've done this both ways, but I'd like to hear what you guys do....
Bind The Entity
Have the VM get an entity, or pass it in to the CTOR, store the entity to a property on the VM, and bind the View to the entity's properties.
With this approach, the only way to 'undo' is to requery the data, but it's easier to set up and maintin, IMHO.
Bind To VM Properties
Have seperate properties on the VM for everything bound on the View. Load those properties from an entity. Then, when saving, create or update an entity from the VM and save it.
To Undo, simply reload the VM's properties from the entity. But it's another set of properties on the VM mirroring those on the entity.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I always had the properties declared in the VM, loaded from the model which reflect a view from the database. However I have a tool that generates the code from the database to the model and a region in the VM so refactoring effort is minimal.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
The first approach is really a "cheating" MVVM approach. You might as well not bother having the VM in there at this point because your view is almost binding directly to the model with only the thinnest of abstractions sitting on top. One of the purposes of the VM is that it is there to act as a guard for your model; suppose that I have a requirement that a model can only be saved if field_A is set and then field_B contains a value from 0 to 10, but if field_A isn't set then field_B can accept anything from 0 to 30. The VM is the place to ensure that this guardrail is enabled; it ensures the model is always pure before you attempt to save it.
|
|
|
|
|
Pete O'Hanlon wrote: The VM is the place to ensure that this guardrail is enabled
Global validation rules should probably be enforced in the entity and the database as well wherever possible. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I use all "three"; depending on the situation. And sometimes all 3 at the same time.
There's the POCO; no "brains"; just getters and setters.
Then there are "is valid" getters, etc.; the "smart" POCO.
Then there are the Observable collections of same; bound to a lists and views at the same time ... with the selected POCO showing in a view ... which could be controls on a map.
Binding the POCO could be simple a DataContext assignment; or it is completely or partially aided by view getters into the POCO (view model).
e.g. if I want to show "full name" and I have "first" and "last", the obvious thing is to make a "full name" getter ... in the POCO or in the view. Variants of the ToString() override. The list goes on.
"Classic" MVVM is only one strategy ... and a very narrow one at that.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
When I instantiate a VM, it typically instantiates the model on its own, which retrieves the data (from a database, xml, or json file).
If the requirements call for modifying/saving the data, I keep the model around in a protected property inside the viewmodel.
Most of the time, I set the data context to the form, and bind controls to the viewmodel(s) and various other properties. I don't think I've ever set the data context to a specific viewmodel because that just means more typing.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
