-
Notifications
You must be signed in to change notification settings - Fork 428
Resize unattended video if zoom factor >1 #1205
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
Conversation
|
@vadosnaprimer I am sorry that you have to resort to personal attacks. As a third-party contributor, my job is to propose changes to the repository. Then it is the job of the core contributors to review whether that change is valid and will not cause issues with other use-cases. My PR was pulled and merged without question or comment. If you expect all of your third-party contributors to know your codebase by heart, I don't see anyone wanting to be insulted for trying to better the community and software. |
|
how do you know he wasn't talking to me? |
|
I assumed that because the comment was on my commit with no additional tags to any other person, it would be relating to me. I apologize for any trouble I caused and I won't be causing any more. |
|
you're too sensitive. I caused the trouble by merging the commit. |
|
@Vilsol apologies accepted. Sorry but it wasn't possible to react in a better way (see here why). You're probably entirely new to coding, in which case it's better to just make an issue and ask something. The option you want is 2x window size + capture OSD enabled (make sure to disable all the actual HUD you don't want). This will result in a dump at whatever the size of the client area is. |
|
LOL, downvoted for telling how to do the scaling, what a petty flashmob. How about posting any sensible arguments instead? |
This sort of language is directly in violation of the GitHub Terms of Service:
Perhaps it would be wise for you to consider re-reading them – I believe it would be totally within my rights to report you for such behaviour and attitude should you continue. This sort of toxic behaviour, as described by @Vilsol, is disappointing to see on the issue tracker of a reasonably popular piece of software. Perhaps it is why there is a disproportionate number of issues to pull requests on this repository – 196 to 6 (~33:1) at the time of writing – significantly higher than most popular repositories marko has 105-6 (~18:1) and angular has 2230-367 (~6:1).
A simple check of his GitHub page is enough to confirm that he is not new to it at all – his first commits on GitHub were in December, 2013. Perhaps you could make at least some effort to confirm your opinions before judging others. While it is good that you gave the settings required to perform the scaling in the end, you could have closed the PR with that message. Perhaps consider ensuring your community managers (those with the power to merge) are up-to-date with knowledge of the codebase, or move them to only be reviewing PRs, so that you have the final say on matters. Wrongly-merged PRs should not at all be portrayed as the fault of the PR creator(s). |
|
Wow, he wasn't kidding about the flashmob. Now we've attracted a visiting lecturer. |
@nickrobson please link me to the actual definitions of those terms that you used when deciding that anything I said matches them. Or will I be reported for asking that too? |
You should be able to find sufficient definitions in your English dictionary of choice. 🙂 |
Make it possible to resize the video even in unattended mode.