WALTER: Help me with volume label pls

[gapalil001]

HI! i'm trying to place tcp.volume.label above tcp.volume (knobmode)
i have an issue, that the volume label won't allow to use volume knob (yes, it's knob)
i need this solution because i definitely like how it looks.



is there any way to make volume label (and pan/width labels) being ignored or "transparent" for mouse clicks?
i am not sure, but as i understand, all what it does is display values and haven't specific submenus, etc.. if that's impossible, i would move this to feature requests

[White Tie]

I believe that many have tried and failed at this before, I'm afraid, because 'front' is only a draw order control; it doesn't affect mouse interaction. Even if the only mouse interaction in question is just 'double click number to reset it'

[gapalil001]

Originally Posted by White Tie

I believe that many have tried and failed at this before, I'm afraid, because 'front' is only a draw order control; it doesn't affect mouse interaction. Even if the only mouse interaction in question is just 'double click number to reset it'

sad true

[Justin]

Coming to a +dev next cycle

[gapalil001]

Originally Posted by Justin

Coming to a +dev next cycle

Love this! thank you a lot!

[lucas_LCS]

Originally Posted by Justin

Coming to a +dev next cycle

Would it be possible to make the Pan/Width labels not clickable?
Similar to how the track IDX works.
It would be extremely helpful to be able to use them for creating backgrounds for other elements without accidentally clicking on them and changing the setting.

::

[gapalil001]

Originally Posted by lucas_LCS

Would it be possible to make the Pan/Width labels not clickable?
Similar to how the track IDX works.
It would be extremely helpful to be able to use them for creating backgrounds for other elements without accidentally clicking on them and changing the setting.

::

now labels works as previously if not placed above the sliders/knobs. i haven't huge experience as your, but (perhaps stupid question) what about yellow markers?


[edited]
i've thinking about creating feature request to add and place specific images via WALTER especially for extra backgrounds, like we have image "mybg_volpan.png"

front tcp.image.1
set tcp.image.1 "mybg_volpan.png" [666 13 69 69 1 0 1 0]

[lucas_LCS]

Originally Posted by gapalil001

now labels works as previously if not placed above the sliders/knobs. i haven't huge experience as your, but (perhaps stupid question) what about yellow markers?

Do you mean the yellow instead of Pink lines around the the border of the PNG file?
While the yellow area can be helpful, it is not flexible in both X & Y axis at the same time.
You can set it for one and not the other and the other will be flexible and vice-versa.
This leaves the flexible area in the other as part of the main or active section of the image.

I've had several instances where I need both X & Y to be flexible, but not be an active part of the image.

Originally Posted by gapalil001

i've thinking about creating feature request to add and place specific images via WALTER especially for extra backgrounds, like we have image "mybg_volpan.png"

front tcp.image.1
set tcp.image.1 "mybg_volpan.png" [666 13 69 69 1 0 1 0]

I'm guessing it won't be possible to have user defined names allowing for unlimited number of unnknown images.
I think they will need to have predifined names for the image(s) beforehand.
I suggest using more generic names, like:
custom_img01.png
custom_img02.png
custom_img03.png
or:
usr_img01.png
usr_img02.png
usr_img03.png

::

[gapalil001]

Originally Posted by lucas_LCS

I'm guessing it won't be possible to have user defined names allowing for unlimited number of unnknown images.
::

why not? we already have user defined folder(patch) names for layouts

[White Tie]

I'm fairly sure (though nothing is certain) that wouldn't happen, it has been asked before. IIRC there are major efficiencies that come from having a known and well constrained set of images that are used or ...er... something.

I would likely oppose this FR because there are things that would be nice and things that we're really missing, and I would hate for the devs patience for theming features to go on a big job for something that is 'would be nice' then we still don't have, for example, full theming and WALTER for the routing window panels.

I say this FYI, don't let me discourage you from seeing it your own way.

[lucas_LCS]

Originally Posted by gapalil001

why not? we already have user defined folder(patch) names for layouts

1. User defined folder names for layouts in WALTER was there from the beginning, it was not added later

2. It's not the same thing.
One is the path to pre-defined elements (images), the other is the elements (images) themselves.
It's "here's where the thing is" vs. "here's a thing, here's what you can do with it, here's how you can do those things with it".

::

[lucas_LCS]

Originally Posted by White Tie

I'm fairly sure (though nothing is certain) that wouldn't happen, it has been asked before. IIRC there are major efficiencies that come from having a known and well constrained set of images that are used or ...er... something.

I would likely oppose this FR because there are things that would be nice and things that we're really missing, and I would hate for the devs patience for theming features to go on a big job for something that is 'would be nice' then we still don't have, for example, full theming and WALTER for the routing window panels.

I say this FYI, don't let me discourage you from seeing it your own way.

This true, but my thought was they were able to add the recarm_norec image a while back, so maybe it's a possible to add another image without too much difficulty.

In any case, Justin seems interested in looking at making the Vol, Pan & Width label "transparent to clicks".
This alone would be very helpful.
Hopefully it will be something easy to implement.

::

[gapalil001]

Originally Posted by lucas_LCS

Would it be possible to make the Pan/Width labels not clickable?
Similar to how the track IDX works.
It would be extremely helpful to be able to use them for creating backgrounds for other elements without accidentally clicking on them and changing the setting.

::

I’ve just remember that i’d never hits double click on labels to set them default. I always hits sliders/knobs itself. I also don’t need any actions on them (exclude situations this thread was started for)

My philosophic and completely subjective opinion about all discussion here that theming is more(or maybe whole) about art, and as traditional for any art it’s completely subjective. there are things i would add or change (disturbance in my signature) but sometimes i met guys who use these to make their own piece of art. Also i had one success feature request that was cancelled because it’s broke other themes. I mean, that IMHO there is no way to make WALTER perfect for everybody

[lucas_LCS]

Originally Posted by Justin

Coming to a +dev next cycle

Didn't see in the dev, but it's in the RC:

+ Theme: hit test vol/pan/width labels [t=267524]

https://forum.cockos.com/showthread.php?t=267524

::

[gapalil001]

Originally Posted by lucas_LCS

Didn't see in the dev, but it's in the RC:

+ Theme: hit test vol/pan/width labels [t=267524]

https://forum.cockos.com/showthread.php?t=267524

::

v6.60+dev0609 - June 9 2022

[rncwalker]

It's your theme, just don't use the labels!

On my theme I do not use the labels, don't need them, I use my ears to make adjustments.


Robert

[gapalil001]

Originally Posted by rncwalker

It's your theme, just don't use the labels!
Robert

it's my theme, i just will use everything i want

[PhelixK]

Originally Posted by Justin

Coming to a +dev next cycle

This is a really nice feature (thanks for suggesting @gapalil001!)

As for the tcp volume label,
In addition to resetting to unity gain on double-click, it would be cool also to allow mouse wheel on values if/when the volume label background element is present.

I'm aware we can place the label on top of the volume knob itself and have it interactive, but this may not always be suitable for dynamic/responsive layouts. And in some cases, it may be useful to have values visible, without the knob itself.

Anyway, I much appreciate how it is now.

- and of course, it would be king to be able to enter exact values directly on the labels somehow!



.