为何glutMouseFunc跟踪状态而glutKeyboardFunc需分设两个回调函数？

Great question—this is one of those API design quirks that ties back to GLUT's roots and how input handling worked when it was first built. Let's break down the reasons:

• Underlying System Event Models
  GLUT was originally built on top of X11 (the Unix window system), and it closely mirrored how X11 handled input events. For mouse input, X11 sends ButtonPress and ButtonRelease events that both include a state flag to indicate if the button was pressed or released. GLUT wrapped these into a single glutMouseFunc callback, passing that state directly to you. For keyboards though, X11 uses separate KeyPress and KeyRelease events with no shared state flag—so GLUT followed suit by creating separate glutKeyboardFunc (for presses) and glutKeyboardUpFunc (for releases) callbacks.

• Usage Pattern Differences
  Mouse interactions often come in paired press-release actions (like clicking, dragging, or releasing a button to finish an action). Having a single callback with a state parameter makes it easy to handle both parts of the interaction in one place without splitting logic across functions. For keyboards though, developers frequently want to handle press and release events independently—like triggering a movement when a key is pressed, and stopping it when the key is released. Splitting these into separate callbacks keeps that logic clean and avoids having to add conditional checks for state in every keyboard handler.

• Historical API Tradeoffs
  GLUT was designed to be a lightweight, easy-to-use wrapper for OpenGL, and its input APIs prioritized simplicity for common use cases. At the time, auto-repeat for keyboard keys was a common system feature that could generate multiple press events while a key was held. Splitting press and release callbacks made it easier to distinguish between initial presses, repeated presses, and the final release—something that would have been more clunky to handle in a single callback with state flags.

It's totally reasonable to wrap both keyboard callbacks into a single handleKey function like you're doing—many GLUT developers do this to keep their input logic centralized. The design difference just reflects the input paradigms and system constraints GLUT was working with when it was created.

内容的提问来源于stack exchange，提问作者Jesse McDonald