In visual studio go to Help -> "Add and remove help content" and that will allow you to download entire topics like .net 4.5 docs.
You can even throw whatever you download on a network, and anyone can access it from there rather than individually needing to download it. That requires setting something in the registry though to access from the network (let me know if you want to know though).
My solution required marking each coord as non-empty when I dropped a rect on it. I was able to hack something that worked (non-zero-len string stuffed into the structure), but I'd much rather know what the structure was instead of guessing.
For me I like static typing because it adds a sanity check of the data getting passed around. Sure, most of the time it catches nothing, but it is nice when it does. Humans will always make mistakes, so static typing improves the amount of help\tools computers can put forth.
Exactly my feelings about it. Being able to specify types, and having the compiler warn me of mistakes is a godsend when comparing it to just writing javascript.
And when valid javascript is valid typescript, it seems odd to not opt to use it when the only addition is a compile step to ensure sanity.
It feels like using the mouse is the tradeoff for using Microsoft products. I use Visual Studio and SQL Sever at work, and they are such a productivity boost, but I hate how often I have to use the mouse. The problem is many of the benefits of using their products perks would be difficult to navigate around with a keyboard.
At times it's frustrating how often you have to use the mouse, but other times it's so great compared to any alternative ways (that I know of).
Yes, sometimes I think jps intentionally ignores bug reports that are not in the Technical support forum. ;) that said, ST lacks a coherent stratgey to collect and evaluate bug reports and feature requests. There's a technical support forum, but that can mean anything from "how do I do X" to "Here's a bug" to "I want the API to do this". It needs a bug report flow with clear rules, like you need to add the steps to reproduce, and a status indicator such as acknowleged, wontfix, the option to reference duplicates etc. User Echo kind of works for feature requests, but it seems to be abandonded as well. There's now a community bug tracking project, but jps has been silent on that too. I know it's not easy to handle support, but there's a lot of room for improvement here.
Agreed. I had searched for a couple minutes to make sure I was putting the bug in the right place when I reported it. And even then there was no great way to search that it wasn't a duplicate considering how easy it is for forum posts to collide on a search.
IE10 only has a smaller chrome when windowed. When maximized, it has the same (within a couple px) top chrome, but combines tabs and nav into one, so the chrome is actually less useful. It's mind-boggling that MS shipped something with so little polish.