Is the [ttk::clickToFocus] meant
to be public? If so, needs docs.
If not, convention would suggest
we name it ttk::ClickToFocus instead.
Logged In: YES
Logged In: YES
The status of most of these is "intended for eventual public consumption but no guarantee of stability until Tile 1.0." There is an unresolved conflict between Tile's current state of stability and what we'd like to have for Tk 8.5.0.
Some of these routines I know are wrong (most of the grab-related stuff), some I suspect are wrong (takeFocus/takesFocus/clickToFocus), and others I'm pretty sure are OK; but I'm reluctant for any of them to be carved into stone at this point.
One approach we've used in this
situation before is an "unsupported"
command. For commands we want available,
but aren't fully ready to commit to
preserving, define them in and export
them from the
namespace. For example, we had
a few releases before enshrining it
as the new [encoding dirs].
Just a suggestion if it fits in
with other constraints.
Can we just live with this for 8.5? Hobgoblinning the core code that's shared with Tile would do more harm than good at this point.
The status of most of these is "Used internally, but intended for public consumption." One of two things can happen in future:
(1) The interface turns out to be OK and is made public. In this case, I just need to write TFM and nobody needs to change any code.
(2) The interface turns out to be wrong and needs to be changed. In this case, the old routine is [ttk::deprecate]d in version N+1 and can be killed in version N+2. In the meantime, application code gets a warning message.
Capitalizing all the function names or using the ::unsupported:: convention just causes code churn in the event of case (1), both internally and for application code that used the semi-public routines, and forces such code to add otherwise unnecessary version tests if it wants to continue to work with version N-1. And making these routines "fully public" for 8.5 means that they're carved in stone and can't ever be killed in the event of case (2).
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.