-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Improvement to the pin tool #954
Comments
This sounds like a great idea.
|
1: I had some touchscreen laptops in the past; at least on Windows a long press will be automatically interpreted as right click. 2: That looks too heavy to me. We are not a full-featured IDE with tip-of-the-day window on startup... |
Okay lets start working on just the menu part and for the tip of the day stuff we can discuss on #887 |
I myself didn't know that double click works on pinned image. About tip of the day, I agree that might be over-doing it, but I can also see some merits in it. The main question is how heavy would it get it we implement that in the welcome screen? if there is a dedicated box to show two lines of text randomly chosen from a pool. |
About the advanced features of Pin tools:
|
@ZetaoYang I have flameshot-git (r576.f34def6-1 AUR) installed and none of the things you mentioned worked:
|
I mean new features that flameshot can add in the future. |
@ZetaoYang 😅 seems I got too excited too early |
I and others from #554 want a way to remove border. It is implemented in #622 but we did not find a good way so far to introduce such setting except adding a separate option in the app settings. Preferably without the need to set it manually for each pin every time. It is not possible to add it in the side panel via a tool-specific widget like for Text because pin activates immediately. And using the global thickness value is not ideal too because then we would need to adjust it all the time when choosing other tools. |
I just realized that you cannot pin the image if the "close after capture" is on. Reported it as a [logical] bug in #964 |
What about having a command like |
@pauloo27 Two points here:
|
I just discovered this whole feature by reading this github issue section, even though I use flameshot on a daily basis since a couple of years haha. 🤣
I see several possibilities :
|
@pauloo27 @mmahmoudian A corollary of this is proposed over at #1100, in a way that I feel is more productive than exposing the pin tool specifically. |
#1100 probably can't allow #954 (comment) because it would probably need to have the titlebar in order to be movable while having editing tools, so it would still need to have some kind of pin mode (remove titlebar and tools). Also saving + re-openning file is less convenient than just clicking the Pin tool. |
@AlexP11223 Funny, I was just writing up a border-removal proposal in a seperate issue. Thanks for your contribution! I'm now realizing this might have been a communication issue, though. I didn't mean for my comment here to be part of #622 (comment), I was just trying to say that it would effectively deliver what @pauloo27 was describing in a way that might alleviate @mmahmoudian's concern that we'd be reducing flameshot to an image viewer. NGL, it was kinda a weird decision to roll #622's discussion in here, since the challenges there are specific to that PR, and don't appear directly related to the issue topic, which seems to be more about improving the pin tool's docs and expanding flameshot's capabilities after an image has been pinned. |
I use this tool to make "diffs" of screenshots by placing one side of the other, and often end up with multiple flameshot windows open. If it was possible to group all screenshots taken in a single window, grouped by tabs (like a browser), this would be ideal to avoid the accumulation of multiple windows of the same program |
@fabianski7 For your case, for the time being I can also suggest having CopyQ to store all your screenshots and then putting them in any order you want in something line LibreDraw or LibreImpress. |
I use pin eveyday, awesome tool. Anyone finds rotation useful? How about rotation while holding... ctrl? Wheel: Zooming. Ctrl+Wheel: Rotation. |
I think #1565 provides an opportunity for a definitive solution, by virtue of the windowed capture mode implemented there. Let me describe it with a scenario:
When #1565 is merged, I think implementing this will be a piece of cake. |
Summary of the threadHere I have summarized the current state of the ideas in this issue, and have added my personal opinion about some of them. Some sentences are slightly modified to fit in this summary. OPAs @toofar kindly pointed out, the #2519 have addressed most part of the initial feature request of this issue. The second part (documentation) can now be addressed partly using the website we have, and hopefully, partly with the "tip of the day" + "welcome screen". Other ideas that was suggested along the way@ZetaoYang
Perhaps the second one is slightly out of context of a screenshot software, and also there are many good minimalistic image viewers (sxiv, imv, pqiv, feh, ...)
Same as above
Even a keybinding can be added to trigger the "what is this" (my suggestion: ?
|
Add a method to allow editing a pinned screenshot by initiating a new screenshot over top of the pinned image, and then closing the old pinned image on success. This adds a new context menu to pinned screenshots. When selected the PinWidget will call the daemon to do the work. Thus this functionality only works when flameshot is running in daemon mode. The context menu options don't show up when not running in daemon mode (I don't know why they don't show up, other ones like the rotate and opacity ones also don't show up). This is not the ideal method of doing this, it doesn't actually edit the screenshot at all. I call it the "bait and switch" method of editing. The only previous attempt that I've soon to do this got caught up in dealing with screens with different DPI (pull/1565). While it would be amazing to be able to limit the whole "grab" region to be less than a screen, or even just one screen, I think this method of editing a pin in the full desktop cature mode is a step forward. It sure is for my workflow anyhow. I'm not familiar with c++ or this codebase so if there looks to be anything weird in this PR it's probably due to ignorance. I'm calling FlameshotDaemon from PinWidget, I'm not sure if I should be doing that or trying to access the Flameshot singleton directly, I just copied off of another tool which called `FlameshotDaemon::copyToClipboard()`. I'm not sure if doing `.geometry() - .layout()->contentsMargins()` is the correct way to get the image geometry, I was guided by what attributes I could see in GammaRay while inspecting a running flameshot. The method of disconnecting from the signals from within the lambdas is from here: https://stackoverflow.com/questions/14828678/disconnecting-lambda-functions-in-qt5 I contemplated calling the method in Flameshot "replacePin" or "captureFromPin" or something more technically accurate. But I figured the signature could stay a bit optimistic and if people would like the behaviour to be firmed up to match the goal in the future that could be done. Eg add functionality to the CaptureWidget to make it so you can't modify the capture region, change the grab region to be less than the whole desktop etc. Known issues: * you can move/resize the selection region, eg not just edit a pin but create a completely different one of a different region of the screen Relates to: flameshot-org#954
Add a method to allow editing a pinned screenshot by initiating a new screenshot over top of the pinned image, and then closing the old pinned image on success. This adds a new context menu to pinned screenshots. When selected the PinWidget will call the daemon to do the work. Thus this functionality only works when flameshot is running in daemon mode. The context menu options don't show up when not running in daemon mode (I don't know why they don't show up, other ones like the rotate and opacity ones also don't show up). This is not the ideal method of doing this, it doesn't actually edit the screenshot at all. I call it the "bait and switch" method of editing. The only previous attempt that I've soon to do this got caught up in dealing with screens with different DPI (pull/1565). While it would be amazing to be able to limit the whole "grab" region to be less than a screen, or even just one screen, I think this method of editing a pin in the full desktop cature mode is a step forward. It sure is for my workflow anyhow. I'm not familiar with c++ or this codebase so if there looks to be anything weird in this PR it's probably due to ignorance. I'm calling FlameshotDaemon from PinWidget, I'm not sure if I should be doing that or trying to access the Flameshot singleton directly, I just copied off of another tool which called `FlameshotDaemon::copyToClipboard()`. I'm not sure if doing `.geometry() - .layout()->contentsMargins()` is the correct way to get the image geometry, I was guided by what attributes I could see in GammaRay while inspecting a running flameshot. The method of disconnecting from the signals from within the lambdas is from here: https://stackoverflow.com/questions/14828678/disconnecting-lambda-functions-in-qt5 I contemplated calling the method in Flameshot "replacePin" or "captureFromPin" or something more technically accurate. But I figured the signature could stay a bit optimistic and if people would like the behaviour to be firmed up to match the goal in the future that could be done. Eg add functionality to the CaptureWidget to make it so you can't modify the capture region, change the grab region to be less than the whole desktop etc. Known issues: * you can move/resize the selection region, eg not just edit a pin but create a completely different one of a different region of the screen Relates to: flameshot-org#954
Add a method to allow editing a pinned screenshot by initiating a new screenshot over top of the pinned image, and then closing the old pinned image on success. This adds a new context menu to pinned screenshots. When selected the PinWidget will call the daemon to do the work. Thus this functionality only works when flameshot is running in daemon mode. The context menu options don't show up when not running in daemon mode (I don't know why they don't show up, other ones like the rotate and opacity ones also don't show up). This is not the ideal method of doing this, it doesn't actually edit the screenshot at all. I call it the "bait and switch" method of editing. The only previous attempt that I've soon to do this got caught up in dealing with screens with different DPI (pull/1565). While it would be amazing to be able to limit the whole "grab" region to be less than a screen, or even just one screen, I think this method of editing a pin in the full desktop cature mode is a step forward. It sure is for my workflow anyhow. I'm not familiar with c++ or this codebase so if there looks to be anything weird in this PR it's probably due to ignorance. I'm calling FlameshotDaemon from PinWidget, I'm not sure if I should be doing that or trying to access the Flameshot singleton directly, I just copied off of another tool which called `FlameshotDaemon::copyToClipboard()`. I'm not sure if doing `.geometry() - .layout()->contentsMargins()` is the correct way to get the image geometry, I was guided by what attributes I could see in GammaRay while inspecting a running flameshot. The method of disconnecting from the signals from within the lambdas is from here: https://stackoverflow.com/questions/14828678/disconnecting-lambda-functions-in-qt5 I contemplated calling the method in Flameshot "replacePin" or "captureFromPin" or something more technically accurate. But I figured the signature could stay a bit optimistic and if people would like the behaviour to be firmed up to match the goal in the future that could be done. Eg add functionality to the CaptureWidget to make it so you can't modify the capture region, change the grab region to be less than the whole desktop etc. Known issues: * you can move/resize the selection region, eg not just edit a pin but create a completely different one of a different region of the screen Relates to: flameshot-org#954
Update
|
Currently flameshot provides a simple implementation of image pinning. However, this implementation is quite simple. Once the image is pinned, it floats at the top of the desktop and can be dragged around, but that's basically everything. In order to close this pinned image, one will have to use the "Esc" key or double click on the image. Otherwise the only possible way is to close from the window list. This is not friendly to tablet users who have limited access to the keyboard.
I think the following improvements can be made:
The text was updated successfully, but these errors were encountered: