# Thursday, July 01, 2010

When I started blogging 3+ years ago, I found Windows Live Writer and really loved it. Since I’ve started blogging again, I’ve switched from blogging on my PC to my Mac. Mainly because I’m trying to use and understand Mono on the Mac. Unfortunately I’ve been unable to find any decent free blogging software on the Mac.

Switching back and forth to my PC to write blog posts isn’t my idea of fun. So, I decided to fire up my Windows VM, installed WLW, and put VMware into Unity mode. I must say, I’m pretty impressed. I was able to write a blog post in WLW, take a screen capture on my Mac, and paste it into WLW with absolutely no issues. Consider me sold :)

Now, if only I could figure out how to get the link that WLW opens after making a post to open in Chrome on my Mac instead of Chrome on my VM :)

Thursday, July 01, 2010 8:25:00 AM (Alaskan Daylight Time, UTC-08:00)
# Tuesday, June 29, 2010

Does your iPhone 4 go from full bars to no bars when you hold the lower portion? Disable the Bluetooth radio and you should see your recption return to (almost) normal.

Tuesday, June 29, 2010 6:37:00 PM (Alaskan Daylight Time, UTC-08:00)

A while back, I was tasked with solving a defect in our system. The defect was “Changes to an image can be reverted only one time.”

As I started to look into the code, I saw something like this:

  1. private Image _originalImage;
  2. private Image _image;
  3.  
  4. public void Show(Image image) {
  5. _image = image;
  6. _originalImage = (Image) image.Clone();
  7. }
  8.  
  9. private void Revert() {
  10. _image = _originalImage;
  11. }
 

Looking at the code, I suspected I knew what was wrong, but I wanted to confirm it. So I ran the app, made modifications to the image, clicked revert, made modifications to the image again, set a break point and clicked revert again. Once Visual Studio broke, I popped over to the immediate window and typed this:


&_image
Which returned: 0x1234abd0
&_originalImage
Which also returned: 0x1234abd0

Now I knew what the issue was, the original image was getting clobbered due to a missed .Clone() on line 10. A simple _image = (Image)_originalImage.Clone(); fixed the issue.

.NET | C#
Tuesday, June 29, 2010 6:45:00 AM (Alaskan Daylight Time, UTC-08:00)