Tim:
>> Hey what?!  Changing your keyboard might make something unbootable?


George N. White III:
> Or only booting to the other OS.
> 
> Many laptop users have docking stations with external  input devices.  Users 
> with RSI 
> may require  input devices that use vendor-specific drivers.  

Here I have a Mac that chucks a hissy fit if I change keyboards, but I
haven't checked if I can't boot until satisfying its needs.

I use Final Cut Pro (FCP) as a video editor, and it's use of a QWERTY
keyboard as the controller is a complete pig's breakfast of a way to do
editing.  Clearly the programmers have never used a real edit
controller.

You can get custom controllers, at enormous costs (typically costing
more than the computer).  But unless they provide some kind of driver
file for FCP, they act as a rearranged QWERTY keyboard in a special
box.  FCP will still react to you touching your real keyboard (in an
annoying way), and your editing controller can type daft things if you
catch a button.  And the OS wants to recognise *that* new keyboard by
you typing some QWERTY keys that you don't know exist, or where, on the
custom controller.

They've never cottoned onto that being a pain, that you will have both
connected simultaneously, and that you don't want one interfering with
the other (let a custom controller solely control FCP, and ignore the
typing keyboard).  Nor how it's a pain that some common hotkey does
different things depending which part of the window the mouse had
clicked on.

> At work we migrated from SGI IRIX64 to Apple because IRIX64 had Photoshop and 
>  color 
> management.  At the time, the same image looked very different using 
> Photoshop in different
> Windows boxes, but Apple systems were consistent.  The Apple systems booted 
> straight into
> macOS unless you used the keyboard to get a list of boot options where you 
> could select 
> Linux.

Colourimetry is a pain between different systems.  They all have
different ideas of how to handle gamut and monitor gamma.  Even
standard-def versus hi-def have different schemes.  And there's various
ideas about handling high-dynamic range video.

A classic simple examples is viewing photos on computers:  If you set
the display up for useful/normal black to white range for typography
(black text, white page), photos look comparatively dark (far worse
than a traditional photo album, which doesn't have photos stuck on
glowing white page).  Conversely, if you set the screen up for normal
photographic imagery, the white backrounds in webpages and your word
processor are glaringly too bright.  They've never quite understood the
problem to not show page white as 100% full intensity.

Film and TV learnt that decades ago.  Unless it's a surreal scene, a
plain white background is never burn-your-eyes-out white.

-- 
 
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
(yes, this is the output from uname for this PC when I posted)
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 

-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to