Previous Page Page 2 of 2 in the Windows8 category
# Sunday, 18 November 2012

Here are some tips for using Window 8 with a touchscreen that you might not know about.

Moving Tiles On The Start Screen

It's easy to move tiles around using the mouse, just click and drag the icons from where they are on the start screen. But when you try to do it using a touch screen, you might find it a bit harder, sometimes you end up scrolling the screen instead of dragging the tile.


What's happening is because if you try to drag a tile directly off it's spot as indicated by the RED arrows, Windows will interpret that as an intent to scroll the screen and you end up scrolling instead of moving the tile. If you want to move the tile via touch, what you need to do is to drag the tile DOWNWARDS first as indicated by the BLUE arrow, once you draw a tile down far enough it'll tear off it's spot in the screen and you can start moving it.

Showing The Keyboard Whenever You Want

The touch keyboard automatically shows up when there's a need for it, do not fret if you need to access the keyboard when there doesn't seem to be anyway for you to do so. Just bring up the Charms Bar, hit Settings then in the lower right corner you'll see a Keyboard icon.


Hitting the Keyboard icon, brings up the input selection list and at the bottom of the list is the option Touch keyboard and handwriting panel tapping on this option will immediately bring up the touch keyboard.

Getting access to other keys on the keyboard

The default touch keyboard is a nice finger friendly keyboard consisting of the most commonly used keys.


This is enough for most of your typing duties, but for legacy desktop apps this might not be sufficient, for example you don't have access to the ALT key and also the function keys.

You can enable a fuller keyboard by bringing up the Charms Bar -> Settings -> Change PC Settings (it's at the bottom) Then in the PC settings screen, hit General on the left, then scroll down to the Touch Keyboard section on the right and find the setting Make The Standard Keyboard Available and turn it on.


Once you turned that setting on you'll now find a new keyboard icon in the change keyboard type button on the touch keyboard (it's the little keyboard icon beside the right arrow key)


This will bring up the fuller more cramped touch keyboard.


You can toggle between numbers and function keys by hitting the Fn button in the lower left. One thing to note is that if you encounter any instance where the program doesn't seem to respond to the default keyboard, you might want to try it with the fuller keyboard.

Accessing The Even FULLER Keyboard

You'll notice that on the standard touch keyboard, some keys are still missing. Such as the Print Screen key, you still have one more option, bring up the Start Screen and type On Screen Keyboard.


This will bring up the legacy on screen keyboard meant for accessibility use.


This should solve all your legacy keyboard needs.

Sunday, 18 November 2012 13:30:45 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Saturday, 08 September 2012

Today's post starts off with an interactive exercise, first download the sample project file and run the program in there. The program looks like this.


When you've run the program, perform a simple exercise, move your mouse in and out of the extra large buttons and note what happens.

The buttons are essentially a ViewBox control containing the XAML which makes up the buttons. The viewbox is then contained inside a grid and scaled to the grid's size.

Code is tied to the PointerEntered and PointerExited events of the Viewbox which basically just changes the background color of the Grid which contains it. If you haven't already run the program and then move the mouse in and out of all of the buttons, do so now.

After running the program and trying out what I mentioned you should have noticed the following problem, given that a button looks like this.


  • Button 1 didn't seem to respond to mouse events in the green area
  • Buttons 2 and 3 did.

So what's happening and why the difference in behavior? Let's take a look at Button 1's XAML construction. (Behold my l33t diagraming skills!)


Note that it is made up of two vector paths (the Stroke and the [Path])

Now let's take a look at Button 2's XAML construction.


Compared to Button 1, there's an extra Ellipse element (the green circle) called hitAssist which is sitting behind the blue circle and 'i' which makes up the button.

By now you should have figured out why Button 1's mouse events where behaving so weirdly, for Button 1 the only elements which have a physical appearance are the circle and the 'i' and that's exactly what triggers the mouse events.

Whereas Button 2 has an additional hitAssist element which fills up the empty gap between the circle and the 'i' and hence the mouse events are triggered as if they're one consecutive element.

"But what about the Grids that are containing the strokes? Wouldn't THEY trigger the mouse entry and exit events?" But they don't! In XAML you'll use a LOT of Grids, Panels and Canvas to layout your elements, you do NOT want every single container to simple fire mouse events!

So how DOES an element qualify for mouse interactivity? Well, I gave a hint just now already. It must have a PHYSICAL appearance. In more easy to understand terms... Make sure the element has a Background Brush assigned to it. The moment a background brush is assigned to an element it will start participating in mouse events because the mouse is able to know if it's running over an element's background brush or not.

So now we know that what we want to do is to fill up gaps in our interactive elements so it makes more sense when users are using them. "But I don't want my sleek outline buttons to have an ugly unadaptable background color!" you say. Well, that's why there's a Button 3 in the sample.


Construction wise it looks just like Button 2, except the Ellipse element that's covering the gap is called hitAssistClear and it's can't be seen. "But didn't you just say that only elements which have a physical appearance can have mouse events?" Because it IS still physically there, it just has an Opacity property value of 0%. It's like a really really really clear piece of glass, you can't see it but it's there! Just remember:-

Any element that has a Visibility property value of Visible will participate in mouse events even if Opacity is 0%. Setting Visibility to Collapsed will remove it from mouse events too. And just in case you didn't realize, there's a property on every element called IsHitTestVisible setting that to FALSE will remove it from mouse events too.

And that is what the name of this whole notion of seeing wheter the mouse is over an element or not : Hit Testing

It's something that I feel all XAML developers and designers should know about, yet I don't really see anyone talking about it much. If you think this is not important, what if the button was only this small?


Notice the hit area of 'i' is now merely a few pixels, do you want your users to have to pixel hunt in order to click a button? Would YOU like to pixel hunt in order to click a button? This experience gets WORSE if your user is using touch to navigate your app!

ps. The button icon you see was created using the TOTALLY EXCELLENT Metro Studio by SyncFusion. Hmm... I should submit a feature request where they insert a hit test element into their XAML output.

Saturday, 08 September 2012 23:11:41 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Tuesday, 28 August 2012

At some point when you're developing a Windows 8 App you probably realized that if the app is run on a tablet form factor device you'd want to freeze the app orientation in either landscape or portrait display modes like you'd do in a Windows Phone app. So what you do in Visual Studio 2012 is that you double click on the Package.appxmanifest file so you can start tweaking the manifest settings for your app, in particular is the Supported rotations section.


Since you want your app to only support landscape mode, you check both landscape modes. Then you decide to test if this works, so you fire up the simulator, and rotate it, but instead of being locked in landscape, your app still rotates to potrait mode.


This doesn't work because the simulator doesn't accurately simulate the hardware rotation, as mentioned in the documentation (look under the change device orientation section)

Since that doesn't work, you try to manually rotate your screen using Windows Mobility Center (Windows + X, then select Windows Mobility Center)


And STILL your app doesn't stick to landscape orientation!

So what exactly is wrong?

The problem here is that the rotation preference setting of the app is only enforced on a Windows 8 system with a supported HARDWARE ACCELEROMETER.

Which means unless Windows knows how the system is orientated through the means of a supported sensor, it'll never attempt to switch to the app's preferred orientation.

So you shouldn't need to worry that your preferred orientation setting isn't working, it'll work on any hardware that is properly designed for Windows 8. How do you deal with people who manually rotate their screens using Windows Mobility Center then? Well... did you know you could rotate your screen using Windows Mobility Center? Did you even know that there was a Windows Mobility Center? It should be safe to assume that if someone knew enough to manually rotate their screen display, they'll know enough that not all apps run fine in both portrait and landscape orientations. Winking smile

Tuesday, 28 August 2012 22:02:29 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Sunday, 26 August 2012

So I've recently obtained the RTM version of Windows 8 through my MSDN subscription. And therefore I have a few updates to add to my previous Windows To Go post.

The first and most important finding which was discovered by a friend was that the San Disk Cruzer Fit 32GB is actually capable of running Windows 8 at usable speeds.


Performance wise, it's still not going to be as good as a hard disk, but the fact that it's

  • Bloody small so it doesn't get in your way like a hard disk would.
  • Bloody cheap (RM67!)

Makes it a very tempting proposition! So what kind of performance are we talking about? Well... overall reading performance will feel slow, but not unbearably slow during normal usage. And you might encounter some instances where it seems like the system stalls for while when there's heavy traffic going through the USB bus. Also, disk intensive scenarios like when you try to install programs might be a bit slower than usual.

One thing to note is that actual performance still depends a lot on your PC's USB Bus, if that becomes a performance bottleneck you still will get unbearable speeds from the drive.

Speaking of installing programs, another interesting scenario popped up once my friend made his Windows To Go drive. If you installed Windows 8 directly onto the USB drive, it's possible that the OS would regard it as a removable drive, this would cause many programs to refuse to install onto the OS drive. Which is not what you'd want.

Luckily, there is a solution for this. All you need to do is to install Windows 8 onto a VHD that's on the USB drive and boot into it. There are again various guides to do this on the net so just search around for it. I might get around to doing one if people actually ask for it.

Till the next update then!

Sunday, 26 August 2012 15:11:15 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Saturday, 25 August 2012

So you’ve just finished installing Windows 8, and you’re staring at the spanking new Start screen.


After staring at this for a few seconds you might already have a few questions on your mind. Let me try and answer them for you.

Where’s the Start Button?

The Start button is in the same place where it was in previous versions of Windows, just that it’s hidden to not take up an extra icon of space. Space saving is not exactly a good argument but in any case, to access the Start button, just move your mouse pointer into the LOWER LEFT CORNER of the screen and the Start button will appear.


The basic idea is to hide your mouse pointer in the lower left corner of the screen to get it. You’ll probably fumble around once or twice but it’s easy enough to get used to it, since it is pretty much in the same place where it was in previous Windows.

Note: Don’t try this when you’re actually IN the Start Screen (The screen you see when you first launch windows, ie. The one on top) When you’re in the Start Screen, the lower left corner brings you to the last app that was opened before your arrived at the Start Screen.

Keyboard Tip : Typing when you're in the Start Screen works just like typing in the Start Menu of Windows 7, it'll immediately start searching for whatever you typed.

What’s this Charms Bar thingy I keep hearing about?

When you hide the mouse pointer in the upper right or lower right corner of the screen, a column of icons will appear.


Then when you reach for them, the icons will gain a proper background and look like a toolbar.


This is what is known as the Charms Bar, it provides quick access to Windows and App features. Start is self explanatory and is basically the Start Button. Devices brings up a list of devices which you can interact with, you can control your projector output settings from this.

Search, Share and Settings have a very interesting and not so obvious behavior that new users wouldn’t understand at first. They are app-specific. For example, if you’re using a calendar application and you’re looking for a button in the app that will open up a setting’s page for you to set reminder options, you don’t have to go digging around just hit the Settings button on the charms bar and you’ll be able to access the application’s settings page. If you’re using a mail application and you want to search for something, hitting the Search button on the charms bar will bring you to the app’s search interface.

One caveat though, as always all these integrated buttons will work like they’re supposed to if the app developer was paying attention and doing their jobs properly.

KEYBOARD TIP: The keyboard shortcut for the Charms Bar is Windows + C

How Do I Turn Off My System?

A very good question considering that the option is now quite hidden compared to previous versions of Windows. Bring up the Charms Bar and click on Settings. Look at the bottom part of the panel.


Apart from the Power Button which we're looking for (FYI clicking on it brings up the options to Sleep, Restart, Shutdown and doesn't immediately turn your system off) There're a few other useful controls that are easily accessible.

Keyboard Tip : Press the physical power button on your PC to turn it off. Smile with tongue out Ok... I suppose some machines are configured to sleep when the power button is pressed.

Where Did The Internet Explorer Address Bar Go?

When you first open Internet Explorer from the Start screen you'll see the address bar at the lower part of the screen.


But after you start surfing for a while the address bar disappears, and you can't seem to get the address bar back by moving the mouse to the bottom of the screen.

To reveal the address bar in Internet Explorer, or the application bar for any other Windows 8 UI app. Right Click on any BLANK space in the application.

Keyboard Tip : You can press Windows + Z to bring up the application bar in Internet Explorer as well as any other Windows 8 UI app. You can also use the familiar Alt-D shortcut as well.

How Come I Can't Run A Program I Just Downloaded!

So you've just downloaded a program and you double click to run it just like you'd do in any other Windows, but a dialog box appears with the message "Windows SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk."


Unlike the previous dialog boxes that block direct execution of downloaded programs, there's no "Yes just run the darn thing already" button that's clearly visible in the dialog. But rest assured, this is not Microsoft preventing you from running anything you want. It's just another well meaning but probably futile effort at stopping people from simply running things which they don't intend to.

In any case, clicking on the More info link in the dialog will present you with the Run Anyway button to run your program.


And that's it for now, future updates as and when I think there's something to add to this.

November 18th 2012 : If you're using Windows 8 on a touch enabled PC you might want to follow up with this post.

Saturday, 25 August 2012 21:18:29 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Saturday, 04 August 2012

So there I was writing my first application for Windows 8, I had to call a web service sitting on a server which had to be connected through HTTPS, but because it wasn't a production server the certificate was self signed and thus is considered to be an invalid cert. No biggie I thought, with all my years of .Net experience I knew that all I had to do was fiddle with the System.Net.ServicePointManager.ServerCertificateValidationCallback method, as mentioned here.

Imagine my surprise when I realized that the class doesn't exists when you're writing a .Net app for the Windows Runtime!

Trying to look for other solutions also came up empty, it was then which I realized that what I needed to do was to allow the application to get a certificate which ISN'T invalid. What I needed was a web proxy which could give the impression that the remote certificate was actually valid.

What I needed... was Fiddler!

So first download Fiddler4 (Because Windows 8 comes with .Net 4.0) from the download page.

After installation and running the program enter Fiddler Options by selecting Tools->Fiddler Options from the menu bar.


After which head into the HTTPS tab and check Decrypt HTTPS Traffic


You'll be warned that you're about to install a wild card certificate on your system. Shown below is one of the many warning screens, you'll have to answer YES to ALL of them.


After the certificate is installed, look back at the options window and check Ignore Certificate Errors. This will make Fiddler not complain about any invalid certs.


Fiddler is a web proxy, which basically means it sits between your machine and the internet so you can monitor the web traffic your PC is making as long as the program is setup to use the system proxy. If you don't know what this implies then just keep Fiddler on only when you're doing development, and turn it off once you're done.

For more information about using Fiddler to assist in Windows 8 development out this post.

Saturday, 04 August 2012 15:51:14 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Thursday, 02 August 2012

One of the most talked about yet not so consumer oriented feature of Windows 8 is Windows To Go which is the ability to run Windows 8 from a USB drive instead of installing it onto a fixed hard drive. And of course everyone wanted to cool looking thumbdrive!

There are no shortage of instructions on how to make a Windows To Go drive. Here's 2 of them

  • Link 1 (Requires downloading of the Windows Automated Installation Kit)
  • Link 2 (Requires an already running Windows 8 installation)

So of course I decided to try and make one myself then! Here's what I found out after tons of sweat and disappointment.

Your USB thumbdrive probably ain't gonna work!

I have a wide range of USB drives ranging from so called super fast speeds, to petit drives that hides itself from the user.


They all failed miserably at running Windows 8! How do you know if your thumbdrive can't run Windows 8?

First of all, when you try to image it following the instructions on the links above it'll take a LOOOOOOOOONG time to image. Basically if the imaging process takes longer than 60 mins (don't read the estimated time from the imaging program) Your thumbdrive is probably not going to work too well. If you actually decide to press on after the installation and actually boot into Windows 8, the first boot is gonna take more than 30 mins to finish the initial setup. If that STILL doesn't deter you from attempting to use Window 8 on your thumbdrive and you actually make it into Windows 8, disk access would be so slow that the user experience is totally unbearable at all!

A Hard Disk Works Best!


The one thing that worked the few times I tried it? A simple USB hard drive. I suppose that since it's on USB, disk access would be slower than on a normal SATA channel, but performance generally feels... normal when I was using a hard drive as the source.

USB 3.0 Might Not Make A Difference

What about USB3.0? That question might have crossed your mind when you were reading the paragraph above. That was what I thought so too! Until I found out that my motherboard's USB 3.0 ports CANNOT be used as a boot drive, I *think* it's because they're basically sitting on a different channel or something like that. While it didn't work for me I suppose there's probably some motherboards out there which CAN boot from their USB 3.0 ports.

In conclusion, does that mean that as long as we use an external HDD we can run Windows To Go probably then? Well...

This probably isn't how to install Windows To Go in the release version of Windows 8

If you go back to the Microsoft page about Windows To Go which I linked at the start, it mentions that a Windows To Go system

  • Disables sleep and hibernate
  • Disabled internal hard drives of the computer it is booting on
  • etc. etc.

This does NOT happen with the install method I link to above, also during my various attempts in getting Windows To Go to work. There was ONE instance which after I booted into Window, a message actually popped up informing me that I was using Windows To Go mode. This has NEVER happened again.

So be warned that all the instructions online probably aren't creating a Windows To Go drive the way Microsoft is talking about.

If you STILL want to proceed...

While it's great that a simple USB hard drive would work, you might want something small and more compact to move around with compared to a hard disk. If that's the case you might want to try and look for the Pen Drive USB 3.0 External SSD


It's a small, thin solid state drive which seems to be capable of running Windows 8 properly.

26th August 2012 : Update #1

Thursday, 02 August 2012 00:00:03 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Monday, 02 July 2012

When Microsoft announced the Microsoft Surface tablet a few weeks ago, although I was surprised that Microsoft had the brass to make their own hardware I pretty much understood it had to be done. As I mentioned in the previous post, I'm no stranger with small, fully functional PCs so it doesn't surprise me to see one. And most people seem to forget.

This isn't Microsoft's first time trying to make a point for small fully functional PCs.

That honor belongs to the long forgotten Project Origami or rather.. the Ultra Mobile PC (UMPC) form factor. But of course, then Microsoft didn't make any actual hardware, then as per usual Microsoft advised the OEM partners on what would make a great UMPC and hoped they could do a great job. When the product (or should I call it... the project?) launched, the complaints were basically circling around the expensive price, comparatively lower performance than notebooks of the same price, and battery life that was not useful for the mobile lifestyle companion it was supposed to act as. Oh.. and of course the usual Windows XP wasn't meant for touch comments. (Which was more justified then cause Windows XP really didn't have much touch optimization compared to Windows Vista which came later)

Edit 19th August 2012 : Hey look, I found out I posted about Project Origami... way... waaaaaayyy back!

A comment which I remember reading from Microsoft was that even though those things were a factor back then, given a few years they would not be too much of a concern anymore. And I guess a few years is now. Let's see what do we have now? Given around the same price of a UMPC back then, we can now have an Intel Core i5 that is no slouch in performance, a potential of 5 hours of realistic battery life (My older generation i5 could do 4 hours, I doubt the new ones are gonna be any worse) and a touch screen + pen digitizer combo. And of course, what else has happened?

Windows 8 happened.

If you look back to a post I made when the Apple iPad launched. (And I DID tell you guys to save the post!) I mentioned that Windows 7 Touch Will NEVER Be Better Than The Apple iPad! And that Windows purpose is "to provide a platform for developers to create apps that are designed for touch interaction, and more importantly to allow users to use as many of their applications as possible even though the apps are NOT MEANT FOR TOUCH OPERATION." If you look at the duality of the existence of the Metro interface as well as the traditional desktop in Windows 8, the statement is pretty much ringing true right now. Of course funny thing is now that the Metro UI is taking the center stage right now, instead of users bemoaning that Windows can't be used properly with touch controls (If you have a touch capable Windows tablet and you think that, please refer to this link), now they're complaining that Windows can't be used properly WITHOUT touch controls! The irony! (And something I hope to help with when Windows 8 RTMs)

So finally at this point in time, we're able to get a highly capable PC in a lightweight, portable form factor and with an operating system that can run effectively through a touch interface. And that's essentially what the Microsoft Surface Pro (I'm not talking about the ARM version here) and the many other ultrabook spec'ed Windows Tablet which are coming out are going to deliver...


As I mentioned before when the Apple iPad launched, it is not meant for me. And the main reason being that anything I need to make a decision into whether to take it with me or not better be worth it. Whatever I would want to do on an iPad, I could do on my phone so how could I justify carrying something around in a bag when the thing in my pocket works just as well? For those of you who are silently thinking "I don't need a bag to carry my iPad, it's light and thin, I just hold it like a small brochure in my hands or tuck in under my shoulder, no biggy." My response to that? Have multiple children, then get back to me on how well having one less free hand works out!

There are those who say that with Microsoft Surface, Microsoft is just trying to stuff a PC into a tablet form factor. To those people I'd have to say that with the Surface Pro at least, there isn't a differentiation. A Windows Tablet is basically a Windows PC, whatever you can do on a Windows PC, you can do it on a Windows Tablet, because.. it IS a PC.

  • Download ANYTHING via ANY protocol? Yep.
  • Watch any video, using any number of weird codecs and formats? Yep.
  • Run the favorite browser of your choice to access browser dependant features? Yep.
  • Use REAL Adobe Photoshop? Why not?

If you're a Windows user, and you're thinking about getting a more portable system you really should wait for Windows 8 hardware to drop and check out all the Windows Tablet devices that are bound to show up.

But of course If you regularly take cross continental flights and need something to keep the days you're up in the air. By all means, get an iPad and load up with batteries.

One final note that I have to point out about how well designed the Microsoft Surface Pro is. It was enough for my non gadget head wife to order me to get one when possible. To me, that's simply amazing!

Monday, 02 July 2012 01:43:06 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
# Tuesday, 19 June 2012

Today Microsoft announced that they were going to make their own Windows 8 devices as well. And it's going to be called the Microsoft Surface.


Personally, ever since Windows 8's features were announced, and seeing the OEM's really gung ho about making Windows Tablets again in Computex 2012, I was already expecting to be able to buy an Ultrabook spec'ed Windows Tablet in the future. What I didn't expect was that it might turn out to be a Microsoft branded Windows Tablet.

Specs wise it brings nothing new to the table for me, as I've been using small and lite Tablet PCs for a while now so seeing the latest greatest notebooks at petit sizes don't really excite me anymore. I'm more surprised that Microsoft themselves are doing it. Some people have likened this to Google giving an OEM early access to their Android builds and coming out with a Google Nexus phone as a lead phone for an Android version. But that's Google telling an OEM "Here are the plans to the next great thing, we're giving you an advantage to build the next great phone first but you must follow the plans to the letter." That would be akin to Microsoft ordering Samsung to make the Windows 8 Developer Preview Slate PC.

But this is not the case here, this is Microsoft partnering with an ODM and making their own hardware. This is basically Microsoft telling the OEMs "We've always been advising you guys on the great ways you can make a Windows Tablet, now we're showing you how to make a great Windows Tablet!" And that's what excites and worries me at the same time. It's exciting because the OEMs HAVE been dropping the ball when it comes to making great Windows Tablets, everyone has just basically been trying to beat the ARM tablets by trying to make a Intel slate and install Windows on it and you end up with lemons like the Fujitsu Q550 and Dell Slate ST. Of course there are also the great ones like the Asus eeeSlate and aside from the Q550 misstep (which I guess can be attributed to Intel's fault) Fujitsu is pretty much the ONLY OEM that's been constantly pushing out Windows Tablets.

What is worrying to me is that Microsoft can't give this Surface endeavor the 110% of the effort they want to. They can't really market and priced the Surface and give it a better advantage compared to the other devices the OEMs are going to come out with, that'd just be inviting the usual anti competition problems. Of course MS could also encourage OEMs to build the same type of device with similar capabilities by offering them the same discount for licenses.

As for the big question of will I be getting one myself? Well, first of all I'm definitely going for an x86 Windows Tablet PC, there's no doubt about that part. The only remaining question which I have for the Surface tablet is the pen. (pic from Engadget)


Being a seasoned Windows Tablet user, all he funky terms like high DPI ink, palm block ability, etc. etc. Basically translates to pressure sensitive digitizer pen, and since Microsoft seem to be only putting the best stuff into the Surface, I'm gonna bet that we're looking at Wacom technology here.

The problem here is that the pen is mentioned as an OPTIONAL input device. That would mean that there might the Surface itself does not have a storage silo for the pen. I HATE the idea of a digitizer capable device not having a slot that can protect and store it's own pen properly. So this is one of the issues that's holding me back on going all "Microsoft, take my money nooooowwww!" on it.

Update : They expect people to latch the pen to the charge port via a magnetic connector. That is NOT a proper and even effective way to store something you don't want to lose!

The other issue is that, this is a PC we're talking about. And I'm pretty sure right now our local Microsoft subsidiary isn't setup to handle support issues for a PC, and like some have already pointed out that Microsoft doesn't have the proper distribution power to perform a global launch. So it's very likely that there's little chance the Microsoft Surface is going to show up on Malaysian soil unless some miracle happens.

So... don't disappoint me Fujitsu... show me what that New Detachable Performance Slate is! And it better have a stylus silo!

Tuesday, 19 June 2012 13:33:41 (Malay Peninsula Standard Time, UTC+08:00)  #    Comments [0]  | 
Previous Page Page 2 of 2 in the Windows8 category