My machine is running OS X 10.5, and I have 2 GB of RAM. (This is important because the solution requires messing with how Eclipse handles memory. If you have a different amount of RAM, these numbers may not work and you’ll need to fiddle with them.)

• Save your work and quit Eclipse.
• Open the Eclipse application package by right-clicking (or Control-clicking) on Eclipse.app and select “Show Package Contents.”
• Navigate to Contents→MacOS→, and open “eclipse.ini” in your favorite text editor.
• Edit the line that starts with -”XX:MaxPermSize” to say “-XX:MaxPermSize=128m”.
• Before that line, add a line that says “-XX:PermSize=64m”.
• Edit the line that starts with “-Xms” to say “-Xms40m”.
• Edit the line that starts ith “-Xmx” to say “-Xmx768m”.
• Save & relaunch Eclipse.

Worked like a charm for me.

Totally missing the point, Gizmodo asks, “Does anyone care?”, noting that users are already accustomed to the iPhone’s non-tactile keyboard, and that this particular haptic keyboard is buggy. Whatever; research clearly indicates that vibrotactile feedback for surface keyboards enhances interaction. Kudos to these folks at the University of Glasgow for beginning an open project on a popular platform to develop this much-needed software.

The way a program like this works is by keeping track of the “previous”, “current”, and “next” states in variables. The code inside one of the states is continuously executed, until the “next” state changes. Each time a state is entered or exited, the variables are updated. But by moving the state variable housekeeping to the header file, our switch statement in main() is much more straightforward.

Here’s the code for the macros in the header file:
#define STATE_ENTRY_ACTION if ( currentState != previousState ) {
#define STATE_TRANSITION_TEST previousState = currentState; } if ( nextState == currentState ) {
#define STATE_TRANSITION_TEST_EXCLUSIVE } else if ( nextState == currentState ) {
#define STATE_EXIT_ACTION } if ( nextState != currentState ) {
#define STATE_EXIT_ACTION_EXCLUSIVE } else if ( nextState != currentState ) {
#define STATE_END currentState = nextState; } break;

The EXCLUSIVE macros are used if you want to ensure that the state machine is run at least three times per state, making the timing of the function call more predictable.

Now adding a state here or there, or inserting functions at the right point in the routine is easy:

void main() {
   while( true ) {
      switch ( state ) {
         case state_n:
            STATE_ENTRY_ACTION
               doColor();
            STATE_TRANSITION_TEST
               checkUserInput();
            STATE_EXIT_ACTION
               fadeColor();
            STATE_END
      }
   }
}
I did not include a default case in this example, but for a real application it’s a good idea to always include one.

First, specify which nested layer you want to change. {labelitemi} refers to the outermost nested list, followed by {labelitemii}, and so on. Then specify the character you want to use with its LaTeX command.

Here’s how to specify a closed bullet (the LaTeX default) in the outermost nested list:
\begin{itemize}{labelitemi}{$\bullet$}
\item First item in the list
\item Second item
\item and so on
\end{itemize}


Any character can be used as a bullet character by writing its command in place of \bullet. Some characters that might be particularly useful:

\circ — An open circle
\cdot — A centered dot
\star — A five-pointed star
\ast — A centered asterisk
\rightarrow — A short right-pointing arrow
\diamondsuit — An open diamond

For a full list of character commands, see Hypertext Help with LaTeX: Binary and relational operators