I used to use ultramon but in all honesty the taskbars were always buggy for me, to the point i eventually just lived without it, after using windows 8 for a few months now on the preview releases, the new taskbars in windows actually feel like they work correctly apart from one pretty major point, for some reason some applications do not correctly move to the second taskbar in some situations (when you have the setting which enables only programs open on each screen show up on that screens taskbar). Specifically WinSCP and Mircosoft office applications both break this functionality, I would hope office would be fixed for the final release though. but apps on the taskbar on the screen they actually relate to is more than just a huge plus for me, its a game changer, for £25 I would pay for this feature on its own.

Dealt with that option recently, the settings changed in the Web Options panel in Excel have no effect on anything except the save as type Simple Web page and Web Page. in the save as dialog. If you want to import as a certain Encoding go to Data (in the ribbon) > From Text, it will ask for a file, and then the Text Import Wizard will open up, on the first page you can set the File Origin which is actually the file encoding.

I agree learning rules about when you can and cant do certain things in a programming language is important and therefore there are context dependent rules for every language that must be learned from an early point. However I do not feel that (in this situation) within a double quoted string is enough of a context switch to cause the user to feel like they are now applying a different rule set. This is especially true in this specific case because PHP will let you do the wrong thing(use un-qouted array indexes outside double quoted strings), other languages, if you apply the context rules in the wrong place you will likely get errors thrown at you and your code will not run (be it a compiled or scripted language) however in PHP in this specific situation(context) the PHP engine will "fix" your incorrect code, almost silently (How silent it is about this depends on your systems error display level), since this is a scripted language PHP has to fix your code every time. Since the user is none the wiser about their error, they will keep doing it that way in the future because "it just works", and then you end up with questions like "This works on my dev box but when I upload it to my live machine it throws errors all over the place!!!! this is why I hate PHP!!!!!" The simpler your rule set, the easier it is to teach and to remember, I would (and am) strongly argue that teaching the use of $array[index] in any context should not be done and that the use of {} to wrap variables is a far more robust system, but I cant stop you, I can only comment on why I think teaching its use is bad in any situation. I will not argue whether PHP is a good or a bad language to write websites in. It has its flaws(some which are quite major) but it has its positives to, like pretty much every programming language, I think its a great pick up and code language, kind of the VB of web languages :D

That's stupid, how would you go about using a defined constant as an array index within a double quoted string then? You would have to resort to the curly braces. This means there is a double standard, one when you are outside a double quoted string and one when you are inside. (My point here is not that PHP is a bad language it is that "quirks" such as this shouldn't be seen as a feature of a language) If that is true I would argue its not a well defined shortcut if you have to apply the rule "well it works in that situation but not in this situation" However, I still stand by my statement that it is not a good idea under any circumstance to tell people to use $array[index] as opposed to $array['index'] even in the case where it may work without generating a E_NOTICE error, the chance of the user misunderstanding and using it in other places simply because it works is too high.

BAD Advice See: http://de.php.net/manual/en/language.types.array.php#language.types.array.foo-bar[^]

That's bad bad bad and more BAD advice. Always use quotes around array indexes in PHP if not what you are essentially telling php is that there is a defined constant with the name of recid, PHP looks for it and doesn't find it, and replaces it with the string 'recid' and generating a E_NOTICE error for you. For more info see here: http://de.php.net/manual/en/language.types.array.php#language.types.array.foo-bar[^] Member 8857022 showed the correct way of doing this using {} to wrap the variable.