Skip to content
This repository has been archived by the owner on Jan 7, 2019. It is now read-only.

Feature Request: Embedded Screenshot Watermark #98

Open
wayneoutthere opened this issue Sep 7, 2018 · 3 comments
Open

Feature Request: Embedded Screenshot Watermark #98

wayneoutthere opened this issue Sep 7, 2018 · 3 comments

Comments

@wayneoutthere
Copy link

Sorry . I suck at github but hopefully you can edit my post to make it a proper 'feature request'.
One thing that has always been both humourous and painful is when you take a screenshot in UT and try to share it. The problem is that in the gallery, where you choose the screenshot you want to share, as soon as the top camera-app editor disappears, it looks like you are using your 'regular phone' because the screenshot occupies the entire screen right to the edge. So often I think the camera app gallery has closed because the screenshot looks like my regular activity.

My 'idea' is that you could turn on a feature in the camera app itself that when you do a hard button screenshot, that it automatically embeds a watermark of the date/time onto the screenshot (not your regular photos) that is fully visible even with the camera-app editor toolbar disappears, maybe on an extreme right edge running vertically.

perhaps something like this
UT-FP2-XENIAL-YYMMDD-HH-MM-SS

Try this file in both 'event' view in gallery and in full individual view on your UT device to see my idea

ut_calc_w_ss_watermark

Thanks!

@wayneoutthere
Copy link
Author

EDIT: I was thinking we could have two levels of this if the idea is liked by others:

  1. what I posted above which contains zero private data and
  2. developer/bug reporting embed mode which includes device info into the embed watermark

@dark-eye
Copy link
Collaborator

dark-eye commented Sep 7, 2018

@wayneoutthere I`m not sure if this issue should be in the camera app, i think the screenshot feature is more of a core mechanic. We can transfer the datetime stamp to the screenshot logic assuming it uses c++/QT :).

@Flohack74 any idea where should this issue be? If you can point me at the code i might be able to implement it

@Flohack74
Copy link
Member

@dark-eye No idea ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants