跨平台适配系统标准的Redo快捷键，有无优于宏的实现方案？

Great question! Preprocessor macros get the job done, but they can lead to messy, scattered platform-specific logic that's hard to maintain long-term. Let's look at a few cleaner, more scalable alternatives:

1. Leverage your GUI framework's built-in platform detection #

Most modern GUI toolkits (like Qt, GTK, or Electron) provide native APIs to detect the current runtime platform, which avoids scattering #ifdef blocks across your code. This keeps all shortcut logic centralized in one place.

Example with Qt: #

void setupKeyboardShortcuts(QApplication* app) {
    const QString platform = QGuiApplication::platformName();
    
    if (platform == "linux") {
        app->setAccelForAction("window.redo", "<Primary><Shift>Z");
    } else if (platform == "windows") {
        app->setAccelForAction("window.redo", "<Primary>Y");
    } else if (platform == "cocoa") { // macOS
        app->setAccelForAction("window.redo", "<Meta><Shift>Z"); // Follows macOS's standard redo shortcut
    }
}

Example with GTK: #

void setup_shortcuts(GtkApplication *app) {
    const gchar* os_name = g_get_os_info(G_OS_INFO_KEY_NAME);
    
    if (g_str_equal(os_name, "linux")) {
        gtk_application_set_accels_for_action(app, "window.redo", (const gchar*[]){"<Primary><Shift>Z", NULL});
    } else if (g_str_equal(os_name, "windows")) {
        gtk_application_set_accels_for_action(app, "window.redo", (const gchar*[]){"<Primary>Y", NULL});
    } else if (g_str_equal(os_name, "macos")) {
        gtk_application_set_accels_for_action(app, "window.redo", (const gchar*[]){"<Meta><Shift>Z", NULL});
    }
}

2. Use a configuration-driven approach #

Store platform-specific shortcuts in external config files (JSON, YAML, etc.) and load the appropriate file at runtime. This lets you modify shortcuts without recompiling code and makes it easy to add support for new platforms later.

Example structure: #

• config/linux_shortcuts.json:

  {
    "window.redo": "<Primary><Shift>Z",
    "window.undo": "<Primary>Z"
  }
  

• config/windows_shortcuts.json:

  {
    "window.redo": "<Primary>Y",
    "window.undo": "<Primary>Z"
  }
  

Load logic (pseudocode): #

void loadShortcuts(Application* app) {
    std::string platform = detectCurrentPlatform();
    std::string configPath = "config/" + platform + "_shortcuts.json";
    
    // Parse JSON file
    auto shortcuts = parseJson(configPath);
    
    // Apply shortcuts to the app
    for (auto& [action, shortcut] : shortcuts) {
        app->set_accels_for_action(action, shortcut);
    }
}

3. Encapsulate platform logic in a dedicated utility class #

If you still need to use preprocessor macros, wrap all platform-specific shortcut logic into a single utility class. This keeps macros contained and makes your main codebase cleaner.

Example: #

class PlatformShortcuts {
public:
    static std::string getRedoShortcut() {
#ifdef __gnu_linux__
        return "<Primary><Shift>Z";
#elif _WIN32
        return "<Primary>Y";
#elif __APPLE__
        return "<Meta><Shift>Z";
#endif
    }

    // Add other shortcut methods here (undo, copy, paste, etc.)
};

// Usage in your main code
application->set_accels_for_action("window.redo", PlatformShortcuts::getRedoShortcut());

All these approaches keep your platform-specific logic centralized, making your code easier to read, test, and extend. Compared to scattered #ifdef blocks, they reduce the risk of bugs from missed platform checks and make it simpler to add new shortcuts or support additional platforms later.

内容的提问来源于stack exchange，提问作者Keyikedalube Ndang