Re: μGiffer [graphic capture utility]
Posted: Fri Jun 07, 2019 6:15 am
0.9.7 is out, fixes a GDI handle leak in capture phase.
TPFC Forums
https://www.portablefreeware.com/forums/
https://www.portablefreeware.com/forums/viewtopic.php?t=24534
I'm not a big fan of keeping config data alongside with the binaries, but I can make the program check for .ini in the exe folder first (and if -c is not specified).∙ If 'uGiffer.ini' is present in the program folder, it isn't automatically picked up. I know it should be passed as a parameter with '-c' command option but it would make uGiffer simpler to operate if it did automatically.
Supporting relative paths is a road to (support) hell, because different people would assume different things about what it is relative to. The lack of support for relative paths is by design, basically. Supporting envvars is not a bad idea, but they will need to expand into an absolute path. Let me see what I can do.∙ Even using the '-c' option, μGiffer doesn't seem to support relative paths and throws an error if you try to use them (see below). If changing that, please add environment variables as well.
Strongly disagree.∙ IMHO, even some sort of minimal command toolbar -- with buttons like Go, Pause and Stop -- would be a great usability improvement.
Can you elaborate?∙ I'm getting some artifacts with video capture that I don't know how to get rid of. Truth be told, I get them in most other giffing tools and μGiffer is the best in this particular aspect.
The whole GH "page" is just a temporary hack. I've been meaning to put together a proper page, but haven't had time for that yet.∙ The Github 'readme.txt' should be part of the download, which should also be packaged into some kind of archive format. Naked executable downloads from the Internet tend not to fare too well.
You know better than we do about supporting a very popular software project, but keeping everything in the same folder is at the heart of portability. If you're running something off a removable drive, the absolute path is going to change and/or die as soon as you have another drive plugged in. This happened to me earlier today as I had to rename my backup process to point to E:\ after an attached SD card pushed my drive out of the D:\ slot. Relative paths in this way require less work/configuration. Storing these configuration changes to the local folder works similarly.
vacherin wrote: ↑I'm not a big fan of keeping config data alongside with the binaries, but I can make the program check for .ini in the exe folder first (and if -c is not specified).
vacherin wrote: ↑Supporting relative paths is a road to (support) hell, because different people would assume different things about what it is relative to. The lack of support for relative paths is by design, basically. Supporting envvars is not a bad idea, but they will need to expand into an absolute path. Let me see what I can do.
vacherin wrote: ↑Strongly disagree.
It is meant for rather specific type of use and it's trivial to learn how to use it that way. Aim, press F1, press F1 (or Esc), done. Once you know this, there's no need for a toolbar. It will be just an embellishment.
If you have a use case where a toolbar is a must, please describe it.
vacherin wrote: ↑Can you elaborate?∙ I'm getting some artifacts with video capture that I don't know how to get rid of. Truth be told, I get them in most other giffing tools and μGiffer is the best in this particular aspect.
vacherin wrote: ↑The whole GH "page" is just a temporary hack. I've been meaning to put together a proper page, but haven't had time for that yet.
Nice! I've seen so many screen recorders at this point it's almost reassuring that someone can still just keep upping the ante.__philippe wrote: ↑Sat Sep 11, 2021 3:50 am uGiffer v0.9.13.0 (link date 28-APR-21) handy right-click "User Manual" ...