The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    MX Revolution mouse w/ uberoptions

    Discussion in 'Accessories' started by FusiveResonance, Jan 20, 2010.

  1. FusiveResonance

    FusiveResonance Notebook Evangelist

    Reputations:
    143
    Messages:
    421
    Likes Received:
    0
    Trophy Points:
    30
    I have the latest version of uberoptions and setpoint.

    My settings are configured such that clicking on the scroll wheel is a mouse 3 action, and clicking on the search button shifts scroll modes.

    When i boot up my laptop, i usually have to click the scroll wheel and the search button a few times to get everything functioning like normal.

    Sometimes though, the search button will not toggle scroll modes. Every second click of the button will result in a sound (which is similar to the microgear shifting) but doesn't actually shift scroll modes.

    Thanks in advance for all the help.

    Running win 7 x64 btw.
     
  2. Vogelbung

    Vogelbung I R Judgemental

    Reputations:
    3,677
    Messages:
    4,067
    Likes Received:
    699
    Trophy Points:
    181
    How old is it?
     
  3. Step666

    Step666 Professional chubby Chris Pratt impersonator

    Reputations:
    3,329
    Messages:
    1,922
    Likes Received:
    89
    Trophy Points:
    66
    I'm using a Logitech MX5000 bluetooth keyboard and an MX1000 bluetooth mouse with my desktop and I too have uberOptions installed.

    When I first start up my PC, it tends to take it a little while for the additional functionality to kick in.
    Initially it's as if the mouse and keyboard work but only as standard/generic devices, then the custom-defined buttons starting to work, the LCD display on the keyboard sorting itself out and Setpoint picking up the battery information.
    I reckon what happens is that Setpoint takes a short while after starting up to actually take over control of any connected devices and that prior to that, Windows just treats them as generic ones.