You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tom since you heavily improving everything right now I wanna mention two of my feature requests at the "Click-to-Continue" indicator...
Since the indicator is a indicator for "click-to-contiune" I wouldn't show it if in auto-forward or skip mode.
So the textbox should be updated as soon as you toggle afm or skip mode and the ctc is shown or hidden...
If you use the "nestled" option then you might have some rare cases where the ctc indicator
jumps to the next line, but your actual text fits perfectly in "one" line. That's because of text.append(ctc).... For some it might be ok but for some other it might look silly or is not what they want. How about a third option where the ctc is kind of "nestled" but not part of the text itself. So the position is dynamically (it follows the text position) and could be also outside/offscreen of your textbox
definition...?
The text was updated successfully, but these errors were encountered:
Tom since you heavily improving everything right now I wanna mention two of my feature requests at the "Click-to-Continue" indicator...
Since the indicator is a indicator for "click-to-contiune" I wouldn't show it if in auto-forward or skip mode.
So the textbox should be updated as soon as you toggle afm or skip mode and the ctc is shown or hidden...
If you use the "nestled" option then you might have some rare cases where the ctc indicator
jumps to the next line, but your actual text fits perfectly in "one" line. That's because of text.append(ctc).... For some it might be ok but for some other it might look silly or is not what they want. How about a third option where the ctc is kind of "nestled" but not part of the text itself. So the position is dynamically (it follows the text position) and could be also outside/offscreen of your textbox
definition...?
The text was updated successfully, but these errors were encountered: