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

The annotation currently being edited is now clearly identifiable #3661

Conversation

kerryland
Copy link
Contributor

When editing annotations it's now each to tell which piece of text is related to the comment.

A couple of notes:

  • My change to EditAnnotations::StartEditAnnotations was simply because I was offended by the repetition of calls to SetColor :-)
  • EditAnnotations::SelectAnnotationInEditWindow has a new call to RepaintAsync, which smells a bit to me. There might be a better way to achieve the same goal, but I don't know it.
  • I apologise if this pull request includes some stupid merges from master, my git skills are a bit rusty

This change fixes another issue I raised in issue 3638

image

@kerryland
Copy link
Contributor Author

This fixes #1996

@kerryland
Copy link
Contributor Author

I've realised, after reading #3590, that this change makes deleting an annotation annoying, so I will fix that first.

@kerryland kerryland closed this Sep 16, 2023
@@ -1535,26 +1548,40 @@ Annotation* EngineMupdfCreateAnnotation(EngineBase* engine, AnnotationType typ,

pdf_update_annot(ctx, annot);
auto res = MakeAnnotationPdf(epdf, annot, pageNo);

std::optional <PdfColor> col;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't use std:: if we can avoid it. It causes terrible bloat of executables.

Set to ColorUnset instead.

@kerryland kerryland deleted the fix-3638-highlight-current-annotation branch September 16, 2023 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants