Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support progress bar/marker #9

Open
snmnzl opened this issue Oct 18, 2019 · 4 comments
Open

support progress bar/marker #9

snmnzl opened this issue Oct 18, 2019 · 4 comments
Labels
feature Feature request

Comments

@snmnzl
Copy link
Contributor

snmnzl commented Oct 18, 2019

For continuous work on one .tsv document in different sessions, it would be handy to be able to mark the progress within that document.
This could fx be realized through an additional column which places a visual marker (e.g. arrow icon) in a selected row by clicking on it.

@cneud cneud added the feature Feature request label Oct 22, 2019
@cneud cneud changed the title support progess bar/marker support progress bar/marker Nov 7, 2019
@cneud cneud added this to the 0.0.1 milestone Mar 19, 2020
@cneud
Copy link
Member

cneud commented Apr 8, 2020

My current thinking is to allow the placement of ONE continue marker that can be set anywhere in the LOCATION column. Upon opening a TSV file that contains such a continue marker, it would offer to jump directly to that line. Would that be of help @snmnzl @JZinck ?

@labusch
Copy link
Member

labusch commented Apr 9, 2020

neat could also store the position at save time within the tsv file as a comment.
When that tsv file is opened again, it could jump automatically to that position.

@cneud
Copy link
Member

cneud commented Apr 9, 2020

neat could also store the position at save time

Even better idea!

@JZinck
Copy link

JZinck commented Apr 10, 2020

Both ideas are very good. I could use the marker while revising as well, since I have to scroll up and down a couple of times and could just use the marker like a bookmark. But the risk of forgettig to put it down before saving and exiting (which I am worrried about) would be nullified by the saved position feature. So I can see the merit of combining them over each individual idea.

In case this is an either-or-situation I think the marker would be more useful to the way I use the tool (but this might differ from what other users might need).

@cneud cneud removed this from the 1.0.0 milestone Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature request
Projects
None yet
Development

No branches or pull requests

4 participants