Quote:
Originally Posted by lucas_LCS
I was referring your the Fcomp images.
They both have the End Folder image on the right.*
Except in this case where the TrackIDX is being used to cover space on top of the Fcomp image.**
True, no one is suggesting otherwise.
That aspect of the TrackIDX is being used to mask the area to the right of the actual Fcomp/folder button image so that when you click in that area nothing happens.***
.
|
OK maybe I am just lost here, and it happens at times. I am under alot of stress right now and a health situation, and I see I already overlooked the fact that the track number would disappear in that situation; stupid....It's
been such a long time since I used these elements this way I forgot.
Also, I could have sworn that this didn't happen with v5 and up. Guess I was
wrong. Anyway, he don't care about the tr. # disappearing on that parent track
so, yay, resolved, but what I am wondering is, because I cannot get it,
and it bugs me that I am not understanding the following:
*ok, after reviewing the posts, still a no from me because his request was
that he wanted the end cap to show up on the right side of the PARENT track
when it was compressed, obviously, this is somewhat erroneous behavior,
and he was saying all along, like, 'there is no way to make this happen with
WALTER, and like, why not??' And so that's when WT said '....' - he was like
yeah, no kidding. So I explained to him at the beginning of my long post that
the parent should not get that end(last) piece, ever because it is not the
last, but that is what he wants, and I get it, it's pseudo-sorta-correctish-like....when compressed, the parent track becomes the beginning and the end of that group of tracks. So that was the whole reason for reworking the .png's.
**ok, I don't get this one because there is no space to the right of the fcomp
image, it's .png is 18Px. how is the trackidx covering anything? I am just not understanding what....well....do you mean that the trackidx is covering the
area between the left and right side not covered by the folder/fcomp elements,
covering this space, not from visibility by the trackidxbg, but covering it
so that it cannot be clicked by a mouse? Because the trackidxbg images are nil, so they cannot really cover anything....idk, idk, idk........I am fried.
It does not matter, but it bothers me when I don't understand a concept,
because I am trying to understand everything about theming, WALTER, etc., that
I possibly can.
***ok, this one, I think, if I understand your explanation for the last entry,
is that the footprint of the trackidx is keeping the fcomp button from having a big clickable area that should NOT be clickable....If everything is in it's untouched state, before his mods, this shouln't be. I am obviously missing
something here, maybe it's brain cells.