Sorting clientstore entries

[BrettB]

Sub:

Would it be possible for NextPVR to sort the entries in the _clientstore.xml files so that the plain and the "_video" versions were next to each other and so that it was easier to find a specific entry?

Also, is the lookup case-sensitive? I notice that I have a few "duplicate" entries (e.g. KeyCode-INFO_video, KeyCode-info_video) where only the keycode case is different. I'm wondering if that is from early testing or if I really need the duplicates.

Right now, I've got sort of a bit of a jumbled mess:

Code:

<Values>
  <KeyCode-MEDIA_SKIP_FORWARD_video>{CTRL}O</KeyCode-MEDIA_SKIP_FORWARD_video>
  <KeyCode-INFO_video>{CTRL}B</KeyCode-INFO_video>
  <KeyCode-info_video>{CTRL}B</KeyCode-info_video>
  <RecordingDefaultView>ReadyAlternate</RecordingDefaultView>
  <KeyCode-U115_video></KeyCode-U115_video>
  <KeyCode-U113_video></KeyCode-U113_video>
  <KeyCode-U114_video></KeyCode-U114_video>
  <KeyCode-U113></KeyCode-U113>
  <LastChannelGroup>Favorites</LastChannelGroup>
  <SORT_READY_RECORDINGS_GROUPS>SORT_DATE_DESC</SORT_READY_RECORDINGS_GROUPS>
  <KeyCode-U114></KeyCode-U114>
  <KeyCode-U241></KeyCode-U241>
  <KeyCode-U115></KeyCode-U115>
  <KeyCode-INFO>Menu</KeyCode-INFO>
  <SORT_READY_RECORDINGS>SORT_DATE</SORT_READY_RECORDINGS>
  <KeyCode-MEDIA_SKIP_FORWARD>{CTRL}O</KeyCode-MEDIA_SKIP_FORWARD>
  <SORT_PENDING_RECORDINGS>SORT_DATE</SORT_PENDING_RECORDINGS>
  <UsingArtworkView>false</UsingArtworkView>
  <LastChannel>802</LastChannel>
  <KeyCode-dpad_up_video>{CTRL}M</KeyCode-dpad_up_video>
  <SORT_ALTERNATE_READY_RECORDINGS>SORT_A_TO_Z</SORT_ALTERNATE_READY_RECORDINGS>
  <KeyCode-info>Menu</KeyCode-info>
  <KeyCode-media_skip_forward>{CTRL}O</KeyCode-media_skip_forward>
  <KeyCode-media_skip_forward_video>{CTRL}O</KeyCode-media_skip_forward_video>
</Values>

[mvallevand]

It is case sensitive, but the KeyCodes come from the client. Lower case would be long presses (I explained that as L for both lower and long)

config.xml isn't much different, this just has odder keys. I personally wouldn't want it sorted since new keys could get lost.

Martin

[BrettB]

It is case sensitive, but the KeyCodes come from the client.  Lower case would be long presses (I explained that as L for both lower and long)

Yeah, I thought that they came from the client. But I didn't remember about lower case=long press. I was actually wondering about how to distinguish a long-press.

config.xml isn't much different, this just has odder keys.  I personally wouldn't want it sorted since new keys could get lost.

config.xml has a couple of key difference, though:
1. It has keys/values broken into sections
2. (Basically) the keys (and order) are static

Fortunately, the clientstore isn't something that one typically needs to edit beyond an initial setup and a very occasional change to how (new) keys operate.

[sub]

Until now they've been in the order they were added.

I've made a change for the next build so that it'll sort the entries whenever it adds one.

[mvallevand]

That's too bad, it means having to look at the clientstore immediately when keys are entered. I liked the old way, a new key would be at the bottom.

The issue is primarily the four states (video t/f long t/f) aren't entered at once.

Martin

[sub]

sigh....can't win.

Ok, it's back to how it was.

[sub]

I've added a <SortClientStore>false</SortClientStore> settting for the next build. You can change it to true if you'd prefer it sorted.

[mvallevand]

Thanks, Brett maybe try this if you'd like https://github.com/kodybrown/sortxml

Martin