But in the pantheon of such things, I stand by my guesstimate that the matter of missing key command text in tooltips “should be easy to fix. Of course, there is always the matter of testing & validation and perhaps user documentation (which is also localized), so without a doubt there is work required, even for the most trivial thing.
DORICO KEY COMMANDS PLUS
That, plus the fact that, like any modern app, Dorico supports many languages (aka “localization”) means that the tooltip text that gets displayed on mouseover events comes from a lookup table of these strings, aka “resources.” Adding localization to a legacy app is a huge PITA, if not rocket science, but adding more entries in the lookup table should truly be “no big deal.” In Dorico, however, users can redefine key commands and also assign MIDI commands. In the trivial case, that would just be a matter of adding text to the display string. In some cases keys on the iOS keyboard will trigger special behaviours inside popovers, but we are still working to improve this. In general key commands only work with an external keyboard, not the onscreen iOS keyboard.
DORICO KEY COMMANDS CODE
I certainly don’t know their code and perhaps there are some barriers you and I cannot see that prevent something from being fixed or implemented - like the Apple Pencil “Scribble” support, which needs to be implemented in the Qt framework first.īut in this case, I didn’t think it unreasonable to surmise that if some tooltips already have the key commands in their resource text, it would not take a large, complex effort to add it to the ones where it is missing. The Dorico-for-iPad documentation is rather sparse in this regard. So believe when I say I meant no disrespect to the obviously highly-competent Dorico team here. Or similarly, insisting that “It can’t possibly take that long” to do the work - and then pressuring Engineering senior management (or worse, the CEO) for your team to do it in half the time you said it would take (and, engineers being engineers - myself included - are already over-optimistic about the schedule by a factor of 2 or more, anyway! (Ask me how I know Hey Leo - Methinks depends on the developer and the nature of the bug report, but i’ve been a professional computer scientist & sw engineer for almost 40 years and processing bug reports & feature requests are de rigueur - and almost always the submitter has an opinion along the lines of, “How hard can it be?” Usually that doesn’t rise to the level of PITA unless it’s the Marketing folks insisting that some major new feature be added to the product version you’re almost ready to release.
0 kommentar(er)
