CDK/XRecord: Bug in scheduling?

[capone]

I've noticed this one in the past...it's just a wierd logic bug I think, more than an error bug.

What happens is I'll take a show, and want it to get all showings, so I tell it to get all (basic). But, if I go into "More" (I think that's the next menu), to make sure it's set not to record dupes or change the padding, it unsets the basic, and ties the recoding to the day of the week (at least, if not channel, etc). If you then go to Power to fix that, and keep your more, it sets a start/stop date and other things, undoing more of the catch-all from the basic.

Basically, what I'm running into is that it seems the different scheduling menus bring their own defualts in that "overwrite" some of the basic things, or just adds conditions that undo broader criteria you set elsewhere.

Like I said, it's not a tech bug, but I think just a logic puzzle/trap you can fall into.

[KingArgyle]

Hmmm....I'll probably have to take a look at how Jorm has those screens coded. Ideally, they should all default to a none type option, or have a check box type option to enable or disable them. If they are enabled the option can be filled in, otherwise, they don't get populated.

I haven't looked at that code before, so I'm not sure how Jorm handles this.

Capone, can you post a bug on the SourceForge site, so that we keep track of it and don't loose it.

[capone]

It may just be the XRecord interaction. Here's a breakdown of the pattern if you add one:

Add a recording using Advanced, set to "All"
Go to Scheduler, and edit it.
Go to "More" (which defualts the dupes to true, even though they do in as false)
Change something and save. Now it's set to just record today (assumeing...has same start/end date)
Go to "Power" to edit that and save. Now it has a start/end of 00:00.

What I think I get confused on is when you add something, it's set to all, and you do more/power on the spot, it doesn't inherit the starting value (it becomes channel/day/time. This part may be more what you think it would do, but not paying attention to what it does do.

Again, it's not a bug I think...just a continuity issue between the edit modes.

[KingArgyle]

Yeah, it's more of an user interface/use ability issue. It still should be checked, but probably a fairly low priority. Not sure what Jorm has going on right now. Either Ton or I can eventually take a look at it.