WPF is a nightmare
-
Are you still using this old and crufty WPF technology? "The Windows UI Platform team is creating a new Framework that will enable new UI experiences in future versions of Windows." http://www.istartedsomething.com/20080111/new-ui-framework-future-windows/[^] Also according to a developer of Windows 7 WPF goes unmanged: "I'm sure that the WPF stack will be optimized, perf-wise. I'll bet anything (well...my MSFT stock options) that it will be unmanaged in the future. Wait! It is! See Silverlight - light, small, fast. Microsoft ended up writing a WPF stack twice - which is expensive, and pointless - we should have released something much better the first time round, imo."
That has got to be a joke, right? Worse than us frikking web developers with our dynamic frameworks that sprout faster than weeds in horse manure.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
-
That has got to be a joke, right? Worse than us frikking web developers with our dynamic frameworks that sprout faster than weeds in horse manure.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
Paul Watson wrote:
That has got to be a joke, right?
I guess only the future can tell, from internal plans to announcements to what actually ships is a long way. But I have zero hope for WPF in its current form and hope for an unmanaged version of WPF which I can used straight from C++ :) But wait, we almost already have it, Codejock is working on a MFC XAML renderer and it beats the performance of WPF by factor 10 or so on my machine. So I can step into XAML without using this bloated framework from Microsoft :)
-
That has got to be a joke, right? Worse than us frikking web developers with our dynamic frameworks that sprout faster than weeds in horse manure.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
-
Nothing except what I've seen here on CP. It looks good, and fun if you have the time and desire to make you app look shiny.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighistpeterchen wrote:
It looks good, and fun if you have the time and desire to make you app look shiny.
IMHO, the true beauty is that MS is finally moving away from the '80s-style "we have to cram the entire UI into 4K of RAM, screw re-use" model of development. The problem is, they wrote it for XAML, which pretty much requires tools to use effectively, and for which no good tools are available. By the time we get good tools, it'll be obsolete.
-
So, we have shipped our product. It pretty much works great on all machines, bar the Dell we bought to use for demos ( it's a portable PC, but too big to be a notebook, it's a media center ). In our app, we show images and when we zoom, we reload them at the new size ( so we keep the smallest possible image in memory ). On the Dell, it zooms, reloads the image, but does not refresh. Calls to invalidate visual do not work. In fact, the whole app bar the frame stops painting, opens calculator and you can leave a trail. Minimise and maximise and all is good again. But not for all images. And only on the Dell. I tried a number of fixes, such as loading a blank image first, clearing the data dependancy property, etc. Many of these work. Twice. Then never work again. How is that possible ? how is any of this possible ? There are huge bugs in WPF that are known and not fixed, don't they even care ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
If Dell doesn't have updated video drivers for that system, look up the specs on it and download drivers from the chipset vendor. There's a good chance that will fix it. Who knows what Dell had disabled during their certification process, or how many versions back their driver is.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
If I turn the hardware acceleration down so that DX is off, it solves it ( but now the app is all jerky ). I wonder if a new version of DX might help ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
Christian Graus wrote:
If I turn the hardware acceleration down so that DX is off, it solves it ( but now the app is all jerky ). I wonder if a new version of DX might help ?
As far as I know, there's no DirectX 9.0c update at this time, after the latest February 2007 update. Also by default, in WinXP, DirectX 9 acceleration is turned off for some part of WPF. See this: http://msdn2.microsoft.com/en-us/library/ms742196.aspx[^] and also this: http://msdn2.microsoft.com/en-us/library/aa970683.aspx[^] In the first link, it says the 3D anti aliasing of WPF is only supported on Windows Vista. Second link is "Optimizung WPF performance" guide. Running WPF on Windows XP means you can't have 3D anti aliasing explicitly. It will go back to software renderer. As for NVidia, I suggest you need to download driver Forceware version 163.xx or latest version. It's stable for me. Correct me if I'm wrong. Eriawan
-
Christian Graus wrote:
If I turn the hardware acceleration down so that DX is off, it solves it ( but now the app is all jerky ). I wonder if a new version of DX might help ?
As far as I know, there's no DirectX 9.0c update at this time, after the latest February 2007 update. Also by default, in WinXP, DirectX 9 acceleration is turned off for some part of WPF. See this: http://msdn2.microsoft.com/en-us/library/ms742196.aspx[^] and also this: http://msdn2.microsoft.com/en-us/library/aa970683.aspx[^] In the first link, it says the 3D anti aliasing of WPF is only supported on Windows Vista. Second link is "Optimizung WPF performance" guide. Running WPF on Windows XP means you can't have 3D anti aliasing explicitly. It will go back to software renderer. As for NVidia, I suggest you need to download driver Forceware version 163.xx or latest version. It's stable for me. Correct me if I'm wrong. Eriawan
Our card is an ATI card, I have their latest driver, and it doesn't work. Will an NVidia driver fix an ATI card ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
If Dell doesn't have updated video drivers for that system, look up the specs on it and download drivers from the chipset vendor. There's a good chance that will fix it. Who knows what Dell had disabled during their certification process, or how many versions back their driver is.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
Yeah, their driver was over a year old. The new one still doesn't work, tho.
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
Yeah, their driver was over a year old. The new one still doesn't work, tho.
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
That's a shame. Check to see if there is an open slot. Unless you are playing games on it, you could probably get away with a PCI card if you had to. :)
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
Our card is an ATI card, I have their latest driver, and it doesn't work. Will an NVidia driver fix an ATI card ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
Christian Graus wrote:
Our card is an ATI card, I have their latest driver, and it doesn't work.
I'm very sorry. What is the model number of your ATI card? I mean, usually the model numbers usually are: X300, X1300, X600, X2100 or X2500. As far as I know, ATI Radeon below X300 (for example, the Radeon 9800), is considered to be Tier 1 renderer. I've used and tested ATI X600 and X1300 with the latest Catalyst driver, works fine for me, and the graphics index is 3.5 for X600 and 4.1 for X1300 (with 256MB GDDR2). Tier 1 renderer is somehow can be slower on Vista, and this bring sluggish performance on WPF running on Vista, IMHO. I've also tested 9500, the score went bad, only 2.4. best regards, Eriawan