An item that provides click-through is one that a user can activate with one click, even though the item is in an inactive window. (To activate an item that does not support click-through, the user must first make the containing window active and then click the item.) Although click-through can make some user tasks easier, it can also confuse users if they click items unintentionally.
Click-through is not a property of a class of controls; any control, including toolbar items, can support click-through. This also means that you can support click-through for any subset of items; you don’t have to choose between supporting click-through for all items in a window or none. Follow the guidelines in this section so that you can support click-through when it’s appropriate.
Avoid providing click-through for an item or action whose result might be dangerous or undesirable. Specifically, avoid enabling click-through for an item that:
Performs a potentially harmful action that users can’t cancel (for example, the Delete button in Mail)
Performs an action that is difficult or impossible to cancel (such as the Send button in Mail)
Dismisses a dialog without telling the user what action was taken (for example, the Save button in a Save dialog that overwrites an existing file and automatically dismisses the dialog)
Removes the user from the current context (for example, selecting a new item in a Finder column that changes the target of the Finder window)
Clicking in any one of these situations should cause the window that contains the item to be brought forward, but no other action to be taken.
In general, it’s safe to provide click-through for an item that asks the user for confirmation before executing, even if the command ultimately results in destruction of data. For example, you can provide click-through for a delete button if you also make sure to give users the opportunity to cancel or confirm the action before it proceeds.
Think twice before supporting click-through for items that don’t provide confirmation feedback. Specifically, consider how dangerous the action might be, and determine how difficult it will be for the user to undo the action after it’s performed. For example, the Mail Delete button does not provide click-through because it deletes a message without asking for confirmation, which is a potentially harmful action that can be difficult to undo. On the other hand, click-through for the New button in Mail is fine because its resulting action is not harmful and is easy to undo.
Ensure that items that don’t support click-through appear disabled when their window is inactive. The disabled appearance helps users understand that these controls are unavailable. For example, the Delete and Mark as Junk buttons in the inactive Mail window shown below don’t support click-through.
What key combination do I have to press to create a line break in a cell in Excel for Mac 2011? The Windows combination of Alt+Enter does not work on the Mac.
Is there a way to change a printer’s IP address in OSX (Lion) without having to add a new printer? I did find Printer IP Remedy, but was curious if there was an ‘official’ method.
A
You can do this in the CUPS web interface with the following steps:
Open Terminal.app and run cupsctl WebInterface=yes. This enables the CUPS web interface
Open http://127.0.0.1:631/printers in your web browser
Click on the printer you want to change. From the “Administration” drop down, select “Modify Printer”.
Log in with your local admin account
Select the new printer IP either from “Discovered Network Printers” or add it manually with “Other Network Printers”. Make sure that you keep the same connection protocol as it says in “Current Connection” (for me, this was LPD).
Once you’re done with this, Mac OS X will directly print to the new IP address. There is no need to reboot or so. If you want to disable the CUPS web interface again, run cupsctl WebInterface=no.
The web interface is currently disabled. Run “cupsctl WebInterface=yes” to enable it.
After enabling it like the CUPS web interface wit cupsctl WebInterface=yes, you can see I have the same printer configured multiple times with different communication protocols and output languages:
Check the modifications (optionally change Description/Location)
Click “Continue”
Keep the driver
Click “Modify printer”
For LPD, note the current address (like lpd://192.168.71.52/), then follow the IPP steps, but choose “LPD/LPR Host or Printer” and enter a valid lpd address.
This is also the place where you can change “Default options”, like paper size (which – for all but the first – somehow defaulted to US Letter 11 inch, while it is actually filled with A4 paper).
At the end, disable the web interface: cupsctl WebInterface=no.
So I created this alias to connect from my Mac to the internal address of my ESXi rig:
alias ssh-esxi-X10SRH-CF-internal='TERM=xterm ssh -p 22 root@192.168.71.91'
The trick is the bold part: TERM=xterm (which you can also replace by export TERM=xterm; if you want future ssh sessions to use the same [wayback] TERM setting).
The reason is that the Mac defines the TERM variable as containing xterm-256 which is defined on the Mac itself, but ESXi has a hard time coping with it.
It seems I already did something similar on ESXi itself to get esxtop working: ESXi: when esxtop shows garbage. That was on the ESXi side and works as well for this problem too.
However, it is a bit harder to have a script run during ESXi boot time that sets this, so it is easier to fix this on the Mac side.
It works for all OS X and ESXi versions I’ve tested so far.
This has happened to me on most Macs with most Apple Mac OS X / MacOS / whatever versions: the built in sound controls for internal speakers and head phones fail to work (keyboard shortcuts and UI both fail).
The Wiert Corner - irregular stream of stuff 