fonpaolo wrote:While I was sure you know it, I prefer to not give anything for granted.

Yes, yes! And i appretiate it!
You never know, when you will realise some obvious thing, what you missed, and you took granted.

But yeah, i write in here, when i am absolutely clueless, and checked my things over and over thousand time. (even that i miss some obvious, basic things sometime ). Also i'm not a pro titled forumer here but i am working with Rainmeter more than 3 years now. I can focus really on one thing at a time to be good at, and i choose Rainmeter, but i would gladly help in here too.

rbriddickk84 wrote:i'm not a pro titled forumer here but i am working with Rainmeter more than 3 years now. I can focus really on one thing at a time to be good at, and i choose Rainmeter, but i would gladly help in here too.

I'm working on a countdown timer that starts from a date/time input by the user rather than starting from the current time.
When I enter a time string such as "10:00", I get a popup that indicates windows is attempting to open an unknown file type. But when I enter a date (mm/dd/yy) or just a number, the popup doesn't happen. Any idea what's going on?

When I enter a time string such as "10:00", I get a popup that indicates windows is attempting to open an unknown file type. But when I enter a date (mm/dd/yy) or just a number, the popup doesn't happen. Any idea what's going on?

Not exactly sure, but even if you enter a time, if you enter one with one single digit before the colon, this isn't going on, but if you're using two digits, it does.
However, there is a small mistake in the Command1 option of the [MeasureTimeInput] measure. Usually you don't have to execute what you've entered through the InputText plugin. In most cases you have to assign it / write it as a variable. Not having the whole code (because I think this isn't the whole code, probably there are some not posted parts of it), it is hard to tell what you should have to do, but probably something like: Command1=[!ShowMeter MeterTimeInput][!SetVariable SomeVariable "$UserInput$"], or Command1=[!ShowMeter MeterTimeInput][!WriteKeyValue Variables SomeVariable "$UserInput$"].
So, what's your intention with the entered value, how do you want to use it?

is there a way to, when for instance InputLimit=4 keep a dot "." after first digit (example: "2.00") so the max possible number to enter is 9.99 and in that way to prevent input of higher ones than 9.99?
Once, by mistake i entered 1111 for the skin scale instead of 1.11 and almost faced with system restore/reinstall/repair only using Windos 10 CD. Neither the safe mode,taskmgr, opening any program-document was possible. Most of the graphics went off.
So this would be a very safety useful solution.

is there a way to, when for instance InputLimit=4 keep a dot "." after first digit (example: "2.00") so the max possible number to enter is 9.99 and in that way to prevent input of higher ones than 9.99?

Probably there is not, but you can use the Clamp function to limit the value. For example if you're using a !SetVariable bang to set the entered value to a variable (Command1=[!SetVariable MyVariable "$UserInput$"]), you can limit this value as it follows: Command1=[!SetVariable MyVariable "(Clamp($UserInput$,0,10))"] (obviously you have to edit the limits of the above Clamp function to whatever you do need).