toehead2001 / aeroshot Goto Github PK

From a usability perspective, I feel the fix for issue #15 alone warrants a new version as more and more people (well I can certainly speak for myself and I used AeroShot practically everyday) are using higher DPI settings and displays. You can decide whether the new version should be christened 1.5 or 1.4.1.

What steps will reproduce the problem?
1. Attempt screen shot via capture screenshot button or Alt+PrintScrn
2. Dialog box pops up stating 'The screenshot taken was blank, it will not be 
saved.'


What version of the product are you using? On what operating system?

AeroShot v1.3.1, Windows XP Professional (32-bit) SP3


Please provide any additional information below.

I've tried altering the various capture/output settings, but doing so does not 
fix the issue.

I have also tested the program under Windows 7 (64-bit) and under that OS works 
without issue.

Original issue reported on code.google.com by [email protected] on 17 Sep 2012 at 1:46

API Homepage: https://api.imgur.com/

They limit uploads by I.P. so using a permanent API key would be fine. They 
support both JSON and XML responses. 

Original issue reported on code.google.com by [email protected] on 9 Mar 2014 at 7:59

Please write a c++ version, not all computers have .netframework.
Thanks

Original issue reported on code.google.com by [email protected] on 3 Jun 2013 at 9:48

AeroShot 1.3.2 did not layout correctly on higher DPI, like at 120 shown below, and made it difficult to use if you needed to tweak the settings:

AeroShot Mini v1.4 continues to suffer from the same issue:

I can submit a fix that will scale the layout at 96, 120 or any other DPI:

There should be option to minimize window of AeroShot to system tray (the area 
on the taskbar).
It would be useful when somebody uses mainly Win+PrtScr to take screenshots. 
The window of AeroShot will open only after clicking on the tray icon.
Now that window is always visible on the taskbar.

(AeroShot 1.2.1,Win7 x64)

Original issue reported on code.google.com by [email protected] on 20 Nov 2011 at 8:47

AeroShot solution and project originates from VS 2010. Now that VS 2015 is out, any objections to upgrading it considering that it still supports targeting .NET Framework 2.0? This would be primarily to use C# 6. It's a small code base and tool so worth the fun. :)

What steps will reproduce the problem?
1. Install DisplayFusion Pro
2. Enable the secondary monitor taskbar
3. Take a screenshot without maximizing the window.

What is the expected output? What do you see instead?
The screenshot should only contains the active window. Right now, a portion of 
the secondary taskbar and the start menu button shows up if the window's border 
is too close to the secondary monitor. (let's say approx. 128 px)

What version of the product are you using? On what operating system?
AeroShot 1.3.2 on Microsoft Windows 7 Professional 64-bit

Please provide any additional information below.
See the screenshot attached for an example (bottom left corner)

Original issue reported on code.google.com by [email protected] on 9 Nov 2012 at 2:30

Attachments:

• [www.google.ca - Google Chrome.png](https://storage.googleapis.com/google-code-attachments/aeroshot/issue-8/comment-0/www.google.ca - Google Chrome.png)

What steps will reproduce the problem?
1. Run a program with elevated permissions, i.e. run as administrator.
2. Capture program window with AeroShot.

What is the expected output? What do you see instead?
Expected: screenshot image with transparent background.
Instead: screenshot captured with background.

What version of the product are you using? On what operating system?
AeroShot 1.3.2 on Windows 7 SP1 x64.

Please provide any additional information below.
Current workaround is to run AeroShot with elevated permissions also.

Original issue reported on code.google.com by [email protected] on 21 Sep 2013 at 5:34

Attachments:

• [系統管理員 命令提示字元 6.png](https://storage.googleapis.com/google-code-attachments/aeroshot/issue-13/comment-0/系統管理員 命令提示字元 6.png)

Pressing Alt activates the "keyboard navigation mode" in apps, which causes the dotted outline around controls to be displayed. Window Clippings uses Print Screen alone which doesn't have this problem.

Original app is significantly faster at capturing, almost instantaneous, where this one has a delay of about 3 seconds.

Would like it to be quicker

/Edit: Seems like Right Alt + PrtSc = Delay
Left Alt + PrtSc = No Delay

Would like a way to toggle that (Left = Delay, Right = No Delay)

While the Alt+PrintScrn key combination works in most cases, if you are trying 
to capture screenshot showing a window's pop-up menu, then act of pressing the 
Alt key will cause the pop-up menu to disappear.

It would be nice to be able to specify an alternate hot-key combination for 
such instances.

Original issue reported on code.google.com by [email protected] on 28 Jan 2013 at 12:01

Next two suggestions:
1. Option to place watermark on the screenshot
2. Option to change the Aero background color (like implemented in Shotty, 
http://shotty.devs-on.net , screenshot in the attachments).

Original issue reported on code.google.com by [email protected] on 30 Dec 2011 at 12:49

Attachments:

• Shotty-change-aero-background-color.png

There could be option to disable window shadow of captured window.

This feature is already implemented in other open source project called 
ZScreen: http://code.google.com/p/zscreen/

Original issue reported on code.google.com by [email protected] on 15 Dec 2011 at 4:27

Modern apps in Windows 10 (maybe Win 8 too?) cause extra entries to show up in the window list.

A couple of ideas for some additional capture modes:

PrintScrn key press - does a standard 'everything' capture, but uses the 
currently focused window for auto-naming/numbering the screenshots (making it 
easy to do bulk PrintScrn captures).

Ctrl+PrintScrn key press - does a 'parent of' capture. Captures the parent 
window of the currently selected window. This would be useful for when want to 
capturing a screenshot of a dialog, but want to show it in the context of the 
parent window.

Original issue reported on code.google.com by [email protected] on 4 Dec 2012 at 11:24

Option to toggle visibility of mouse cursor on the screenshot (when using 
Win+PrtScr) would be nice.
Now when capturing an active window with Win+PrtScr the cursor is not visible.

(AeroShot 1.2.1, Win7 x64)

Original issue reported on code.google.com by [email protected] on 18 Nov 2011 at 6:40

AeroShot should be a portable application out of the box for 3 reasons:

• Minimal impact and changes to the host system
• Settings can travel with the application, e.g. on a USB stick or even when copying between computers over a local network
• It is what you would expect (self-containment) from a simple and small tool

Currently AeroShot saves and loads settings from the registry. Deleting the executable leaves the system in an unclean state. By saving settings into a text file (INI) adjacent to the executable, the application can be rendered portable.

AeroShot should also be ready to handle the situation that the executable runs from a location (such as Program Files) where the user does not have write permissions. In that event, the settings file should be written to the user's profile.

Having settings in a text file also adds the following benefits:

• Settings can be hand-edited in a text editor
• Settings can easily be transferred between machines
• Settings can be backed up by simply making a copy of the file
• Settings can be reset by simply deleting the file
• Settings can be shared online
• Multiple settings setups can be swapped in and out by simple rename of files; alternatively the file to use can be specified over the command line

I can help with this.

Tasks:

• Loading settings from INI
• Saving settings to INI
• Migration of settings from registry to INI
• Save INI to user profile when permissions don't permit saving next to executable
• Look to load INI from user profile

It would be nice if aeroshot could somehow turn of ClearType before taking the 
screenshot.

ClearType improves quality a lot on LCDs but
a) You don't know if someone looking at your screenshot has the same ClearType 
settings, the same physical pixel order or even a LCD at all
b) The size of the screenshot increases since the text isn't actually black on 
white but the pixels have different colors and compress less.

Original issue reported on code.google.com by Eduard.Braun2 on 4 Nov 2012 at 6:44

1. Open a drop-down menu or a hidden menu with Alt (Explorer.exe, Firefox…). 
Something volatile to losing focus.
2. Try to capture window with AeroShot.
* Using the GUI makes the subject lose focus and hide before the screenshot is 
taken.
* The Alt in Alt-PrintScreen also hides my subjects.

Using AeroShot 1.3.2 on Windows 7 Home Premium.

I would like to be able to shoot these elusive targets and I suspect adding a 
option to delay the actual screenshot from the time of the 
key-press/button-click by a couple of seconds would allow it as follows:

Activate AeroShot -> Open and focus subject -> AeroShot fires

Original issue reported on code.google.com by [email protected] on 28 Nov 2012 at 1:31

It would be nice to have a copy to clipboard option for pasting into e.g. Word.

Original issue reported on code.google.com by [email protected] on 21 Sep 2011 at 2:47

I absolutely hate to bring up this discussion but I'd like to still try my luck anyway and make a plea for the case that while tabs work fine in code editors and everyone can go about their usual business & preferences, code is also read online a lot today (here via the GitHub web UI). Browsers don't accommodate preferences of tab widths and therefore tabs hinder online reading with “white noise.”

Again, I don't want this to degenerate into any sort of carnage so I'll suck it up & accept if you close this as “I don't care” or “won't fix” for now. 😄

I always use the hotkeys for capturing screenshots. That is why I made AeroShot a Tray Icon program and killed the Capture button & window list.

It's useful for some people, so I'll add it back. I really don't want the Capture button & window list in the Settings UI though. I can understand the convenience of it, but they are not settings. Here is my proposed compromise.

Text version if you need to quote something.

• Create a setting to allow the program to start with the Capture UI open. Tray Icon will always be visible regardless.
• If the program starts with the Capture UI open, we should disable the balloon message on the tray icon.
• When the Capture UI is closed, ask if the user wants to close the whole program, or just the Capture UI window. Offer to remember their choice.

@atifaziz Thoughts, concerns, suggestions?