Leaderboard

Hi everyone, We are a small team of six and have been evaluating uniGUI for about a week as part of our review process, and it stands out as a strong candidate compared to other frameworks we're considering for converting a large, mature app developed over the last 15 years. We appreciate the powerful features uniGUI offers, but we do have a few concerns we hope to get some clarity on: Source Code Clarification: There seems to be some uncertainty about what exactly is included in the "Complete" edition. Specifically, we've seen mentions that the source code for "uniTools" might not be distributed. Could someone confirm if this is still the case? Documentation: Certain areas seem to lack comprehensive documentation, the Hyper Grid being one example. Are there any plans to expand these resources, or could anyone share additional examples or guidance? Roadmap for 2025: We're interested in learning more about the roadmap for 2025, as well as an overview of past milestones. Has there been any assessment of previous roadmap achievements, or is there a place where this information is available? Forum Response Times: We recently posted a question regarding an issue with TActionList.OnUpdate not being called, but haven't received any responses yet despite significant views. Is there an alternative support channel for paid subscribers or best practice for getting more timely feedback? We're excited about the potential of uniGUI and would love to hear from others who may have thoughts on these issues or have other suggestions. Any insights would be greatly appreciated! Looking forward to your feedback.

This comes up kind of often. The progress bar in Unigui doesn't behave like you are used to in Delphi, because of the fact that the server and client actually runs asynchronously. So, in order to get the result you expect you are pretty much forced to implement a multithreaded solution. I think it is well worth noting here, that this is actually the Correct way to use the progress bar even in standard VCL applications as well and not doing it this way and perhaps using tricks like Application.ProcessMessages is inherently evil. The attached project shows a very basic example of a multithreaded application which uses a worker thread to do a task that takes a while to complete (it calls sleep one hundred times). Every time the thread returns from sleep it checks for termination from the UI, updates the progress count and goes back to sleep. When the progress count has reached 100 the thread terminates automatically. The UI inspects the progress of the worker thread at regular intervals using TUniTimer. It then updates the progress bar and returns control to the user. The user can request that the thread terminates by clicking a cancel button. ProgressBarExample.zip