Feature request: Increase per-book clipping limit

[fokrul-hasan]

Running CrossInk 1.4.0-tiny on an Xteink X3. Hit the per-book clipping cap, with no in-device way to free up slots:

• Deleting /My Clippings.txt doesn't help — the cap isn't tracked there. New clippings still fail on the same book afterward.
• "View Clippings" for the book is view-only — no delete/edit option.
• Only workaround found: manually deleting that book's .bin file from .crosspoint/clippings/ on the SD card via computer, which resets its clipping list (confirmed via docs — each book has its own file named by type + CRC32 of book path).

This mirrors the old bookmark cap issue (32 → 1024 per book, fixed in an earlier release). Could the clipping cap get the same treatment — either raised significantly, or an in-device delete/reset option added for individual clippings?

Happy to provide more details if useful. Thanks for the great firmware!

[farfromexact]

The per-book .bin behavior is useful evidence: the cap is not coming from My Clippings.txt, so deleting that file cannot reset the stored clipping count. I would treat this as two separate improvements:

1. Raise the per-book limit.
2. Add an in-device way to delete or reset clippings.

For the limit, the earlier bookmark change from 32 to 1024 is a sensible precedent, but the implementation should be checked for fixed-width counters, record-size assumptions, and available RAM before choosing the same value. A versioned migration is preferable to silently changing the binary layout.

For deletion, the safest UX would be View Clippings -> select one or more -> Delete, plus a book-level Reset Clippings action with a confirmation showing the number of records. The storage update should be atomic: write a temporary replacement file, flush it, rename it over the old file, and refresh the in-memory list only after the rename succeeds. That avoids leaving a partially rewritten .bin file if the device loses power.

Until that exists, the documented manual deletion is a reasonable recovery path, but it should be clearly labeled as a backup-first workaround because removing the file deletes the whole book's clipping list. A temporary higher cap would help immediately, while the on-device reset would solve the underlying usability problem without requiring users to remove the SD card.

[uxjulia]

@fokrul-hasan, I'm pretty sure I responded to you on Reddit about this? If I didn't my apologies. In any case, deleting works like deleting most things on the firmware: long-press the item and a context menu will pop up with the option. So for clippings, when you view the list, just long-press on it and you can delete.

As for the limit, the code has already been refactored to improve RAM which in turn allows increasing the limit from 64 to 256. It's been on my development branch for awhile. This release is taking longer because of Dictionary, Sticky/Touchscreen support, and incremental indexing. All of which are huge code changes so I want to make sure I get it right before even a pre-release.

[fokrul-hasan]

Yes, I saw your reply. I really appreciate your response. Thank you. I just posted it here again with hope that developers might want to keep it in mind on future updates

[moisessakai]

@uxjulia , thank you so much! You really help the community a lot! Thank you for being that light.

Regarding Clippings, I'm using CrossInk version 1.3.4 Tiny on my XTEINK X4.

The point about Clippings:

1. I select the Clipping (5% of the book) and continue reading.
2. When I go to the MENU and select 'View Clippings', I can see my Clippings.
3. However, when I click to 'open' CrossInk, it goes to the page where is the clipping (5%), but it forgets that I was at 10% of the book and not 5%.
   If I don't note where I was, I might get lost.

Has there been any improvement or is it cataloged? Thank you very much in advance!