My mouse pointer briefly turns into an "X" when loading a program that uses crossover

Discussion in 'macOS' started by doxavita, Nov 14, 2010.

  1. doxavita macrumors 6502a

    Jul 6, 2010
    My mouse pointer briefly (1 second) turns into an "X" when loading a program that requires crossover or crossover itself.

    Anybody know what this means?

    The other day I made a force-quit on crossover after taking long to finish a task I had assigned it. After that I was unable to use crossover (wouldn't load), so I reboot my Mac, and then I was finally able to keep using it.

    I'm not sure if it did that "X" thing before the force-quit. But I'm thinking, if I had corrupted or damaged any files AFTER the force-quit, the program wouldn't even load at all or it would give me an error message. The program does indeed load, so I just want to know if this pointer change is an issue.

    I tried reinstalling crossover, (drag and drop to trash the icon) and it still did that X thing again.

    What are your thoughts?

  2. larkost macrumors 6502a

    Oct 13, 2007
    The X is because it is using X-windows, and that is the default cursor for X-windows. This is a bit odd, since this is Windows code calling Windows display code, that gets translated into X-windows calls, which then gets translated for use with Apple's display system, but it works, and they are getting most of that path for free (all of it if you count the Wine code).
  3. milbournosphere macrumors 6502a


    Mar 3, 2009
    San Diego, CA
    I believe that crossover uses a version of X11 to do its GUI work. The 'X' cursor icon indicates that the program is 'thinking'. Basically, it's like the hourglass in Windows or the spinning beach ball in OS X.
  4. doxavita thread starter macrumors 6502a

    Jul 6, 2010
    What are your thoughts on that force-quit I made?

    Like I said, after the force quit I wasn't able to load crossover, but after a reboot the program ran again.

    What are the chances something got damaged as a result of this?

    (otherwise the program wouldn't even run at all, right?)

    My thinking is that the X shows up because the system realizes it needs to call additional external code to run my app. (Which explains why the cursor only changes for about a sec or so.)

Share This Page