Quote:
Originally Posted by KevinH
Is it just people against change (even though it prevents a crash) or something tangible?
|
I feared this kind of reaction in the back of my mind, but yes... when people mention things like "unintuitive" in their reasoning, I find that it usually translates to "
I'll have to adjust my process", rather than something actually
being unintuitive. Had Sigil not used native dialogs on Windows all along, we'd not be having a discussion about intuitiveness. *shrug*
I'm not exactly opposed to offering people a way out of this recent change, but I'm not really sure it's in their best interest in the long run, either. Because I can see an eventual transition to non-native dialogs
everywhere in Sigil (for
all platforms). The amount of code we maintain that determines
how dialogs are launched on the various supported platforms (not to mention code needed to prevent platform specific crashes) is already clunky and hard to maintain. Non-native just tends to work everywhere without barfing.
If we allow a way for individual platforms to override non-native dialogs in that potential
non-native-for-all future edition of Sigil, we'd need a utility function of some kind that would that handle (in a cross platform manner) whether a native or non-native dialog was required. That function could then be used everywhere a dialog is called for.
I'm afraid I'm not interested in coding (or maintaining) any more piecemeal stuff for dialog launches scattered throughout Sigil's codebase.