Should on-Empeg soups ever show as dirty?

Currently in jEmplode 42pre3, soup playlists never appear to be dirty (even though they actually could be). However, if soups were updated, you will receive a warning that you need to sync before quitting (i.e. things actually are dirty, but it just doesn't look like it in the UI).

Does anyone have a preference? I tend to like it not appearing to be dirty. In fact, I've been considering making it so soups don't even cause the "warn on exit" to occur (basically, if you sync, they'll be fixed up, otherwise, they are ignored).

Mike

some of us need reminders...what day is it again?

If it's not too CPU-intensive, I'd like soups to be coloured when they're dirty (and perhaps also colour the empeg-car icon when config.ini is changed). It helps answer the question of "what did I change? Do I really want to sync?". Just MHO.

The CPU intensive part is the only thing I'm concerned about ... With soups you end up with a lot of playlists, and to colorize back up the tree you have to check every child for dirtiness (and "coloredness").

What about making soups "immune" to the "you need to sync" warning? That way you wouldn't even be bothered? The only time this would be _wrong_ would be if you modified tunes through Emplode then came back into jEmplode. Any other time, the actual changes that you made that caused the soup to be modified would show up as dirty (i.e. in the "normal" playlists).

In reply to:

---

What about making soups "immune" to the "you need to sync" warning? ... the actual changes that you made that caused the soup to be modified would show up as dirty (i.e. in the "normal" playlists).

---

Wouldn't this cause problems for people who have tunes not in any playlists? (I don't do this, but I'm told that one can). If such tunes were modified (e.g. by adding a "comment" tag), then would the user be able to find the changed tune?

/me thinks that "changed" would make a nice useful pseudo-tag to build a search view...

Well ... yes and no. The tune itself would appear red (since there's no difference between a "soup:" tune and an "unsoup" tune, but it wouldn't colorize back up the tree.... I'll have to do some profiling and actually see what kind of performance hit is taken...

Is it possible to turn this feature (colouring up a soup tree) on and off from the .jempegrc file\? That would keep (nearly) everyone happy...

Yeah probably so ... Maybe I'll make it so it just checks once at startup ...