Messages

31

Questions / Removing old custom tags

« on: May 29, 2016, 07:44:22 PM »

Is there a way to remove the value of custom tags that were "Saved to MusicBee database only"? I want to replace one of my old custom tags with a new one. I've renamed the tag, but all values from the old tag still remain.

EDIT: I was also wondering if there is a way to move custom tags that are saved in the MB database only. So if I have Custom Tag #11, (Save to MB database only) and I want to switch it to Custom Tag #16. Is that possible (without losing all the tag info)?

32

Bug Reports / Re: Some odd behavior in the tag editor can lead to changes not being saved.

« on: May 29, 2016, 04:24:34 PM »

There's a wishlist request somewhere for an apply or save & continue type button for the tag editor.  In the meantime, there is a Hotkey for Save & Next.

Thanks, that's what I needed. A button would be nice, but this helps a lot. Oddly, the save and close buttons are separate in the docked editor, but not the floating.

33

Bug Reports / Re: Some odd behavior in the tag editor can lead to changes not being saved.

« on: May 29, 2016, 04:09:22 PM »

Well it looks like you got rid of that save dialogue all together.

I'm not sure what you mean. It's still there. Try editing a tag for multi tracks and select another track, then you will get the dialog.

How is this done? If a tag is edited, the editor automatically closes. If you select another track without saving, the changes are lost. It can be done in the docked editor, but no dialogue is displayed. Selecting new tracks simply brings the editor to the main (tags) page/tab.

34

Bug Reports / Re: Some odd behavior in the tag editor can lead to changes not being saved.

« on: May 28, 2016, 10:02:09 PM »

Well it looks like you got rid of that save dialogue all together. This means that you must press the save button after making any changes, and before selecting any new tracks to edit. That's fine except that unlike all the other menus, the (floating)tag editor has no separate Save and Close buttons. So the whole editor closes every time you press Save. This means that when you're editing a lot of tags, you have to re-open the editor again every time after saving. The docked editor does have a separate Save button(icon), but I much prefer the floating panel to work with. Is there some reason they should function differently? I realize this isn't a bug, just thought I'd mention it.

In either panel (float or docked), when you select new tracks to edit, the menu automatically returns to the main (Tags) page. This makes it significantly less convenient if you're specifically working on editing custom tags/artwork/lyrics/settings. It just seems to me that when the editor is open and tracks are selected, the editor should stay on the same tags page/tab. Anyway, I apologize for the pain in-the-ass rant. I'm done bugging you. (for now, lol)

35

Bug Reports / Re: Some odd behavior in the tag editor can lead to changes not being saved.

« on: May 28, 2016, 05:40:06 PM »

In the first part of the .gif, I click to the side of the input box, which checks the box and highlights the text. After selecting a track in the main panel, the save option appears, I select yes, and you can see the info is saved.

In the second part of the .gif, I click directly on the checkbox, which highlights the text but does not tick the box. Still, the save option appears. However after selecting "Yes" to save, you can see the info does not get saved.

http://i.imgur.com/6uOQcB4.gifv

The problem here is that the save menu appears when it shouldn't. If the checkbox isn't selected, the save menu should not appear, because selecting "yes" does not result in the tag info being saved.

36

Bug Reports / Some odd behavior in the tag editor can lead to changes not being saved.

« on: May 28, 2016, 04:05:57 PM »

I was wondering why some of my changes weren't being saved and this is what I found:

When editing multiple tags in the editor, there is a checkbox displayed next to each input box. After editing a tag, the checkbox is automatically ticked if you click anywhere in the editor panel, and the changed text appears highlighted as an indicator. Oddly, if you click on the actual checkbox (or the tag description/heading beside it), the newly edited info becomes highlighted, but the checkbox IS NOT ticked. The box must be clicked twice if the checkmark is to appear.

The reason this is important is because if you select a different track/album in the main panel without checking the box, MB will not save the changes. If the box is ticked, MB will display a message "One or more values have been amended - do you want to save the changes?" Selecting "Yes" ensures the changes are saved. HOWEVER... this message is also displayed with the above described scenario in which the changed text appears highlighted but the box is not checked. So even after selecting "Yes", none of the changes are actually saved.

Seeing the message and selecting "Yes" results in the assumption your changes have in fact been saved when they have not been.

37

General Discussions / Re: GUI changes for v3.0

« on: May 26, 2016, 05:29:18 AM »

That's the thing. These albums do not have track numbers. Each track consists of a title in the format [yyyy-mm-dd. Title]. They are a large collection of lectures and seminars which I have stored with my audiobooks.

there used to be handling for that but it seems somewhere in v2.5 it was made ineffective. Its addressed for the next v3 patch update

All good now, thanks.

38

General Discussions / Re: GUI changes for v3.0

« on: May 25, 2016, 03:51:36 PM »

That's the thing. These albums do not have track numbers. Each track consists of a title in the format [yyyy-mm-dd. Title]. They are a large collection of lectures and seminars which I have stored with my audiobooks.

I suppose I could assign disc/track numbers to all of them if I have to. Is there a reason why the artwork views would ignore the custom selected sort options? I don't understand why the behavior would be different for those views.

39

General Discussions / Re: GUI changes for v3.0

« on: May 25, 2016, 02:07:51 PM »

I'll bring this up once more, as a previous attempt didn't get a reply, so I'm unsure if this is intentional or not.

When enabling the album collapse/expand feature for Album&Tracks view, the sub-headings dissappear. This is especially unfortunate when viewing audiobooks, which often contain 50+ tracks. Usually audiobooks are divided into multiple discs, which are nice to have displayed as a sub-heading. Having them all expanded requires a lot of scrolling.

40

General Discussions / Re: GUI changes for v3.0

« on: May 25, 2016, 01:43:26 PM »

I can't get the tracks to sort by title in Album Covers or Artists views. Everything sorts fine in the other views. So when I sort using Album>Title, the titles are all in a random order. Using the same sort setting with Tracks or A&T views, the titles are all sorted alphabetically within the albums. I don't know if there could be a setting that's causing this?

 The only way I can get the titles to organize correctly is to:
-select 'Show the tracks at the bottom of the main panel'
-click on 'Title' in the fields header

However if I re-select viewing tracks in the expanded panel, the titles are immediately displayed randomly again.

41

TheaterMode / Re: Multi-Line Tag Values

« on: May 25, 2016, 06:43:12 AM »

Using this example:
<element name="#Lyrics" type="Lyrics" xAnchor="#Box.10" x="0" yAnchor="#Box.10" y="0" widthDock="x:#Box.90" width="0"  heightDock="y:#Box.50" height="0" font="Segoe UI" style="Regular" size="10" fg="200,200,200" ></element>

Let's say you want to place the following Comment element directly beneath it:
<element  type="Field" id="Comment" xAnchor="#Box.10" x="0" yAnchor="#Lyrics.Bottom" y="0" widthDock="x:#Box.90" width="0" heightDock="y:#Box.90" height="0" font="Segoe UI" style="Regular" size="10" fg="200,200,200" ></element>

The Comment will always be anchored to to "y:#Box.50", regardless of how many lines are used by the Lyrics element. This is what I've been trying (and failing) to explain. How can we get an element which is directly below a multi-line element, to move either up or down depending on how many lines are above it. So whether a lyric has 4 lines or 400 lines, the element below will still be directly underneath.

If this still isn't clear I can provide a pic.

42

TheaterMode / Re: Multi-Line Tag Values

« on: May 25, 2016, 02:24:20 AM »

To be clear, even with Lyrics and ArtistInfo, the bottom anchor does not change/adapt to the number of lines needed.

43

TheaterMode / Re: Multi-Line Tag Values

« on: May 25, 2016, 01:40:46 AM »

+1 (if I understand you correctly).

44

TheaterMode / Re: Multi-Line Tag Values

« on: May 24, 2016, 09:01:36 PM »

Thanks. Yes, I read that thread. The problem was that I was writing multiline, not multiLine.

Unfortunately it seems the element's height is not adaptable to content, but rather fixed with a scrollbar.  The options are to use a smaller panel and scroll through longer tags, or create a large panel and waste precious space when larger tags aren't present.

EDIT: I solved the anchoring issue, again a dumb error.

45

TheaterMode / Multi-Line Tag Values

« on: May 24, 2016, 03:42:01 PM »

- Is it possible to display a multi-line tag, such as Comment? Currently I can only get a single line to display and it gets cut off.
- If it is possible, can the element below it be anchored to it in such a way that the element's location on the y-axis is dependant on the number of lines used (in the multi-line tag)?