Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Magic_Randy]

Is there a way to change the default ‘current view’?  I find myself customizing current views making them the same as the other current views I have already customized.

[Magic_Randy]

I found somthing through a more detail search of the forum - you can use presets for this.

[MrHaugen]

Yes, you can use presets.
But you got a hell of a lot of work to do if you have changed fra MC 11 to MC 12,
and want to get rid of the irritating small image etc. on 100 playlists. That's my case.
And I want to get MY default view when creating new.

You CAN save your preffered view to Audio. But that will NOT set the default right next time you create a playlist.
Anyone got other ideas here??

[MrHaugen]

Is it not possible to change default view?!?

[AndromAK]

I've got the same problem, and  don't know how to make a default view...
I would be glad if someone know how to do this.

[MrHaugen]

Hello!?

Can someone at least confirm that this is not possible??

[wig]

I'd also like some clarification on this matter. I really dislike changing the view for each new playlist.  The process seems overly long, involving opening a second window and then loading the preset from that window.  How about loading a preset from an expanding menu in the customize current view option instead?

[Matt]

How about loading a preset from an expanding menu in the customize current view option instead?

We're considering this approach.  Would others find it useful, or is this not enough?

BTW, the difficulty with "default view" is that MC can display a lot of different types of views, and they each have different defaults. (video playlist vs music playlist vs mixed playlist vs library view, etc.)

[glynor]

I'd Really Just Like the old "Apply to this view and all child views" option back!!

Barring that, anything that would make it quicker to apply my presets to the views would be much appreciated.  I have different "column & sorting sets" for different uses (general Audio gets one type, Imports another, Video another, Top Hits another, etc, etc).   If I ever decide to add a column to one of these sets, it's a nightmare of applying presets to sometimes 10 - 20 child view schemes...

[dcwebman]

I'd Really Just Like the old "Apply to this view and all child views" option back!!

I agree with that.

[New Vermaje]

I agree that !

it was possible with MC10 or MC11, I don't remenber exactly !!!!

Jean-Marc

[slipknot]

I've been finding that my current view sometimes reverts to the default for unknown reasons.

[glynor]

it was possible with MC10 or MC11, I don't remenber exactly !!!!

Both 10 and 11 had this option.  It was removed in 11.1 for some reason that most of us don't fully understand.

[Matt]

There'll be some improvments in this area in coming builds.

Thanks for the input.

[glynor]

Thanks for listening!   

[rjm]

Yes!

Thank you, thank you, thank you.

[Magic_Randy]

Great

[New Vermaje]

Thanks, Danke, Gracie, ....

MERCI, GRAND MERCI !

Jean-Marc

[Matt]

There's a little discussion on the fire-tester's forum, but I wanted to ask here as well.

We're making it easy to say "make child views look like this view". (for playlists and library views)

However, there are two ways to do this:

1) Make new views automatically look like their parent until customized.  Saying "make child views look like this" simply removes child customization so the view looks like their parent again.

2) Make new views look like the default.  Saying "make child views look like this" would update the children.

#1 may save some people time since new playlists and view schemes would look like others without any action.

However, #2 involves less magic, meaning it may be easier to understand.

Thanks for any advice.

[Magic_Randy]

There's a little discussion on the fire-tester's forum, but I wanted to ask here as well.

We're making it easy to say "make child views look like this view". (for playlists and library views)

However, there are two ways to do this:

1) Make new views automatically look like their parent until customized.  Saying "make child views look like this" simply removes child customization so the view looks like their parent again.

2) Make new views look like the default.  Saying "make child views look like this" would update the children.

#1 may save some people time since new playlists and view schemes would look like others without any action.

However, #2 involves less magic, meaning it may be easier to understand.

Thanks for any advice.

I like the current implementation better. The productivity is higher.

I also think the current implementation is easier to understand. Others may disagree on this point, but to me it works exactly as I would expect it to work.

So I think the current implementation wins on both productivity and ease of understanding.

[slipknot]

I like the current implementation better. The productivity is higher.

I also think the current implementation is easier to understand. Others may disagree on this point, but to me it works exactly as I would expect it to work.

So I think the current implementation wins on both productivity and ease of understanding.

Currently there is no "default" view that we can set.  The current default is useless.  It's track oriented and not album oriented.

I'd sure like to be able to set a default view, like the way it was.  And to be able to propagate that view to all others if I modify it.

[New Vermaje]

Hello !

The choice "customize as the current implementation" is better and simpler ....

Thanks.

[MrHaugen]

The choice "customize as the current implementation" is better and simpler ....

Not to me...

I opt for "make child views look like this" or similar. Don't get much clearer than that.

[MrHaugen]

How is this work progressing?  Have not tested the latest builds yet.  Is something like this included yet?
Would save me a lot of work.

[Matt]

The latest builds have a way to save a view to child views and a way to save and load complete view presets.

Look in the view header menu at the top of each view. (hover your mouse over the title text in the view header to get the menu)

[park]

The current solution is great for applying presets to views which contain lots of columns (smartlists, playing now, panes view with detailed list), but is like trying to find the door in the dark when applying presets to tile views. You have absolutely no idea which columns, sorting, and thumbnail sizes are being saved and how that would affect another tile view if you were to apply it. some kind of window, like customize current view, showing you what info will be saved (and perhaps allowing you to tick/untick whole sections; such as sorting, or thumbnail size) would be great.

[MrHaugen]

Thanks ALOT! That saved me a few hours of work. Exactly what I needed!
Don't even know what a tile view is, but the management of the normal playlists and smartlists got alot simpler.

[johnnyboy]

sounds like it's too late but my vote is that all children views are automatically created to look like their parents - it makes logical sense in terms of if a view is in a parent group - its because its connected to that group (parent) so the required columns is probably going to be similar.
This also makes it easy to customise default for audio/video/images.

Applying a view to all children is too destructive in that you just wipe out EVERY child and then have to go back and customise any individuals - far more hassle.

Saving and loading presets as it sounds like has been implemented sounds awesome!

[MrHaugen]

Applying a view to all children is too destructive in that you just wipe out EVERY child and then have to go back and customise any individuals - far more hassle.

Imo that's exactly the way it should be. If you got a few playlists in a group that you don't want to change, do this: Save the layout of the few views you would keep. Set the parent group to the custom view you like, applay it to all children. And then load the special view on the few. THAT is alot less hassle I think.

Only different approach I can think of is a checkbox list/wizard for choosing all underlaying playlists of a group, that you would include or exclude in new custom layout.

[johnnyboy]

Imo that's exactly the way it should be. If you got a few playlists in a group that you don't want to change, do this: Save the layout of the few views you would keep. Set the parent group to the custom view you like, applay it to all children. And then load the special view on the few. THAT is alot less hassle I think.

Only different approach I can think of is a checkbox list/wizard for choosing all underlaying playlists of a group, that you would include or exclude in new custom layout.

Most logical all around thing is all children should have as their default VS whatever their parent is - gives the parent more meaning than just a simple folder to dump views on. Also providing an option to apply this view to all children is obviously a feature alot of people would also want to be able to do then and being able to load and save views just gives people the total power to easily copy views from anywhere to anywhere.

I'd imagine having these 3 things in place dont at all conflict with each other but just make the whole system work that much more smoothly?