User canceled operation?

I think the new UI is not as good as the old one. Can I switch back to the old UI while also making it multi-column?

@nuhi

No. Instead tell me what is not good with the new UI, 2 screenshots old vs new next to each other so I can know what we're talking about.
And give a few pointers how you see the issue, that will help potentially improve the new one.
 
In other words, name one or two things that are worse so I can act on it. Maybe it's surprising but I am listening to users, it's just a bit tricky, those users need to actually say something.
 
In other words, name one or two things that are worse so I can act on it. Maybe it's surprising but I am listening to users, it's just a bit tricky, those users need to actually say something.
From the time I open this program, to the time I close it, and everything in between, it simply is nowhere near the previous interface. If it was just one thing, I would tell you what that was; but it's everything.
 
In other words, name one or two things that are worse so I can act on it. Maybe it's surprising but I am listening to users, it's just a bit tricky, those users need to actually say something.
非常感谢您的倾听。这边建议您参考使用人数比较多的软件的交互设计,因为它确确实实影响了很多人的使用习惯。
UX参考之一:1787838772015.png
还有其它细节,比如《队列》和复选框就比现在的好很多,让人一眼看得懂。有些东西不应该跟用户玩捉迷藏
 
By the look of that screenshot, we seem not to have similar tastes, let's put the UI topic aside and let me know if you see any bugs.
 
By the look of that screenshot, we seem not to have similar tastes, let's put the UI topic aside and let me know if you see any bugs.
When I use NTLite to perform customization, my computer restarts abruptly as soon as I start the process. The reason is that my computer does not have enough memory. Therefore, I would like to suggest adding an option that allows users to manually limit the number of threads when performing operations such as customization, mounting, saving, and unmounting with NTLite.
 
When I use NTLite to perform customization, my computer restarts abruptly as soon as I start the process. The reason is that my computer does not have enough memory. Therefore, I would like to suggest adding an option that allows users to manually limit the number of threads when performing operations such as customization, mounting, saving, and unmounting with NTLite.
There is an option in the ntlite.exe switches.
Edit shortcut for it to be
ntlite.exe /ThreadMax:N
(N is the number of threads)

e.g. "C:\Program Files\NTLite\NTLite.exe" /ThreadMax:3

Let me know once you see which max number it can take, how many cores you have, and how much RAM on that machine? So I can tweak the automatic algorythm.
 
There is an option in the ntlite.exe switches.
Edit shortcut for it to be
ntlite.exe /ThreadMax:N
(N is the number of threads)

e.g. "C:\Program Files\NTLite\NTLite.exe" /ThreadMax:3

Let me know once you see which max number it can take, how many cores you have, and how much RAM on that machine? So I can tweak the automatic algorythm.
I still suggest providing an option in the settings for users to manually set a limit.
 
I still suggest providing an option in the settings for users to manually set a limit.
Agreed, already done for the next one. Automatic side also needs improvements, so do let me know when you say limited, what is the core count and memory available?
 
Agreed, already done for the next one. Automatic side also needs improvements, so do let me know when you say limited, what is the core count and memory available?
Actually, I can't pinpoint the real cause of the crash. I suspect it's either insufficient memory or CPU issues — the system should either make tasks wait or kill those with lower priority. But based on past experience, it used to run stably for a year with 16 threads and 32GB of memory, whereas now it frequently crashes with 16GB. I think a limit of 3GB per thread would be more appropriate.
1787921469643.png
1787921494625.png
 
Last edited:
Back
Top