[prev in list] [next in list] [prev in thread] [next in thread] 

List:       flightgear-devel
Subject:    Re: [Flightgear-devel] Video encoding GUI suggestions
From:       Benedikt Hallinger <beni () hallinger ! org>
Date:       2023-11-28 11:51:32
Message-ID: e8fa78e7b02d1d4296cc7f5e1a3be8e4 () hallinger ! org
[Download RAW message or body]

Well, I still think the best and simplest solution is:

1) merge the patch, so the additional menu entries go into the video 
recording dialog.
Reasoning:
  - To stop the video, its just one click more
  - Its more consistend with all the other options
  - Before starting the video, one gets again a refresher on the 
currently set encoding options and can verify, which prevents surprises
  - Currently, with opening the menu its already "ugly", so there is 
definitely more gain in decluttering than pain in the additional click

2) Add a new keybind to stop the video.
Reasoning:
  - This clearly gives the advantage to get a nice video as end result, 
because neither the "start" button press nor the stop is recorded.
    Which was one of the main concerns against moving the menu entries 
down to the dialog.
    (which also is *not* adressed properly, if we leave everthing as it 
is now)


Kind regards,
Beni


Am 2023-11-23 11:11, schrieb James Turner:
>> On 23 Nov 2023, at 09:58, Julian Smith <jules@op59.net> wrote:
>> James will probably dislike this, but the various different and
>> incompatible opinions on the Video recording UI suggest to me that
>> it
>> should be configurable by the user.
>> 
>> In the `Video Control` dialogue, the proposed new start/stop
>> recording
>> buttons are ok for everyone i think - they don't get in the way for
>> those who don't use them.
>> 
>> But could we also allow setting/removal of start/stop key bindings,
>> and
>> allow insert/remove of Video start/stop items in the File menu? This
>> could possibly be in a separate `Video UI` dialogue.
> 
> I guess this is really my dislike: not that it's configurable, but
> that we end up with a hundred different small bits of Ui to configure
> other features. And we have no way to search / graduate / scale the
> amount of that UI based on the user experience level. So everyone is
> forced to deal with the fact we now have a ‘Video UI' dialog, even
> if they don't care about the entire feature. It's not *terrible*
> of course, but it does increase Ui clutter and workload.
> 
> And of course everyone is happy to have the extra UI for the features
> they do use, and finds the UI excessive and annoying for the features
> they don't use ;)
> 
> But, none of this actually helps your immediate problem, so I would
> guess add the UI options but please try to name it accordingly or even
> add it into an existing UI / settings dialog?  Or make it a sub-dialog
> / expandable panel on the video dialogue?
> 
> BTW, ‘video UI' is particularly bad because some people use
> ‘video' to mean ‘graphics' or ‘rendering', so at the very
> least please label everything ‘video recording' or ‘screen
> recording' I would suggest.
> 
> Kind regards,
> James
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel


_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[prev in list] [next in list] [prev in thread] [next in thread]