nas8e9 wrote: This discussion, triggered by zer0's unhappiness with adding yet another option to an already large dialog, has been very messy, particularly with regard to tweaks. I won't rehash that discussion either, but in the end the developer has to be persuaded that there is a problem to begin with.
I agree completely.
nas8e9 wrote: All feedback has been somewhat theoretical as well as generic in the sense that all powerful software grow options and with XYplorer's development pace, at an alarming rate.
Well, not all feedback has been theoretical and generic. My contributions are always intended to be pragmatic and to address the problem as efficiently and minimally as I would do myself, based on 25 years of experience and in recognition of where Don is coming from as the developer. For example, I can only see this configuration issue, if recognized as a problem, as the kind of thing that should be properly addressed once, in a way that will scale long into the future. Otherwise, don't waste time on it.
nas8e9 wrote: How to deal with this, has seen relatively little consensus.
Yes, that has been a great dilemma, again largely I think, because of our differing perspectives and motivations. We would all do ourselves and fellow forum readers, now and in the future, a great favor if we could first get consensus and formally assert what specific objectives, guidelines, invariants, etc motivate XYplorer development and why -- a sort of real time, working manifesto to the Roadmap. I won't say "should motivate" -- I'm just suggesting we all be clear on exactly what those things are at the present time, as Don sees them. And where he is uncertain, we can possibly help illuminate.
nas8e9 wrote: I hope we can agree that shipping is a feature, and thus pragmatism is called for.
Well, yes, though I wouldn't quite term it a feature, it is more of an invariant that necessarily guides and constrains everything else. But that same invariant also means that decisions on certain core elements have to be made wisely, with other principles in mind, so that deliverability in the future will not be negatively impacted by the features and cut corners implemented today.
nas8e9 wrote: Since your proposal includes searching as well, I take it you don't object to adding that to the existing functionality, but would like a different approach in addition to and underlying the current settings infrastructure.
Searching is important, yes. But a solution that does not address the entire property space is just going to be revisited again and again, I fear. That is my main point.
nas8e9 wrote: Don doesn't see more than marginal return on that, especially when compared to the functionality he still plans to add.
And frankly, I think he's right. Despite my participation on the issue thus far, configuration really isn't a major concern for me, relative to other things. I am more interested in how this kind of issue is addressed, then the issue itself.
nas8e9 wrote: On a personal note, it's always a pity to see new users raving about XYplorer and its developer, only for them to discover that both have limits, and then sometimes slide towards ranting. This is still the same software you tried and liked enough to buy, with the same amazing developer at the helm. It's just that nothing and no one is unlimited or, well, perfect.
Indeed, it is easy to get too caught up precisely because there is this great open channel to the product and its creator. And because sometimes, we have way too much time on our hands. ;-)
Running on Windows 10 Pro 64-bit quad-core ASUS G752-VY notebook with 64 GB RAM, over 26 external USB3 drives attached via multiple powered hubs with letters and mount points, totaling 120+ TB.