Page 2 of 2

Re: Where are the types for "find by type" defined?

Posted: 12 Jul 2010 19:00
by j_c_hallgren
admin wrote:But not 100% sure about monitor widths. People on 1024x786 will get problems then... hmm.
Well, I'm on a 1024x768 and here's how my section of this typically looks with the Catalog off to to the left:
SS - 07-12-10 @ 12-54-06001.jpg
Looking at this, what I'd suggest is:
1) Change it to "Executable's" to reduce width of that one item
2) Then reduce width of this option to eliminate white space on right
3) Extend the left side to the right to eliminate some of that unused gray space and be similar in layout to Raw View tab

That shouldn't push the "Find Now" that far out to east and yet still restore much of the prior Name field length.

Re: Where are the types for "find by type" defined?

Posted: 12 Jul 2010 19:07
by admin
j_c_hallgren wrote:
admin wrote:But not 100% sure about monitor widths. People on 1024x786 will get problems then... hmm.
Well, I'm on a 1024x768 and here's how my section of this typically looks with the Catalog off to to the left:
SS - 07-12-10 @ 12-54-06001.jpg
Looking at this, what I'd suggest is:
1) Change it to "Executable's" to reduce width of that one item
2) Then reduce width of this option to eliminate white space on right
3) Extend the left side to the right to eliminate some of that unused gray space and be similar in layout to Raw View tab

That shouldn't push the "Find Now" that far out to east and yet still restore much of the prior Name field length.
But your tree is only about 200 pixels wide -- I think that's unusually narrow. I would not draw conclusions about free space from that.

The width of the type filter box has been chosen that wide deliberately because more filters will be added with time, and who knows how wide they will be...

Re: Where are the types for "find by type" defined?

Posted: 12 Jul 2010 19:20
by j_c_hallgren
admin wrote:But your tree is only about 200 pixels wide -- I think that's unusually narrow. I would not draw conclusions about free space from that.
While I agree that I do have a somewhat narrow tree, I don't see how one could have a fully usable list any narrower than I do and thus a narrow tree is the result...and also, my size screen is getting to be rather small these days so I think with any wider screen, it would be just a typical to have that amount (and more) of gray space at right.
admin wrote:The width of the type filter box has been chosen that wide deliberately because more filters will be added with time, and who knows how wide they will be...
Ok...so could the Mode width be reduced for blank white space, and then "case/whole/fuzzy/etc" be double stacked, and type put at right of those? In order to do so and not expand IP height, the checkboxes under Location would have to move closer to bottom border and top border might also need to be tweaked down...just an idea!

Re: Where are the types for "find by type" defined?

Posted: 12 Jul 2010 19:52
by admin
j_c_hallgren wrote:
admin wrote:But your tree is only about 200 pixels wide -- I think that's unusually narrow. I would not draw conclusions about free space from that.
While I agree that I do have a somewhat narrow tree, I don't see how one could have a fully usable list any narrower than I do and thus a narrow tree is the result...and also, my size screen is getting to be rather small these days so I think with any wider screen, it would be just a typical to have that amount (and more) of gray space at right.
admin wrote:The width of the type filter box has been chosen that wide deliberately because more filters will be added with time, and who knows how wide they will be...
Ok...so could the Mode width be reduced for blank white space, and then "case/whole/fuzzy/etc" be double stacked, and type put at right of those? In order to do so and not expand IP height, the checkboxes under Location would have to move closer to bottom border and top border might also need to be tweaked down...just an idea!
I don't want to sacrifice any of the remaining white space. The Find Files tab is already pretty overcrowded.

I think making it about 100 pixels wider should work for everybody even one with a 800x600 screen (using Wide Info Panel then).

Re: Where are the types for "find by type" defined?

Posted: 13 Jul 2010 07:27
by Gandolf
You had better change the default window size now since anybody using XY "Out-of-the-box" gets the Find Files panel truncated, which is not a professional look to a first time user.

Re: Where are the types for "find by type" defined?

Posted: 13 Jul 2010 10:08
by admin
Gandolf wrote:You had better change the default window size now since anybody using XY "Out-of-the-box" gets the Find Files panel truncated, which is not a professional look to a first time user.
Yep, thanks, (it's already on my list for today). However, right now I'm tending to think that the rubber approach (within a min and max limit) might be better...

Re: Where are the types for "find by type" defined?

Posted: 13 Jul 2010 15:22
by j_c_hallgren
admin wrote:
Gandolf wrote:You had better change the default window size now since anybody using XY "Out-of-the-box" gets the Find Files panel truncated, which is not a professional look to a first time user.
Yep, thanks, (it's already on my list for today). However, right now I'm tending to think that the rubber approach (within a min and max limit) might be better...
Yes, that has the advantage of adapting to users display more effectively, so I'd vote for that style.

Re: Where are the types for "find by type" defined?

Posted: 13 Jul 2010 15:39
by admin
j_c_hallgren wrote:
admin wrote:
Gandolf wrote:You had better change the default window size now since anybody using XY "Out-of-the-box" gets the Find Files panel truncated, which is not a professional look to a first time user.
Yep, thanks, (it's already on my list for today). However, right now I'm tending to think that the rubber approach (within a min and max limit) might be better...
Yes, that has the advantage of adapting to users display more effectively, so I'd vote for that style.
Me too, but I met some technical problems when trying. So for now it will stay as it is.