DonationCoder.com Software > T-Clock

T-Clock 2010 (download)

<< < (150/171) > >>

Curt:
day number of year, but not yet day number of week

WhiteTigX:
will be added once I've added the ordinal day number (1st, 2nd, 3rd etc) which kind of requires a rewrite of internal format processing

WhiteTigX:
Hello T-Clock community ;)

I require your help but let me apologize first because I've re-read some of my own posts a while ago and I really sound like an asshole from time to time :P It's really not meant to sound like that and I'll try to be more careful about what I write to sound less aggressive and that like.
Might be related to my partially lacking English, but who knows.

Well, lets go back to my help request.
I've decided to add a question dialog regarding the update checker because it isn't really possible otherwise to prevent it from running before you had a chance to disable it if you really want to.
The goal is to have this dialog as short as possible to not be too annoying, and to prevent people from accidentally disabling update checking in case they tend to close every window that pops up..

So my current "try" looks like this:

raw textT-Clock can automatically check for updates to ensure
that you're aware of the latest bug fixes and features.
This usually requires less than one KiB of data
and won't disturb your daily work.

It is recommended to have update checking enabled.
Note that you'll have to click "Disable" to actually disable it, because it is enabled by default (which means the other two buttons and closing the dialog does the same thing)
I've chosen this layout as I think it might prevent people from accidentally disabling it by closing the dialog, hitting the right most button or clicking the left most.. (a message box usually got "OK" and "Cancel")
But I've got no real experience or psychological skills to know whether my thinking is right or not.

What do you think? And feel free to suggest a different layout or text. Or correct my current one

mouser:
I think it's nearly perfect. 

A couple of suggestions:

1. Three buttons seems like one too many.  I would suggest merging the "Keep enabled" and "OK" to one button "OK, keep enabled".
2. I'd remove the sentence "This usually requires" and change it to "No personal information or extra data is transmitted during this check." (or something to that effect).
3. You *could* also add a sentence like "You can change this option at any time from the preferences dialog".


Having said all that, i think people have become completely used to the idea of update checks, and so a pre-warning dialog like this is not strictly necessary (i don't use one in my apps); i think the important thing is having a way for user to disable it.

WhiteTigX:
1) well.. what about accidentally clicking the wrong button? I also have to include non-English people in my decisions (which might not even read anything at all)
There's redundancy right now, but it's so far intended even though it might look weird :P
Also, I'm currently unable to resize buttons because it's just a subclassed MessageBox (though I might add that if really needed)

2) Well... at least I want to know how much an update check requires... I know of a lot bad implementations that require ridiculous amounts of traffic for what they should do (though I can trim mine further down to about 32bytes excl. HTTP headers and TCP traffic)
I'm also actually not a fan of this "no personal information...." stuff... it suggests that it'll otherwise transfer this kind of information which I think is wrong. So I'll rather add a notice about what personal information I'll transfer, rather than putting a notice that I don't transfer^^ I want to live in a world that assumes everyone is good unless they say otherwise.

3) That's something I've really missed ;) Thanks. (though the message gets longer...)
Though I have to add the UI first xD Which isn't easy to squeeze in currently...
Lets assume this dialog is to be added, would a button be enough that says "configure updates" which simply displays this dialog again?
A bit easier (smaller) than check boxes:
"☑ Regularly check for updates     ☐ include beta versions"


[...]
Having said all that, i think people have become completely used to the idea of update checks, and so a pre-warning dialog like this is not strictly necessary [...]
-mouser (December 01, 2015, 07:04 PM)
--- End quote ---
I agree. But my issue is that I've decided to do an update check on first launch. Mainly to get firewall notices popped up and hopefully allowed so it won't happen eg. 5 minutes after startup, somewhere in the middle of the day or next day etc.
Yet it prevents people from disabling it before it triggers...
And the quite fast response to this feature up here showed it's still an issue.
Also, the popup notifies users before a firewall popup appears, which is good because T-Clock isn't some Internet related software and it looks a bit suspicious without a forewarning

Navigation

[0] Message Index

[#] Next page

[*] Previous page