MrSeanKon
New Member
- Joined
- Nov 14, 2006
- Messages
- 267 (0.04/day)
- Location
- Athens in love with Anna :)
System Name | BY-2021 |
---|---|
Processor | AMD Ryzen 7 5800X (65w eco profile) |
Motherboard | MSI B550 Gaming Plus |
Cooling | Scythe Mugen (rev 5) |
Memory | 2 x Kingston HyperX DDR4-3200 32 GiB |
Video Card(s) | AMD Radeon RX 7900 XT |
Storage | Samsung 980 Pro, Seagate Exos X20 TB 7200 RPM |
Display(s) | Nixeus NX-EDG274K (3840x2160@144 DP) + Samsung SyncMaster 906BW (1440x900@60 HDMI-DVI) |
Case | Coolermaster HAF 932 w/ USB 3.0 5.25" bay + USB 3.2 (A+C) 3.5" bay |
Audio Device(s) | Realtek ALC1150, Micca OriGen+ |
Power Supply | Enermax Platimax 850w |
Mouse | Nixeus REVEL-X |
Keyboard | Tesoro Excalibur |
Software | Windows 10 Home 64-bit |
Benchmark Scores | Faster than the tortoise; slower than the hare. |
ThicknessAnimation myanimation = new ThicknessAnimation(new Thickness(0), new Thickness(100), TimeSpan.FromMilliseconds(1000));
// Both statements produce run time error!
button2.BeginAnimation(Button.MarginProperty,myanimation);
button2.BeginAnimation(Button.BorderThicknessProperty,myanimation);
Yeap it is a good idea to use try/catch blocks for making robust applications.Use breaks to catch an error before WPF implodes itself.