Hi,
why isn't it possible to export text as an WPF/E XAML Text element. I currently get all my text exported as a path instead. I'm missing something
Michael
WPF/E Export: Text as Path, how to change?
Hot Topic
- Any MSFT website supporting CardSpace at all ?
- parallelism in state machine
- While loop only executes once
- WWF and ASP.NET
- WinWf, SharePoint and OnActivated
- Best practices for integrating WF & WCF?
- WMI and Win32_DeviceChangeEvent
- Capture the frames with directshow
- Flash Professional 8, | VISTA | Bug
- WebserviceInput and Enum in interface definition will not bind to properties
Windows Vista
- Latest DirectShow SDK, overview and samples
- DirectX.AudioVideoPlayback Issues
- previewing Video From Capture Devices on a network
- GetComputerName() issue in C++
- Can Activities defined in XOML file share data?
- How to programmatically create the Invoked event handler on an ExternalEventHandlerActivity
- problem with some activities
- sqlTrackingWorkflowInstance.Status = Forever.Running?
- Question about FileRender
- How to get the system-defined interface in the development of namespace extension?
WPF/E Export: Text as Path, how to change?
Tom_Liu
I'm assuming you're talking about the Expression Designer again. I think the reason you're seeing that is because Expression Design is really for creating graphics, not neccessarily for doing things like what WPF/E is used for. Think of it more like Paint rather than Word.
What we really need is for Blend to support WPF/E. :)
Blkbird
Yes, of course, I would like to see Blend as WPF/E editor, too, and what I know Microsoft will do that. It makes no sense that a subset of XAML (WPF) couldn't be managed with it. But with Blend you are not able to create graphics as you can do it with Expression Designer, or I'm wrong
Michael
alihht
We're currently working on improved tooling for WPF/E and I realize it's painful where we are today. The workflow I usually use is to do the rich graphics in Design then switch to Blend for the WPF/E XAML (including the text). It's painful, but possible to structure your XAML in a way that the WPF/E XAML is WPF compliant, or you can do some design in a WPF project and copy chunks of XAML into your WPF/E project.
Hope this helps and sorry for the painful workflow, we're working on it!