TC 10 x64 Interface slowdown in dark mode

[ghisler(Author)]

I want to start the next public beta test this spring.
If the described problem affects you, you could just use the 32-bit version which doesn't have this problem.

[Horst.Epp]

This is an example why I like the beta testing in XYplorer and Everything more than TCs way.
Why not providing beta versions in shorter cycles with small amount of changes ?
This gives users fast corrections of known problems.
No one is forced to install such betas tests in between
but for many users it will be a benefit.

[nsp]

This is an example why I like the beta testing in XYplorer and Everything more than TCs way.
Why not providing beta versions in shorter cycles with small amount of changes ?
This gives users fast corrections of known problems.
No one is forced to install such betas tests in between
but for many users it will be a benefit.

I Agree that it is a bit frustrating to wait for an already corrected issue. TC do not provide intermediate version on the flow... I consider that the reference implementation is still the 32bit version. I personally do not have issues with this, but it is hard to convince mates that with default 64bit OS it still exists a benefit to use 32 application.

[ghisler(Author)]

This is an example why I like the beta testing in XYplorer and Everything more than TCs way.

I have considered this, but for me the downsides are too high:
1. Many people use beta versions and never update to final versions, so these beta versions need to have a very high quality standard to not get a bad reputation. Work in progress versions are not good enough for every day work.
2. Beta versions are seen as unfinished - many people wait for the release of a final version before buying. Sales are lower during beta tests, and increase considerably after a final release. Doing a perpetual beta test would have a negative impact.
3. During a beta test I get a lot of feedback, via forum and e-mails, so I have far less time to do actual development work.

[hi5]

1 & 2 are perhaps remedied by not making them publicly available but only to registered users. By having small incremental updates, errors should be caught relatively soon, so rather than having to fix 100s of items "at once" during a public beta, there should be fewer fixes during the actual public beta which I assume will still be a thing after a certain point in time of the development so it might all even out. Just my 2cts.

Edit: forgot to add, make the beta's available for say 60 days before they stop working - that prevents them from being used for prolonged periods, I have some software programs that work that way, you can sign up for the betas and they are valid for X days before you need to upgrade to a new beta.

[ghisler(Author)]

make the beta's available for say 60 days before they stop working

That would be a case where the legitimate users have worse conditions that those of patched/cracked versions, with the check disabled...

[hi5]

The idea is of course: people have to sign up for the "quick beta" releases, you only accept registered users, when they do, they will have to accept that they will need to update frequently (if they don't want/can't: their choice, they will have to wait for the next official release).

From my own experience with other software I referred too, I find that I report bugs, they get fixed quickly, so I update quickly - at some point there is an official beta (like the current TC beta), and then the final version.

And then I sign up for the new beta program again

I can understand that it entails additional work and code (adding time limits etc) so don't feel compelled to do it, but in my personal experience it works well and I think it could do too for TC.

[nsp]

make the beta's available for say 60 days before they stop working

That would be a case where the legitimate users have worse conditions that those of patched/cracked versions, with the check disabled...

I already have some software where the beta/alfa version have time bomb (date based) and this not an issue as they are regularly updated and never stop working if you update on the flow.

For a quick/security fix the correction should not be applied only to the current development branch but understood as a fix on the current release. You provide a diff mechanism to only patch totalcmd64.exe and/or other.. Specially when 32bit and 64bit versions differs you can even calculate hashes to legitimate non cracked version.

[Hacker]

Just as an offtopic note, this is the first release in a long time that wasn't followed by an xx.01 update after release.

Roman

[JOUBE]

I prefer the way ghisler(author) handles it.

Please don't release many betas publicly, which will then be buggy... or in expiration mode...

It is right: please put work into development instead.

JO"I understand that some enthusiasts are curious about new things and paw their hooves. But these are only a few regulas here. Everyone else prefers a stable finished version"UBE

[Horst.Epp]

I prefer the way ghisler(author) handles it.

Please don't release many betas publicly, which will then be buggy... or in expiration mode...

It is right: please put work into development instead.

JO"I understand that some enthusiasts are curious about new things and paw their hooves. But these are only a few regulas here. Everyone else prefers a stable finished version"UBE

Sorry but then you will for example never use the power of Everything search tool.
If Christian would make more betas you would not be forced to install them
so what is the problem for you ?

[ghisler(Author)]

This should be fixed in TC 10.5 beta, please test it!

[ghisler(Author)]

Could someone test this, please?

[Horst.Epp]

No slowdown here in Dark mode.

[ghisler(Author)]

Great, thanks!

Moderator message

Moved to fixed bugs