TallShultzy wrote: ↑July 2nd, 2020, 5:02 pm
Before I ask for help two "incidence" which took a while to solve.
1 - the "↓" came out as a hieroglyph, your encoding was set to UTF-8 mine are UCF-2 LE BOM
2 - an errant mouse click set the "click-through" to active thus rendering the slidein/out inoperative
Anyway what I wanted to ask before I extend it to the 7 day version is:
if I create a [MeterContainer2] with the same info as [MeterContainer] then replicate the current meters and the day 3 meters into this new container, is this the way to go?
Or create one for current meters and one for each other day and move them together?
1 - My encodings in skins I work on are always
UCS2-LE BOM, since I extensively use Unicode characters in all of my skins and beyond. I just checked the encoding of my local version of the code as we speak (I didn't checked it before, as everything was working fine) and it's set to UCS2-LE BOM alright, so this issue wasn't from my end, really. Not to mention that if it was, you'd have seen those hieroglyphs in the preview GIF I posted next to the code, which obviously wasn't the case. I think it has to do with how you saved the copied code from the forum in the new Notepad (not sure if it's true for Notepad++ too) text file. It's easy to overlook these details and make sure the encoding is properly set before editing the file further.
2 - Yeah, those errant mouse clicks happen for everyone once in a while, and if you're not paying attention you're left wondering why the heck stuff isn't working. Hopefully you didn't waste too much time until you identified the (otherwise, logical) problem.
Creating a ton of containers, plus current and additional meters into it is not really the way to go, especially since you can do it much easier. For example, assuming you have a place to hover to show, say, the day 2 night temperature (could be any day, day part, or field here - I just use this as an example), you only have to dynamically set the MeasureName
option in the corresponding meter accordingly, before the slide in happens, like having this in the hovered meter's options (notice the first bang below, that's everything you need, really):
Code: Select all
MouseOverAction=[!SetOption MeterForecastDay2DayTemp MeasureName "@ForecastDay2NightTemperature"][!CommandMeasure MeasureSlideInOut "Stop 2"][!CommandMeasure MeasureSlideInOut "Execute 1"]
Of course, you'd need to add additional bangs after the first one, corresponding to the meters you want to modify (basically, all the 'Forecast' meters at the end of the code) and to the measures you want to use, but as soon as you do one "set" of such bangs, it's only a matter of copy pasting the set and change the day indexes or day part names in the MouseOverAction of another meter you want to hover on and show a different day or day part.
You'd still have to decide how to approach the hovered meter topic though. You could reuse [MeterTomorrowName]
to do it (however I don't see how you can achieve this just by using a simple hover, since unlike scrolling, hovering has no means of setting an "amount" / "index" that you'd want to "slide" to), or you could create other new meters to serve as hover targets (one or two rows of smaller "bullet-like" or numbered-like meters would be suited for this, in order to not overcrowd the skin with meters and make it bigger than desired) - it's your choice. Personally, I would lean towards the latter, something like (only text used below, so it doesn't look that appealing, but you get my point) this towards the bottom of the 2nd rounded rectangle in the skin:
Code: Select all
D1 - D2 - D3 - D4 - D5 - D6 - D7
N1 - N2 - N3 - N4 - N5 - N6 - N7
Code: Select all
○ - ○ - ○ - ○ - ○ - ○ - ○
● - ● - ● - ● - ● - ● - ●
are day parts, N
are night parts. Sure the meters should be small enough to not enlarge the skin excessively, yet large enough to make good hover targets. You could even use images instead of text for them, the design is obviously open to interpretation.
Or, maybe you have a better idea that I didn't thought of, I don't know.
P.S. Sorry for the delay in responding, I was a bit busy before. I'll be busy with other stuff I postponed until now tomorrow as well, but I think I can deal with that in order to be relatively free of commitments in the afternoon and evening.