Clark Sell's Blog - Latest Comments

Re: 31 Days of Windows 8 | Day #21: Camera Capture

csell5 — Tue, 30 Apr 2013 12:11:52 -0000

It's not something you have to even mess with as it's handled by the Camera Capture UI already. If you run the sample on a machine that has two cameras, when the Camera Capture UI is presented you will have an option at the bottom of the window to switch cameras. The user can freely switch between the two.

Re: 31 Days of Windows 8 | Day #21: Camera Capture

Apoorva — Tue, 30 Apr 2013 10:02:31 -0000

Please help me out, how to access back camera like web cam or front camera of Surface Device.

In short, How to use back camera in above example and take photo or video.

Re: Setting up npm for node.js on Windows

Deepak Shakya — Fri, 19 Apr 2013 02:44:57 -0000

Thanks. I got it up and running

Re: 31 Days of Windows 8 | Day #21: Camera Capture

csell5 — Thu, 21 Feb 2013 15:16:40 -0000

Yes you can get access to the camera on Windows Phone but at this point it’s still a bit different. Jeff<http: www.jeffblankenburg.com=""> actually wrote a 31 Days of Mango which walks through doing development with Windows Phone 7.5 but I can’t image it’s that much different in 8. You can see more here: http://www.jeffblankenburg.com...
Clark</http:>

Re: 31 Days of Windows 8 | Day #21: Camera Capture

Richard Hartzenberg — Tue, 19 Feb 2013 05:25:31 -0000

Very nice article,

Can similar access to the camera be achieved on windows phone 8?

Re: 31 Days of Windows 8 | Day #5: Settings Contract

catherinalucy — Fri, 15 Feb 2013 02:15:48 -0000

Oh dat's a good idea explained in java script code.

http://www.samplecontracts.org...

Re: Where do you shop online?

Jromer — Mon, 04 Feb 2013 16:45:32 -0000

Equipment Failures
I have had repeated failure with the equipment used in the Well Guru's design, more specifically the Water Way In-line Chlorinator (515-1210) and the Water Way Check Valve (600-7010). The lids on both of these products broke at the manufactured seams multiple times, having nothing to do with regular maintenance as the owner suggested. I got in contact with the manufacture Water Way Plastics and was told the products you used on my system are designed and tested for pool and spa's use only. Furthermore, they recommend that I have a professional remove the system since the products were not tested for use on wells or county or city water services. While they stated they have no controls over how any product of theirs is used, they did confirm lack of maintenance or lack of using salt in my system would not have caused the lids on the Chlorinator or Check Valve to crack. As to the O ring being dry or needing to be inspected and or replaced, as the Well Guru claimed to have caused the failure, Water Way stated that would not have caused the lids to crack either. The Well Guru refused to consider the problem may be the design and blamed everything on maintenance. The problem with the lids cracking started soon after installation but he did not come out to see why the failures were occurring. He has slandered me and sent me an email telling me "Refund Request. No contract / no service - abuse and your shutoff" and called me a JERK. Funny, I thought I was a customer? I have removed the water purification system designed and installed at my residence by the Well Guru. I requested a full refund and in return told them they could come and get the equipment they installed. I now have a new system which is working great, water is clear not Gray (even using salt), no chlorinator which means I no longer require Chlorine which I found out is not recommended to be used in water being consumed by humans since chlorine has been linked to causing Cancer. I would not recommend their system!

Re: 31 Days of Windows 8 | Day #2: Orientation & Snap

csell5 — Fri, 14 Dec 2012 10:11:02 -0000

I only got to play a bit last night but I think I figured it out.

Ironically I can't duplicate it on my build tablet to save my life but my wife's surface I can, but can't determine why it will run sometimes and not other times. Maybe because I was refreshing the app on that page. I am wondering if the page's life cycle and dumping the eventhandler but I have never seen that before and it doesn't really make any sense.

That lead me to think of a race condition. It seemed like, when I put a break point on that registration and refreshed things worked. So what was racing?

The other sensors actually have a reporting interval you set, where as this sensor doesn't seem to so it should always fire, regardless. Yet we didn't see that.

Well crap code on my part, or so it looks to be. If I define the event handler function first, it runs fine. The watch window still shows null which I don't understand. I would have expected it to show a function.

Now if I set it like this:
sensor.onorientationchanged = sensorOrientationChanged;

rather than the typical event registration, you in fact do see the function pointer in the watch window.

Regardless the function should have been defined first. Why the break point caused it to load, I am really not sure.

I have updated git but I want to play around some more and see if still hold true. Curious to see what you see as well.

Re: 31 Days of Windows 8 | Day #2: Orientation & Snap

Joe Paris — Thu, 13 Dec 2012 20:58:54 -0000

No, the handler does not get called with or without a breakpoint. I put a console.log in the handler and it's not outputting anything. I put another one here:

if(sensor) {
sensor.addEventListener("orientationchanged", sensorOrientationChanged, false);
results.innerText = "Sensor Found";
console.log("wiring sensor");
}

and it gets called every time. I navigate to the page (right after I see the HTML1300 msg in the console). I'm seeing the same behavior both with my solution and with yours that I pulled down from GitHub.

When I refresh the app I see the HTML1300 and the "wiring sensor" output but nothing else.

Re: 31 Days of Windows 8 | Day #2: Orientation & Snap

csell5 — Thu, 13 Dec 2012 19:38:07 -0000

Does the handler get called when you rotate it?

I just tried it on my surface and do see a problem. It seems if I put a break point in where the sensor gets set it will always run but if not, then not. You can refresh by hitting ctrl + shift + r while your playing around.

Not sure why that is not always running though. I need to look more into that.

Re: 31 Days of Windows 8 | Day #2: Orientation & Snap

Joe Paris — Thu, 13 Dec 2012 19:25:28 -0000

No, no error message. The text simply doesn't get updated when I rotate the machine it's running on. I've tried it on both a Surface RT and a Lenovo Yoga. Then I grabbed your code from GH and got the exact same behavior. The SimpleOrientationSenor demo code from MSDN runs fine on both.

sensor gets new'ed up, I can inspect it in the locals window, has an onorientationchanged property which remains null after executing sensor.addEventListener("orientationchanged", sensorOrientationChanged);

This is weird.

Re: 31 Days of Windows 8 | Day #2: Orientation & Snap

csell5 — Thu, 13 Dec 2012 18:13:26 -0000

Well, hum. I just ran mine here on two difference machines and it was working fine. is the sensor object actually getting created? var sensor = Windows.Devices.Sensors.SimpleOrientationSensor.getDefault(); If sensor is undefined or null then it can't set an event handler for sure.

If you are, then make sure your binding to the right event "orientationchanged" all lowercase. Then when you rotate your function should fire just fine.

When you says fails, do you have an error message?

Re: 31 Days of Windows 8 | Day #2: Orientation & Snap

Joe Paris — Thu, 13 Dec 2012 17:21:36 -0000

Updating results.innerText for the simple sensor demo does not work. I couldn't get it to work with my code and after downloading your source from GH I am getting the same results. Debugging shows that the call to sensor.addEventListener() on line 13 of SimpleOrientationSensor.js fails to set the event handler for onorientationchanged. I'm clueless as to why, any idea?

Re: 31 Days of Windows 8 | Day #5: Settings Contract

Myke — Wed, 12 Dec 2012 11:37:47 -0000

Very good, concise explanation, as well as informative.

Re: 31 Days of Windows 8 | Day #3: The Splash Screen

csell5 — Tue, 11 Dec 2012 13:54:33 -0000

Thanks Myke. I fixed it.

Re: 31 Days of Windows 8 | Day #3: The Splash Screen

Myke — Tue, 11 Dec 2012 13:19:46 -0000

Just a proofing note. The first sentence says that this is day 2 when it really is day 3.

Re: 31 Days of Windows 8 | Day #9: Live Tiles

mimeArtist — Thu, 06 Dec 2012 05:27:06 -0000

Hi Clark,

I've been trawling the web and not sure if it's possible or not, but have you encountered a way to update a tile that is just a bookmark from IE10?

E.G If I bookmarked a new website, it could update depending on an XML on said sites server?

Not sure if this thing exists, but would be great if it did

Re: Downloads

Hwang — Mon, 03 Dec 2012 08:30:35 -0000

good

Re: 31 Days of Windows 8 | Day #20: Printing

csell5 — Wed, 21 Nov 2012 13:24:26 -0000

Thanks Oscar, make sure you go back to the start and catch the other 20 too ;)

Re: 31 Days of Windows 8 | Day #20: Printing

Oscar Vargas — Wed, 21 Nov 2012 12:56:46 -0000

I will be following these series starting today, they are excellent!
thanks a lot

Re: 31 Days of Windows 8 | Day #20: Printing

Oscar Vargas — Wed, 21 Nov 2012 12:56:00 -0000

Nice! thanks

Re: 31 Days of Windows 8 | Day #4: New Controls

PincoPallino — Thu, 15 Nov 2012 05:35:46 -0000

Really usefull ! ...

Re: 31 Days of Windows 8 | Day #13: Navigation

csell5 — Tue, 13 Nov 2012 17:09:39 -0000

No problem. Thank you for reaching out too!

Re: 31 Days of Windows 8 | Day #13: Navigation

Tim Laubacher — Tue, 13 Nov 2012 12:11:35 -0000

Great, that helps - thanks! I think I know what I'm doing now.

Keep up the good work on the articles and thanks for doing them!

Re: 31 Days of Windows 8 | Day #13: Navigation

csell5 — Tue, 13 Nov 2012 09:14:35 -0000

No no. good questions. The whole point of writing this is to distill down the huge amount of stuff out there and get simply get stuff done.

You can think of app.onready similar to the browsers window.onload but at the application level for Windows Store Apps. app was just my shortcut to WinJS.Application and onready is just a function off that. The navigation app template has that defined at the top. The onready function wasn't there, I added it.

WinJS.Application.onready = function () {
WinJS.Utilities.query("a").listen("click", anchorHandler, false);
}

Now having said that onready might not be the function you really want to load in. You have 5 seconds to get your app loaded for the user. onloaded might be a better place to load up things like event handlers simply because that will happen later on and not block startup. Regardless for our purposes here they both are fine.

Then my anchor handler looked like such

function anchorHandler(eventInfo) {
eventInfo.preventDefault();
var link = eventInfo.target;

WinJS.Navigation.navigate(link.href);
}

In my article I was trying to speak at more of the abstract level and not that of the exact but I will go back and look at things.

The real problem with what you have above is zero idea about what link you should really navigate too. Since you attached to all anchor tags you need to know what the href is that the user clicked on.

Check out the source here: https://github.com/csell5/31Da...