Tewha.net https://tewha.net/tags/tips/ Recent content on Tewha.net Hugo -- gohugo.io en-us Sun, 07 Aug 2011 14:00:00 +0000 How to reset Wii to lower resolution https://tewha.net/2011/08/how-to-reset-wii-to-lower-resolution/ Sun, 07 Aug 2011 14:00:00 +0000 https://tewha.net/2011/08/how-to-reset-wii-to-lower-resolution/ <p>So you’ve set your Wii to 480p, then moved it back to a TV that supports only 480i. How do you fix it?</p> <p>I searched for this for a while and found a few wrong and complicated answers.</p> So you’ve set your Wii to 480p, then moved it back to a TV that supports only 480i. How do you fix it?

I searched for this for a while and found a few wrong and complicated answers.

One way is to use the composite cable instead of the component cable. Your Wii came with a composite cable, and if you’re only using 480i the component cable does nothing extra for you anyway.

But what if you can’t find the composite cable? This was the case for me, after my move. The answer is ridiculously simple:

  1. Unplug the component cable on the Wii end.
  2. If the Wii is already on, press the Reset button. If it was off, turn it on.
  3. Wait a couple seconds. The Wii will notice there’s no component cable plugged in, and switch to 480i mode.
  4. Plug the component cable back into the Wii.
]]> Flux adjusts your monitor’s color temperature https://tewha.net/2010/12/flux-adjusts-your-monitors-color-temperature/ Sat, 04 Dec 2010 16:00:00 +0000 https://tewha.net/2010/12/flux-adjusts-your-monitors-color-temperature/ <p>Install <a href="http://www.stereopsis.com/flux">Flux</a> right now.</p> <p>What does it do? Well, at sunset it adjusts the color temperature of your monitor to make it warmer and less glaring. At sunrise, it adjusts it back.</p> <p>I installed it yesterday afternoon; yesterday and today at sunset, it automatically adjusted my monitor’s color temperature. The difference on the eyes is nothing short of amazing. And if you need to do some accurate color work, it has a menu that lets you turn it off for an hour.</p> Install Flux right now.

What does it do? Well, at sunset it adjusts the color temperature of your monitor to make it warmer and less glaring. At sunrise, it adjusts it back.

I installed it yesterday afternoon; yesterday and today at sunset, it automatically adjusted my monitor’s color temperature. The difference on the eyes is nothing short of amazing. And if you need to do some accurate color work, it has a menu that lets you turn it off for an hour.

]]> Xcode tip: Renaming files shared by projects https://tewha.net/2010/12/xcode-tip-renaming-files-shared-by-projects/ Sat, 04 Dec 2010 16:00:00 +0000 https://tewha.net/2010/12/xcode-tip-renaming-files-shared-by-projects/ <p>What if you want to rename a file that’s used in multiple Xcode projects? Well, previously I’d rename the file in one project, then open each project in series and correct broken references. But I discovered today that this is unnecessary. If you open all of your projects first, Xcode will fix the references across <strong>all</strong> of your open projects as you rename files in <strong>any</strong> of the projects.</p> <p>For all I know, this has always been a feature of Xcode. But I’ve never noticed it before. So for this stunning display of common sense: Well done, Apple!</p> What if you want to rename a file that’s used in multiple Xcode projects? Well, previously I’d rename the file in one project, then open each project in series and correct broken references. But I discovered today that this is unnecessary. If you open all of your projects first, Xcode will fix the references across all of your open projects as you rename files in any of the projects.

For all I know, this has always been a feature of Xcode. But I’ve never noticed it before. So for this stunning display of common sense: Well done, Apple!

]]> Better Xcode warnings through .xcconfig files https://tewha.net/2010/11/better-xcode-warnings-through-xcconfig-files/ Sat, 27 Nov 2010 16:00:00 +0000 https://tewha.net/2010/11/better-xcode-warnings-through-xcconfig-files/ <p>Peter Hosey <a href="http://boredzo.org/blog/archives/2009-11-07/warnings">posted a list of warnings he turns on</a>. Here’s the warnings I turn on. It’s mostly the same list.</p> <p>Rather than set these per project, I have a .xcconfig file I add to my project. I then base each build configuration off this file. Changing the .xcconfig file changes all projects based on it (though with the current Xcode, it’s sometimes necessary to reload the project to get the settings to take).</p> Peter Hosey posted a list of warnings he turns on. Here’s the warnings I turn on. It’s mostly the same list.

Rather than set these per project, I have a .xcconfig file I add to my project. I then base each build configuration off this file. Changing the .xcconfig file changes all projects based on it (though with the current Xcode, it’s sometimes necessary to reload the project to get the settings to take).

// // MoreWarnings.xcconfig // // Created by Steven Fisher: // http://tewha.net/2010/11/xcode-warnings/ // See also: // http://boredzo.org/blog/archives/2009-11-07/warnings //

GCC_WARN_CHECK_SWITCH_STATEMENTS = YES
GCC_WARN_SHADOW = YES
GCC_WARN_64_TO_32_BIT_CONVERSION = YES
GCC_WARN_INITIALIZER_NOT_FULLY_BRACKETED = YES
GCC_WARN_ABOUT_RETURN_TYPE = YES
GCC_WARN_MISSING_PARENTHESES = YES
GCC_WARN_ABOUT_MISSING_FIELD_INITIALIZERS = YES
GCC_WARN_ABOUT_MISSING_NEWLINE = YES
GCC_WARN_SIGN_COMPARE = YES
GCC_WARN_UNDECLARED_SELECTOR = YES
GCC_WARN_UNUSED_FUNCTION = YES
GCC_WARN_UNUSED_LABEL = YES
GCC_WARN_UNUSED_VALUE = YES
GCC_WARN_UNUSED_VARIABLE = YES
GCC_WARN_ABOUT_MISSING_PROTOTYPES = YES
GCC_WARN_TYPECHECK_CALLS_TO_PRINTF = YES
GCC_WARN_ABOUT_DEPRECATED_FUNCTIONS = YES
GCC_WARN_HIDDEN_VIRTUAL_FUNCTIONS = YES
GCC_WARN_ABOUT_INVALID_OFFSETOF_MACRO = YES
GCC_WARN_NON_VIRTUAL_DESTRUCTOR = YES
GCC_TREAT_WARNINGS_AS_ERRORS = YES
RUN_CLANG_STATIC_ANALYZER = YES

Peter wrote a great explanation of why you’d want most of these warnings, which I’m not going to attempt. I’ve added some C++ warnings, too. They don’t do anything with clang 1.6, but might be useful in the future.

A few notes:

  • Like Peter, I don’t turn on GCC_WARN_UNUSED_PARAMETER. Although you can add __unused to each parameter to disable the warning, doing so breaks Xcode’s code formatting. I use code formatting constantly, so anything that breaks it isn’t acceptable.
  • The warnings that were the most painful to turn on were GCC_WARN_64_TO_32_BIT_CONVERSION and GCC_WARN_SIGN_COMPARE. If you use int and NSInteger interchangeably, you’re going to have a tough time with these. (I don’t, but some of the internal libraries I use do.) These are also some of the more dangerous warnings to fix; if you’ve got automated tests, you should run them after every few corrections.
  • RUN_CLANG_STATIC_ANALYZER will roughly double (or more) the time your project takes to compile. I consider this a good trade: I rarely trigger a static analyzer warning now, but when I do I want to fix it.
  • Also note the GCC_TREAT_WARNINGS_AS_ERRORS. If you are applying these to an existing project, you may start with hundreds of warnings. You’ll probably want to start with this set to NO and change it to YES after you’ve fixed the warnings.
  • Remember, too, that this changes the defaults for settings. You can still specify different settings in the build configuration! If the static analyzer is taking too long to run in one project, just turn it off in that one project but leave the .xcconfig file alone!
]]>