And some keep forgetting that a record function had to start somewhere. Record on, record off...then, record from x to x time etc.
If the current implantation of record functions is too complex at this stage for it to function at a basic level, with minimal data parameters , then it would fairly trivial to make a second basic one, that does just that. Or copy the current Record function, strip it down, and have the UI elements call up that record function program code when under the present "not recordable channel" scenario.
However, this is not ideal or very efficient. As it means the devs then have 2 sets of function code sets to debug and update.
Instead, Making it so that the existing record function code so that it can perform in this scenario would be most ideal. The 2 ways i thought of this being accomplished already mentioned in previous post.
I was born in the 80's, and VCR was one of the first things i took apart and fixed when it broke (or ate a tape) when i was a kid. Ours never had the flashing clock, cause i read the manual and programed it. VCR more essential than running water, dear old mom recorded flipping everything. (3 closets, a pantry, a single car garage, and a 10x10 public storage locker full of paper ream boxes full of vhs tapes, recorded in SLP (6hrs/8hrs per tape) ).
What i realize from your analogy, is that modern tech has gotten so "Smart"....it actually is quite dumb...in certain practical use cases that us older folks are used to it being plum simple.
To put it more in simple context.
What is Channels DVR?
A home media software made to watch and RECORD live tv and programs.
User can not RECORD programs on a built in auto populated channel.
Does it affect everyone: Yes, (TVE users at least)
Does everyone care: No
Should not have to do fancy custom "workarounds" to use basic functions on provided services.