[GH-ISSUE #33] As a library

kerem commented

2026-02-26 08:45:02 +03:00

Owner

Originally created by @JKSnd on GitHub (Nov 4, 2016).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/33

Originally assigned to: @NickeManarin on GitHub.

This could be a very powerful support tool if it could be included in a software project.

The idea as a workflow:

A user of my software is having an issue
They hit the "Report Issue" button
Behind the scenes, screentogif.dll starts recording the application's window.
The user is instructed to reproduce the issue if possible
Once the user has recreated the problem, they indicate that they're done
The application stops the recording
The application acquires the generated gif
Logs are packaged up with the gif, it is all sent back to our support department as a tidy little ticket.

If such a library as screentogif.dll existed, and supported steps 3,4,6, and 7 then that would be stellar.

I'm sure we could pull the source and just do it in-house as a one-off, but everybody benefits when packages make it up to NuGet.

Thanks for considering!

Originally created by @JKSnd on GitHub (Nov 4, 2016). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/33 Originally assigned to: @NickeManarin on GitHub. This could be a very powerful support tool if it could be included in a software project. The idea as a workflow: 1. A user of my software is having an issue 2. They hit the "Report Issue" button 3. Behind the scenes, screentogif.dll starts recording the application's window. 4. The user is instructed to reproduce the issue if possible 5. Once the user has recreated the problem, they indicate that they're done 6. The application stops the recording 7. The application acquires the generated gif 8. Logs are packaged up with the gif, it is all sent back to our support department as a tidy little ticket. If such a library as screentogif.dll existed, and supported steps 3,4,6, and 7 then that would be stellar. I'm sure we could pull the source and just do it in-house as a one-off, but everybody benefits when packages make it up to NuGet. Thanks for considering!

kerem added the

🔷Enhancement

future feature

labels

2026-02-26 08:45:02 +03:00

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@NickeManarin commented on GitHub (Nov 4, 2016):

This is an awesome idea!

@NickeManarin commented on GitHub (Nov 4, 2016): This is an awesome idea!

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@BobVul commented on GitHub (Jan 30, 2017):

If you do, please consider also dual-licensing with an additional licence, because MS-PL might not be GPL-compatible. Depending on how permissive you want to get, perhaps (one of) the LGPL or MIT licences.

@BobVul commented on GitHub (Jan 30, 2017): If you do, please consider also dual-licensing with an additional licence, because [MS-PL might not be GPL-compatible](https://softwareengineering.stackexchange.com/questions/191123/why-isnt-the-microsoft-public-license-compatible-with-the-gpl). Depending on how permissive you want to get, perhaps (one of) the LGPL or MIT licences.

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@NickeManarin commented on GitHub (Jan 31, 2017):

Yes, I want to change the license of this project, but I have to read everything carefully.

@NickeManarin commented on GitHub (Jan 31, 2017): Yes, I want to change the license of this project, but I have to read everything carefully.

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@BobVul commented on GitHub (Jan 31, 2017):

Thanks! :)

I suggested dual-licensing instead of changing the existing one so existing users won't have to reevaluate the licence. Might make things easier.

@BobVul commented on GitHub (Jan 31, 2017): Thanks! :) I suggested dual-licensing instead of changing the existing one so existing users won't have to reevaluate the licence. Might make things easier.

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@NickeManarin commented on GitHub (Jan 31, 2017):

Oh, I was thinking about switching to a license very close to the current one with the same reason in mind. :)

@NickeManarin commented on GitHub (Jan 31, 2017): Oh, I was thinking about switching to a license very close to the current one with the same reason in mind. :)

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@JKSnd commented on GitHub (Feb 8, 2017):

That would be awesome! Especially since I'm not a pro at interpreting 3d of the Ms-Pl. What constitutes a compatible license? I'm not sure.

I'm a big fan of the MIT, for what it's worth.

Dual-licensing as a temporary way to smoothly transition may be a good option.

@JKSnd commented on GitHub (Feb 8, 2017): That would be awesome! Especially since I'm not a pro at interpreting 3d of the Ms-Pl. What constitutes a compatible license? I'm not sure. I'm a big fan of the MIT, for what it's worth. Dual-licensing as a temporary way to smoothly transition may be a good option.

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@vatterspun commented on GitHub (May 31, 2017):

... please consider also dual-licensing with an additional licence, because MS-PL might not be GPL-compatible.

To clarify, according to the GNU.ORG site, MS-PL is incompatible with the GPL.

Yes, I want to change the license of this project, but I have to read everything carefully

Sounds great. Whatever you choose, make sure it includes something about patents (something the MS-Pl definitely gets right). So for example, Apache 2.0 does so while BSD and MIT do not.

I'm a fan of the GPL for a few reasons, but maybe the major one is that I like the idea of programs and their code living beyond their creators, where many "permissive" licenses can be taken in a fully closed source direction, as most notably happened in the case of Apple's Darwin and the Microsoft Windows networking stack.

ScreenToGif is one of the most active and interesting I've seen in a long time (and I've played with a LOT of animated GIF editors), so please don't let anyone influence you to select anything that will diminish your interest.

@vatterspun commented on GitHub (May 31, 2017): > ... please consider also dual-licensing with an additional licence, because MS-PL might not be GPL-compatible. To clarify, according to the GNU.ORG site, MS-PL is [incompatible with the GPL](https://www.gnu.org/licenses/license-list.html#ms-pl). > Yes, I want to change the license of this project, but I have to read everything carefully Sounds great. Whatever you choose, make sure it includes something about patents (something the MS-Pl definitely gets right). So for example, Apache 2.0 does so while BSD and MIT do not. I'm a fan of the GPL for a few reasons, but maybe the major one is that I like the idea of programs and their code living beyond their creators, where many "permissive" licenses can be taken in a fully closed source direction, as most notably happened in the case of Apple's Darwin and the Microsoft Windows networking stack. ScreenToGif is one of the most active and interesting I've seen in a long time (and I've played with a LOT of animated GIF editors), so please don't let anyone influence you to select anything that will diminish your interest.

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@vatterspun commented on GitHub (Jan 13, 2019):

This is far from a critical topic, but I did want to point out that - as Microsoft purchased Github - you can look at the top (pinned) projects from Microsoft and their open license right here on the site: https://github.com/microsoft/

I couldn't find any data on how popular the MS-Pl license is overall, but it's interesting that even Microsoft doesn't seem to be using it's own license. Maybe there's a reason for that?

@vatterspun commented on GitHub (Jan 13, 2019): This is far from a critical topic, but I did want to point out that - as Microsoft purchased Github - you can look at the top (pinned) projects from Microsoft and their open license right here on the site: https://github.com/microsoft/ I couldn't find any data on how popular the MS-Pl license is overall, but it's interesting that even Microsoft doesn't seem to be using it's own license. Maybe there's a reason for that?

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@konard commented on GitHub (Oct 30, 2019):

There is another way to approach the same issue. We can record everything at the background for the last hour or two, and when something unexpected happens, we can save a recording. This way we save user time, and there is no need to reproduce anything. This approach is similar to how the black box works.

@konard commented on GitHub (Oct 30, 2019): There is another way to approach the same issue. We can record everything at the background for the last hour or two, and when something unexpected happens, we can save a recording. This way we save user time, and there is no need to reproduce anything. This approach is similar to how the [black box](https://en.wikipedia.org/wiki/Flight_recorder) works.

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@NickeManarin commented on GitHub (Aug 8, 2020):

@Konard With the next version, there will be available a new capture mode, which only captures a frame when something actually changes within the capture region.

With this new feature, it will be possible to make long captures using less disk space.

@NickeManarin commented on GitHub (Aug 8, 2020): @Konard With the next version, there will be available a new capture mode, which only captures a frame when something actually changes within the capture region. With this new feature, it will be possible to make long captures using less disk space.

kerem commented

2026-02-26 08:45:03 +03:00

Author

Owner

@sharwell commented on GitHub (Nov 22, 2023):

Hi @NickeManarin,

We are very interested in using a library version of ScreenToGif as part of our product integration test pipeline. It sounds like you may be interested in having this feature be part of ScreenToGif itself, so I wanted to discuss this possibility with you and determine if it would be best to try and create the library separately (derived from this project) or work on it here as a new product feature for everyone. Looking forward to hearing your preference.

As a side note, IANAL but I have assisted other projects in license migration. If you are interested in migrating to another license, I'd be happy to explain the process we followed.

Thanks,
Sam

@sharwell commented on GitHub (Nov 22, 2023): Hi @NickeManarin, We are very interested in using a library version of ScreenToGif as part of our product integration test pipeline. It sounds like you may be interested in having this feature be part of ScreenToGif itself, so I wanted to discuss this possibility with you and determine if it would be best to try and create the library separately (derived from this project) or work on it here as a new product feature for everyone. Looking forward to hearing your preference. As a side note, [IANAL](https://en.wikipedia.org/wiki/IANAL) but I have assisted other projects in license migration. If you are interested in migrating to another license, I'd be happy to explain the process we followed. Thanks, Sam

kerem referenced this issue

2026-02-26 09:30:42 +03:00

[GH-ISSUE #292] Publish the app to Microsoft Store #241

kerem referenced this issue

2026-03-01 18:45:12 +03:00

[GH-ISSUE #33] As a library #1400

kerem referenced this issue

2026-03-01 18:46:53 +03:00

[GH-ISSUE #292] Publish the app to Microsoft Store #1610

Rows
Columns

[GH-ISSUE #33] As a library #33