This isn't a trick question, it's really kinda bizarre, actually. These are two different buttons on the same skin. Code A, when executed, does exactly what it's supposed to and leaves the passive name showing, even upon refreshing the skin. Code B, on the other hand, does what it's supposed to except upon refreshing the skin, and then the name disappears until the next time it is moused over, whereupon the passive name re-appears and it goes back to working properly and stays there until the next refresh. For the life of me, I can't tell them apart. Worse, If I copy and paste A over B, then B starts to behave like A, which is what I want. What am I not seeing? Is there another part of the meter that's being called in one and not the other? If so, how do I tell them apart?
Last edited by balala on September 14th, 2021, 1:52 pm, edited 1 time in total.
Reason:Please use <code> tags whenever are posting code snippets. It's the </> button.
Ack! How about get rid of all the million year old obsolete commands, like !Execute, !Rainmeter..., etc. Aside from that, there's a space in the case B MouseOverAction code, after the first bang. Maybe it's that?
SilverAzide wrote: ↑September 14th, 2021, 12:56 am
Ack! How about get rid of all the million year old obsolete commands, like !Execute, !Rainmeter..., etc. Aside from that, there's a space in the case B MouseOverAction code, after the first bang. Maybe it's that?
Active Colors wrote: ↑September 14th, 2021, 6:59 am
Not sure, but, the space?
ED771525-7E15-4292-80E9-727F0439F688.jpeg
The code I posted, does not have the space.
Anyway, I am not positive, but the space might actually interrupt bang logic, as I 'might' have had to debug the same thing for me in the not so distant past.
sl23 wrote: ↑September 14th, 2021, 9:42 am
Spaces between commands makes no difference, least not in any of my skins. I use that to be able to read the code a little better.
Of course practically there are personal preferences regarding comfortable coding or readable formatting, but is just technically better to stick to the normal, recommended, and standardized way of writing a Rainmeter code. Rainmeter will try to ignore irrelevant characters or spaces between the bangs, but no one can ever guarantee that the diferent ways will work 100% of the times. There was recently a similar issue with the space https://forum.rainmeter.net/viewtopic.php?f=14&t=36882. I suggested checking that just to be sure and eliminate anything like that before going too deep into the woods like requesting to send the whole skin and analyzing it.
OrionsHope wrote: ↑September 13th, 2021, 11:59 pm
This isn't a trick question, it's really kinda bizarre, actually. These are two different buttons on the same skin. Code A, when executed, does exactly what it's supposed to and leaves the passive name showing, even upon refreshing the skin. Code B, on the other hand, does what it's supposed to except upon refreshing the skin, and then the name disappears until the next time it is moused over, whereupon the passive name re-appears and it goes back to working properly and stays there until the next refresh. For the life of me, I can't tell them apart. Worse, If I copy and paste A over B, then B starts to behave like A, which is what I want. What am I not seeing? Is there another part of the meter that's being called in one and not the other? If so, how do I tell them apart?
Best would be to post the whole code, not just these two meters, otherwise it is extremely hard to tell something meaningful.
Beside this, note a few things:
SilverAzide wrote: ↑September 14th, 2021, 12:56 am
How about get rid of all the million year old obsolete commands, like !Execute, !Rainmeter..., etc.
This makes no difference. Doesn't mater if those deprecated bangs / prefixes are used or not, Rainmeter will deal. It's recommended not to use them, this is another story, but if used, they create no problems.
SilverAzide wrote: ↑September 14th, 2021, 12:56 am
Aside from that, there's a space in the case B MouseOverAction code, after the first bang.
This doesn't create problems either. The only bang which had such problems was !Delay, but it has been fixed, I think. However using no such useless characters (like spaces at the beginning of lines) is an extremely good idea, makes the code easier to be read, but if used, they cause no trouble at all.
So, my only idea is that I'd like to see the whole code of the incriminated skin.
Interesting... Actually, I didn't write the code and I did suspect it wasn't needed but it seemed to be working so I left it. So just the !Hide, !Show, etc. is needed or is there a better a better way yet? I'm betting some of this is in the docs so I'll post again if I need further clarification.
