Who is using WPF ?
-
Christian Graus wrote:
It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
Yeah, and I don't see this improving as frameworks get more and more complex yet coding is still constrained by people, budgets, and marketing deadlines. And the reality is, mixing declarative and imperative code is not as trivial as we have been led to believe. I should know, as I've created some rather unwieldy architectures myself and when I look at WPF, I can only shake my head in dismay. Some of the things I see there are definitely things that I've learned to avoid. Well, not avoid, but here's a thought--if separation of concerns is an important thing in the imperative world, it is a critical thing in the declarative world, and looking at WPF, all I see is entanglements upon entanglements. Not a pretty sight.
Christian Graus wrote:
I doubt the lounge can
So, I'm curious--is there an event handler on MinHeight that's firing when you change that property? Marc
No, I don't believe there's an event firing. I've learned to do as much as I can in code, it's just easier to read and easier to control.
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 )
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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:
Application.Current.MainWindow.MinHeight = ActualHeight + 100;
Lines like that has thrown me off by accidentally leaving optimization on. In my case it was ASP.NET, and the real line was about 100 lines off the noted line. Make sure optimization is off. :)
xacc.ide - now with IronScheme support
IronScheme - 1.0 alpha 1 out now -
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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 )
I'm not - but just because the tooling support sucks.
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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 )
How does Trailblazer sound. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
Christian Graus wrote:
It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
Yeah, and I don't see this improving as frameworks get more and more complex yet coding is still constrained by people, budgets, and marketing deadlines. And the reality is, mixing declarative and imperative code is not as trivial as we have been led to believe. I should know, as I've created some rather unwieldy architectures myself and when I look at WPF, I can only shake my head in dismay. Some of the things I see there are definitely things that I've learned to avoid. Well, not avoid, but here's a thought--if separation of concerns is an important thing in the imperative world, it is a critical thing in the declarative world, and looking at WPF, all I see is entanglements upon entanglements. Not a pretty sight.
Christian Graus wrote:
I doubt the lounge can
So, I'm curious--is there an event handler on MinHeight that's firing when you change that property? Marc
Marc Clifton wrote:
if separation of concerns is an important thing in the imperative world, it is a critical thing in the declarative world, and looking at WPF, all I see is entanglements upon entanglements. Not a pretty sight.
I haven't delved into WPF, but for some reason this immediately invoked visions (or nightmares, if you will) of the original / "classic" ASP stuff.
Christopher Duncan Author of The Career Programmer and Unite the Tribes Coming soon: Got a career question? Ask the Attack Chihuahua! www.PracticalUSA.com
-
How does Trailblazer sound. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
Surprisingly similar to Stationary Target. :-D
Christopher Duncan Author of The Career Programmer and Unite the Tribes Coming soon: Got a career question? Ask the Attack Chihuahua! www.PracticalUSA.com
-
No, I don't believe there's an event firing. I've learned to do as much as I can in code, it's just easier to read and easier to control.
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:
No, I don't believe there's an event firing.
Hah! Without spending an entire day examining the assemblies in Reflector, you can't know that. Just because you're not handling the event, doesn't mean the event isn't being routed elsewhere in the framework, it just dead ends because you don't handle it (since almost all events are routed in WPF - the internal routing is probably still set up even if you don't add a handler). I could be wrong, though. Josh Smith might have a better answer. Where's he been, anyway? Ah, huge, obfuscated frameworks... gotta love 'em.
It has become appallingly obvious that our technology has exceeded our humanity. - Albert Einstein
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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 )
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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 )
They are using WPF: Karl Shifflett http://karlshifflett.wordpress.com/ Josh Smith http://joshsmithonwpf.wordpress.com/ Tor Langlo http://www.kodasoftware.com/
Christian Paproth
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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 )
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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, To answer the question, I'm using WPF for a new huge business application. I love it. Challenges, some. But all technologies have challanges, so... I found your question in the new WPF forum and am responding there.
Cheers, KarlMy Blog | Mole's Home Page | How To Create Screen Capture Videos For Your ArticlesJust a grain of sand on the worlds beaches.
-
No, I don't believe there's an event firing. I've learned to do as much as I can in code, it's just easier to read and easier to control.
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 )
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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 )
I cannot consider WPF, as yet another step in .NET obscurity, for my application-development toolset. I got burned by VS2005 when I wrote a Windows-desktop version of a commercial application for Life Compass™ Cards (www.lifecompasscards.com), then tried to beta-test it among my target audience. Nobody had ever heard of .NET nor did they have it installed on their Windows PCs, even XP, so when the application download (not ClickOnce as it takes too much effort, if at all, on a non-corporate audience) took them to the scary Microsoft geek-speak web-page to download 38MB of code, they panicked & cancelled. Come to discover that despite promises of ubiquity starting in 2000, Microsoft did not generally distribute .NET Framework till Vista, so any install to over 80% of the Windows marketplace comes with an additional, huge download. So, I'm looking to rewrite in something open-source. Got any suggestions?
-
I cannot consider WPF, as yet another step in .NET obscurity, for my application-development toolset. I got burned by VS2005 when I wrote a Windows-desktop version of a commercial application for Life Compass™ Cards (www.lifecompasscards.com), then tried to beta-test it among my target audience. Nobody had ever heard of .NET nor did they have it installed on their Windows PCs, even XP, so when the application download (not ClickOnce as it takes too much effort, if at all, on a non-corporate audience) took them to the scary Microsoft geek-speak web-page to download 38MB of code, they panicked & cancelled. Come to discover that despite promises of ubiquity starting in 2000, Microsoft did not generally distribute .NET Framework till Vista, so any install to over 80% of the Windows marketplace comes with an additional, huge download. So, I'm looking to rewrite in something open-source. Got any suggestions?
I've never used .NET and have no plans to do so unless forced to by an employer. Native C++ is the way to go.
-
I spent the past year writing a WPF project, which is now live and in the marketplace. WPF does some cool stuff, but it has it's fair share of issues. The most frustrating thing for me is when we hit a showstopper, and I ask a question ( specifically on the MSDN forums, although I am asking in the CP WPF forums now too ), generally, it takes a couple of weeks for the question to go stale and then someone from MS to answer, so we often get into situations where, for example, WPF can't read a photograph from a jpg and resize it without destroying the image ( I believe this bug is still present in .NET 3.5, we get around it by using GDI+ to load images ). My current bug is interesting. Out of the blue, we get an intermittent error: Not enough quota is available to process this command. I tracked it down to this line of code: Application.Current.MainWindow.MinHeight = ActualHeight + 100; Despite being in a try/catch, this line crashes the program regularly. It's been there from day one, but the problem is new. I've removed the line, perhaps in a few weeks I'll have an idea of how this can crash the program. No, this is not a programming question - if the MSDN WPF forum can't help me, I doubt the lounge can. It's meant to be a trigger for 'what a weird error' or 'gosh it's hard trying to work with new frameworks, because you're the one finding the weird bugs' type discussions.
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 )