Essential WPF - All Comments

re: Time to move on after 9 years…

Tomer Shamam — Wed, 01 Feb 2012 12:35:27 GMT

Thanks guys :)

re: Time to move on after 9 years…

Shay Friedman — Wed, 01 Feb 2012 11:56:09 GMT

ברוך הבא ובהצלחה!!!

re: Time to move on after 9 years…

Rotem Bloom — Wed, 01 Feb 2012 08:03:55 GMT

שיהיה המון בהצלחה אתה מצטרף לאחלה של חברה עם אחלה אנשים.

re: Time to move on after 9 years…

Ariel Ben Horesh — Sun, 29 Jan 2012 09:45:20 GMT

Tomer, as I said to you alredy in twitter, It's about time :)

Goodluck!

re: Time to move on after 9 years…

Eran Stiller — Fri, 27 Jan 2012 15:03:10 GMT

שיהיה רק המון בהצלחה!

re: Time to move on after 9 years…

Tomer Shamam — Fri, 27 Jan 2012 08:24:13 GMT

תודה אלון!

אני מסכים איתך בהחלט :)

re: Time to move on after 9 years…

אלון — Thu, 26 Jan 2012 23:28:26 GMT

ברוך הבא!

פעם שלישית שאנחנו עובדים ביחד, בכל פעם זה רק נהיה יותר טוב.

אלון.

re: Know that you're in design time mode

Youngy — Sun, 22 Jan 2012 19:05:54 GMT

Thanks alot - your anwser solved all my problems after several days struggling

re: Exit Windows Phone Application

Tomer Shamam — Sun, 15 Jan 2012 07:01:52 GMT

Thanks Josh, indeed many developers have the same problem. I hope this solves it for good. :)

re: Exit Windows Phone Application

Josh — Sun, 15 Jan 2012 06:21:51 GMT

Ahh, that is brilliant! I can also see how this would be userful in other ways as well, like in login forms. Before, you were supposed to have the app "load", and then pop up the login screen "for the result", and then close it when it finished. That way users could not use the back key to go back to the login screen.

Now if I understand this correctly, I can just do a "no-pain" login screen and then call the script on the next page.

Thanks so much!

re: WPF Performance Sweets – ContentControl.Content = null

Per Lundberg — Wed, 11 Jan 2012 07:30:23 GMT

Very interesting blog post indeed. With huge visual trees, the performance impact of setting ContentControl.Content = null can be HUGE. We are talking about times like 10+ seconds! However, I don't know if the "indirect view" approach will work in our case, but still, your thoughts and explanations make a bit of sense. Will try to find a workaround based on this.

re: Open Window, Dialog or Message Box from a ViewModel – part 2

Leon — Tue, 10 Jan 2012 10:24:39 GMT

Tomer hi,

Great post.

I did love the Dispatcher.BeginInvoke(() => OnOpenChanged(opening), DispatcherPriority.Loaded) in one line you resolve the issue of 'rasing' condition.

However in some cases this could cause the Dispatcher to stack. For example, if there is considerable time till this contol is loaded. Since the priority is Loaded it is placed in the message queue and would be called again and again, those preventing other messages with lower priority being processed.

And if Loaded of this control depends on some other thread with lower priority doing something it would never ever arrive here.

Of cause the other threads priority could be changed, but what if you don't know who the users of your control and how it would be used.

Thank you,

Leon

re: Windows 8 Dilemma – Could it run your Enterprise Applications?

Tomer Shamam — Thu, 29 Dec 2011 10:59:15 GMT

I can agree that it may not be the same application, with all of the great features, but sure it will be far more sophisticated than Office for Windows Phone, if I can call it Office at all.

re: Windows 8 Dilemma – Could it run your Enterprise Applications?

Ted — Wed, 28 Dec 2011 23:13:39 GMT

Metro Office easily can share only its name with the "most complicated software beast". Same as Office for Windows Phone is in no way a real MS Office.

re: Windows Phone Enhanced Application Bar or Bindable AppBar – Part I

Tomer Shamam — Wed, 28 Dec 2011 20:17:20 GMT

Hi Łukasz,

The link you provided doesn't work. Could you please post it again?

Also feel free to send PM.