Your comments
P.S. I'll report the issue with the "are you human" image to the UserEcho team. Thanks.
10 years ago
Thanks for your feedback.
This is a duplicate of:
http://tweaker.userecho.com/topic/165205-please-al...
While I agree that it would be a great optional addition, it requires an implementation, and that requires time. I might get to that in the future, but currently that's what we have. On the other hand, you must admit that the update procedure of the tweaker is not as bad, comparing to most software which just open a link to their website, where you have to download and launch the installer (and sometimes - remove checkboxes with offers).
This is a duplicate of:
http://tweaker.userecho.com/topic/165205-please-al...
While I agree that it would be a great optional addition, it requires an implementation, and that requires time. I might get to that in the future, but currently that's what we have. On the other hand, you must admit that the update procedure of the tweaker is not as bad, comparing to most software which just open a link to their website, where you have to download and launch the installer (and sometimes - remove checkboxes with offers).
For some reason, Userecho deleted all replies to issues which have no status (like "started", "completed", etc.). Here's my reply:
I always try to minimize the number of updates, and try to push as many changes in a single release as possible.
Unfortunately, I can't always predict the situation.
For example, looking at the last three releases:
v4.2 - a comprehensive release, including new options, translations, other fixes and improvements. It could end here.
v4.2.1 - It was reported that one of the new options doesn't work correctly with the classic theme. I fixed the issue and released a fixed version the next day.
v4.2.2 - two days later, I've received a bug report about an explorer crash. In fact, this bug is quite rare and it existed since the first versions of the tweaker, but I consider an explorer crash to be a serious issue, so I updated as soon as I fixed it. The fact that it got released right after v4.2 and v4.2.1 is a mere coincidence.
The tweaker is in no way "becoming the most frequently updated app".
Now, about silent updates, I would prefer not to allow this. The same way as old bugs are fixed, new bugs may be introduced, which can cause unexpected behavior or even an explorer crash without you expecting it.
The thing that I may consider in the feature is silent updates of "stable" versions, e.g. versions which have been released for over a week. This way they're less likely to cause issues.
I always try to minimize the number of updates, and try to push as many changes in a single release as possible.
Unfortunately, I can't always predict the situation.
For example, looking at the last three releases:
v4.2 - a comprehensive release, including new options, translations, other fixes and improvements. It could end here.
v4.2.1 - It was reported that one of the new options doesn't work correctly with the classic theme. I fixed the issue and released a fixed version the next day.
v4.2.2 - two days later, I've received a bug report about an explorer crash. In fact, this bug is quite rare and it existed since the first versions of the tweaker, but I consider an explorer crash to be a serious issue, so I updated as soon as I fixed it. The fact that it got released right after v4.2 and v4.2.1 is a mere coincidence.
The tweaker is in no way "becoming the most frequently updated app".
Now, about silent updates, I would prefer not to allow this. The same way as old bugs are fixed, new bugs may be introduced, which can cause unexpected behavior or even an explorer crash without you expecting it.
The thing that I may consider in the feature is silent updates of "stable" versions, e.g. versions which have been released for over a week. This way they're less likely to cause issues.
Use the shift key ;)
Fixed in v4.4.5.
Sorry for the inconvenience.
Sorry for the inconvenience.
That's already possible with the advanced option "no_width_limit".
See help file, Advanced options -> OptionsEx for more details.
See help file, Advanced options -> OptionsEx for more details.
That's already possible with the advanced option "no_width_limit".
See help file Advanced options -> OptionsEx for more details.
See help file Advanced options -> OptionsEx for more details.
Done in v4.4.4 as an advanced option.
No, it's not possible to blacklist elements, the change is global.
That's not a bug of the tweaker. The extension probably assumes that it's tray icon is of a particular size, so it behaves differently now that it's smaller.
You might want to contact the developers of this extension, if it's still maintained. This should be an easy fix, as getting the padding is easy and is documented (using the TB_GETPADDING message). Also, the Shell_NotifyIconGetRect function might be useful.
That's not a bug of the tweaker. The extension probably assumes that it's tray icon is of a particular size, so it behaves differently now that it's smaller.
You might want to contact the developers of this extension, if it's still maintained. This should be an easy fix, as getting the padding is easy and is documented (using the TB_GETPADDING message). Also, the Shell_NotifyIconGetRect function might be useful.
Customer support service by UserEcho
