[HAZARDLEADER]

Ok, Logitech site says that the G700 mouse does not support Mac os, will it still work considering my last logitech hard ware installed Logitech control center?
Its dumb assed I know. 

[Scourge of Ages]

Without research or testing, I would say that the software probably won't work though the basic mouse functions should. So likely you'll get both buttons, good tracking and the wheel, anything else is iffy. I've used a USB mouse before on Macs, and it just plugged-and-played.

[jr2]

Maybe you could find a 3rd party solution?

Quick Googling pulled up what looks to be a solution:

http://hints.macworld.com/article.php?story=20100818101533988

[HAZARDLEADER]

You guys are awesome! Thats exactly a solution I needed to hear! Thanks guys. 

[Nuke]

its all a usb hid class which is standard for all usb devices. its when you add extra buttons to the mouse that you need something extra, like features in which you need a peice of software to access. but its usually built around the hid class instead of through it. i want to do some usb projects, but the software side is really ****ing complicated.

[z64555]

i want to do some usb projects, but the software side is really ****ing complicated.

SDL looks far more friendly than most of DirectInput's functions.

[Nuke]

i want to do some usb projects, but the software side is really ****ing complicated.

SDL looks far more friendly than most of DirectInput's functions.

i should have said firmware side. i was thinking more about designing custom usb devices. there are 2 ways to go about it, use an mcu with hardware usb support, or use a software usb implementation (like vusb) to bitbang the low speed protocol. i already use sdl for pretty much everything i do on the pc side.

[z64555]

I'd opt for the MCU with USB support, as it's basically a much faster version of RS-232 signals. I wouldn't be surprised if there was a lib out there that covered the USB protocols already, if not, I think they have a free publication that goes over the operation of USB 1.0.

[Nuke]

rs-232 is fairly simple to work with. but it has speed and cabling length limits that even a low speed usb device can out perform. low speed usb is 1.5mbit/sec (which is your limit with a software usb implementation), where as most rs-232 seems to have an upper limit of 115200 (higher baud rates are supported but are less commonly supported). also rs-232 doesn't enforce any high level packet structure or protocol, it just pipes out bytes, what you do with them is up to the developer. so serial baud rates do not include protocol overhead. ive wrote several protocols on serial, where the best ones have about 1/8th overhead, and others the overhead is about 25% or greater. generally more overhead == less error prone, so you're free to balance it as needed. usb on the other hand does all this stuff for you behind the scenes, so you get the full 1.5mbit for data. usb also comes with an hid stack so if you want to do a mouse, keyboard, joystick, etc, the spec has features for that built in. all the features of course make usb devices a complicated affair. i found a good tutorial on it here:

http://codeandlife.com/2012/01/22/avr-attiny-usb-tutorial-part-1/

but im trying to finish up my last project, as im kinda short on breadboards and other prototyping tools. i got a bunch of other gismos ive been waiting to play with as well.