Today I installed latest FNC UI Pack version 6.5.1.0 and saw you did some changes to TileList component and some other fixes and improvements to another controls.
However TileList now it's a tremendous backward from the previous FNC UI Pack version 6.5.0.1 wich at that time was extremely fast and agile, now looks with a lot of delays and faster clicks is not responding.
I saw another "posts" from other users and the one wich requesting you to expose "double click" on a Tile, if you think clearly the concept of Tile List is a control wich shows in a rectangles information perhaps with photo but the main idea is to respond "FAST" to one click or finger press, so honestly expose double click was not a good idea from your team.
I told Mr. Fierens my behavior in this forums will improve significantly, but right now I am exposing a very good argument in order to revoke what you did on the new FNC UI Pack version 6.5.1.0 concerning only to TileList component.
I recorded two videos in order to show you my concern.
As a TMS customer I consider that some of our needs help another TMS users for certain tasks, but sometimes we need to understand that TMS has a goal and not sold us custom components, so not all the new features we ask to you need to be valid because in my case now the FNC TileList component introduce more troubles to my endusers than happiness.
It's not my intention to cause debate and I take care the words I used to express my idea.
P.S. Remmember now I am using Delphi 12.3 with latest components
It was not the intention to break existing functionality with the introduction of the double click event.
Both should be able to co-exist without behavior changes so we applied a fix for this. The next version will contain the improvement.
Next photo was taken from Internet showing a customer using a "kiosk" in order to select items, the main purpose of TileList is to bring the user a way to select faster some product/service with just ONE click or finger press... it was not the main purpose of the Tile to use double click, please take that in consideration.
I am a TMS customer so I know your company help me with components in order to code faster my application, but with some limitations, TMS don't sold me customized components for that, if my requirements demands a custom component I must pay for that and I know TMS can do this as "external" project.
Saying that I will not mention again the idea that for this case "double" click on TileList was not a necessary event that you must include on your FNC UI Pack releases, but it's my personal opinion.
The point I need you to remark as bug on the video of my App compiled with Delphi 12.3 is concerning to the right & left arrows navigators used to move between pages, as you can see when I press quickly left or right arrows the TileList hangs up until I wait probably 1 second and then press the same arrow again. If I press slowly the left or right arrow navigators then your controls move forward or backward as expected but this behavior does not occur with Delphi 11.3, so I don't know if the new Delphi affect your control but you must to solve that because is the latest Embarcadero release.
I want to thank you for all your effort in order to solve this issues.
The basics for handling double click was already present internally for many versions, just not exposed as an event. It's not something we added from scratch but rather exposed it as a published property. In that process a simple "else" what caused the double and single clicks two to be mutually exclusive, and as I said, that was not the intention.
Yes, for a kiosk style application with a touchscreen double click doesn't make sense. However, in desktop applications without a touchscreen a single click usually means select and double click means open. A simple desktop use-case could be showing a list of files/folders in a tile arrangement with a vertical scrollbar instead of pagination.
We were able to finally track this down. Indeed it is caused by a difference between versions, so we applied an improvement that should get rid of the slow navigation behavior.
The next update will contain the changes for this.
