|
AnilUnni wrote: This can be done using Adobe Illustrator using XAML plugin
That's interesting. I didn't know that Illustrator could do that.
|
|
|
|
|
Pete,
Illustrator has a plug-in to export vector images and scenes to xaml. It works great.
The converting of bitmpat images to vector article is a done by tracing, I have not seen one yet that does a great job on complex photos.
modified 27-Feb-21 21:01pm.
|
|
|
|
|
Karl Shifflett wrote: Illustrator has a plug-in to export vector images and scenes to xaml. It works great.
Nice, although we are using Expression for our artwork (and looking into Zam3D based on Jammer's recommendation).
|
|
|
|
|
There are also utility apps for PSD - XAML converting, I've had limited success using this one here though as it can't handle complex PSD's. There are quite a few things potentially in a PSD that just don't map to any equivilent in XAML or WPF.
I've been working with ZAM3D some more ... I'm even more impressed with it now than when I recommended it!!! I've had a few crashes which is unfortunate but to be expected with a v1 app I guess ...
Jammer
Going where everyone here has gone before! 
My Blog
|
|
|
|
|
Hi All,
Does anyone have any tips on tracking down hard to find problems in XAML?
My application runs without any hitches and everything works as designed.
Blend opens the solution and displays the main window with out any errors or problems building the solution.
But VS2008 wont show the main screen in its XAML designer pane and says that there is an un-handled exception "Object reference not set to an instance of an object." I've seen this error and solved it before but the exception track trace gives no clue as to the source of the exception.
Thanks,
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
Jammer,
1. build often so that things don't creep in.
2. I've seen this too. Blend likes this, VS doesn't. Also in the reverse.
3. To find your problem, open in VS and remove sections one at a time until the offending section is discovered. Then, go look at the constructors for code and controls in the offending section. You really need to watch code in your constructors as if it blows up, you get "REAL" misleading exception messages.
Hope this helps.
modified 27-Feb-21 21:01pm.
|
|
|
|
|
Yeah, i builld really often ... in fact almost constantly as I'm still really feeling my way around .NET in general.
I have a couple of ideas as to what might be doing it ... I need to investigate these. I think your idea of removing sections (do you mean controls and use controls?) will be a good one ...
Do you know of any plans by the WPF team to tighten the grip on XAML exceptions like this? I was chatting to another Developer at work today (a contractor) and he was expressing similar feelings about how difficult it can be to track down XAML problems.
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
Jammer wrote: Do you know of any plans by the WPF team to tighten the grip on XAML exceptions
Have not heard of any specific rumblings, which is why I build often and learn the do's and don'ts. Comes with time, you'll get it all sorted out. 
modified 27-Feb-21 21:01pm.
|
|
|
|
|
For sure ... nothing beats experience.
I have my data loading and saving via my custom dialog now ... all looking very WPF and spanky new sparkly nice ... 
Just trying to find out where the Serialization exceptions live now ...
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
Unfortunately, the issue with the designer pane reporting an unhandled exception is consistent with the behaviour of the old WinForms designer. The problem actually relates to the designer having to "compile and interpret" the item in the designer, and some things just go wrong. I usually find that attempting a clean rebuild is a good idea in order to find issues.
|
|
|
|
|
Hi Pete,
A clean rebuild? Do you mean run a "Clean Solution" and then rebuild/recompile?
Cheers,
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
Jammer wrote:
A clean rebuild? Do you mean run a "Clean Solution" and then rebuild/recompile?
I certainly do.
|
|
|
|
|
Feck ... that didn't help at all. I need to sit down with more time for tackling this one.
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
So I got inspired at work to learn WPF and Xaml. Cool technologies indeed, especially the data template stuff!
Anyway, I've been playing around with the TreeView control. I've successfully bound it to my data structure using the HierarchicalDataTemplate element. Now to my question: how do I propagate changes in my data to the control? Resetting the DataContext property to my data didn't do anything at all (which was expected - same reference being used!).
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
If you bind to an Observeable collection your changes will automatically be displayed.
modified 27-Feb-21 21:01pm.
|
|
|
|
|
Thanks! I will try it as soon as I get home.
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
Is there a rich text editor for silverlight, or will that be a 3rd party control?
|
|
|
|
|
Nope. No rich text editor. There's a marketing opportunity for you right there.
|
|
|
|
|
|
Hi,
I have two buttons on my WPF window when I click one I want to change the visibility of two layers in the screen. Problem is I can't see those layers in the intellisense.
Both the usercontrol navigator and the screen are in the same namespace. How do i 'find' the layer from the user control in order to change its visibility?
Cheers,
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
Jammer,
What do you mean by a layer? WPF does not have a layer control. What is the control type you are trying to hide or make visible? Does that control have a name assigned to it? When you assign a name to a control and rebuild the project, that control will show up in intellisense.
modified 27-Feb-21 21:01pm.
|
|
|
|
|
Hi Karl,
Its that old friend of ours d:IsLayer="True"
Basically In the user control (in the same namespace as the main presentation project not a separate UserControls namespace) I can't seem to 'see' any of the controls that are used in the main screen in order to change their visibility ... really odd.
And these controls have a x:Name="" ... should these be plain Name=""
Cheers,
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
x:Name is fine.
If you are in the code behind of a user control, you will not see the objects in the main window.
This encapsulation and separation of responsibilities is a feature of .NET and object oriented languages.
By having the user control address the controls on the main form you are creating a dependency inversion which "normally" we try to stay away from.
If the design of your application requires this you do have several options.
1. You can get a reference to the main window, then cast it to the type your main window is, then you can reference the controls on the main window.
2. You can have the user control raise an event that the the main window services and then allow the main window to set its controls.
3. You can expose properites on the user control that the main window can bind to, that controls their visibility.
4. You can pass a reference to the controls that the user control will effect in and then the user control can control them.
I'm sure there are other ways to accomplish this.
modified 27-Feb-21 21:01pm.
|
|
|
|
|
Thanks for this Karl. Loads more learning to do now! Not sure I even know how to cast something at the moment.
I'm still at the stage where I expect to be able do things that are simply daft, you shouldn't do or can't do at all.
hmm ...
Jammer
Going where everyone here has gone before!
My Blog
|
|
|
|
|
What language to you use? C# or VB.NET?
modified 27-Feb-21 21:01pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
