Day 2 - It's all over
Actually, I'm way too tired to blog about the awesomeness of today, but figured I'd at least put up a quick message to say it was an amazing experience. I worked with some great, smart people, learned a lot, and got to meet some of my favorite writers.
Tomorrow, a fuller recap, including tales of the special guest stars!
7 comments:
Congratulations. Looking forward to reading about the experience.
cheers
Dave
PS were you surrounded by Macs? :)
Oh yes. There were many Macs. However, it helped me decide that I won't be getting a Powerbook when I get a new laptop next year.
I spent some time in Final Draft on a teammate's computer and found it even worse than my desktop Mac. I can't believe how badly the touchpad works. It's almost impossible to select arbitrary large blocks of text, because clicking and holding the button selects a single word so quickly. Plus, I'm used to having my touchpad detect taps and double taps on it so I don't always have to travel all the way to the button(s). I gather that I could get some software to change the behavior. but that should be an out-of-the-box configuration option, I think. Oh well.
You can't double tap as standard on the touchpad? hmmmm as much as I dislike the touchpad unless it is less than 5 mins work, I agree double tapping should be standard. My personal lappie(LG - must admit, have been very impressed with mine for the price)even has a special scroll section built into the touchpad.
Still insanely jealous of your experience and looking forward to it once you have rested and flushed those studio notes.
cheers
Dave
Hey, Guys....
I'm sitting here with my world-class techno geek expert friend.
Here's what he says:
"On most modern Mac laptops, you can set the touch pad to enable both left- and right-clicking as well as dragging from the 'Keyboard & Mouse' pane in System Preferences.
"When the option is enabled, a one-finger tap on the track pad is a left-click, and a two-finger tap is right-click."
He adds, with what I consider to be unwarranted sarcasm, "Although this is not the default, it takes 3 seconds to enable this option."
So how about if we limit our Mac-bashing to the iPhone's proclivity to attracting spam?
Alright, that seems fair. It was awfully late, and it was Jesse's laptop so I didn't want to mess with his configuration.
I won't bash for this reason...but let's not forget about the iPhone's apparent ability to crash Duke University's wireless network. :)
Evening, Mr. Porter. I'm Dan's tech-geek friend.
I am compelled to point out that according to Duke University, the alleged iPhone dustup was in fact not caused by the iPhone.
Here's the relevant text from Duke's chief information officer (emphasis mine):
"Cisco worked closely with Duke and Apple to identify the source of this problem, which was caused by a Cisco-based network issue. Cisco has provided a fix that has been applied to Duke's network and there have been no recurrences of the problem since. We are working diligently to fully characterize the issue and will have additional information as soon as possible. Earlier reports that this was a problem with the iPhone in particular have proved to be inaccurate."
You can read the entire statement here:
http://www.dukenews.duke.edu/2007/07/cisco_apple.html
Post a Comment