Effacer les filtres
Effacer les filtres

Performance of uitable() within a uifigure() compared to the performance within a figure()

16 vues (au cours des 30 derniers jours)
Currently I am trying to figure out why the performance of uitable() within a uifigure() is so bad, that it is not useable at all. I hope somebody can direct me in direction here.
Basically I just have a uitable() within a uifigure() and fill the table with a 2000x100 mat of numbers. The uitable becomes unuseable. If you scroll it lags like hell until it is all rendered again. If you select a cell it also lags until the cell selection is shown.
If you create a uitable() within a figure() and fill it with the same amount of data there are no problems at all. It is super responsive as it should be.
Here are two coding examples for a uitable() in a uifigure() and a uitable() in a figure().
Please let me know if I am missing anything here because the new uifigure() approach seems to be unuseable.
%% uifigure() test
% this table will lag while scrolling and clicking cells
% Create and stack magic data
data = magic(100);
data = repmat(data, 20, 1);
% create figure
f = uifigure('Name', 'Test');
% create a 1x1 layout
g = uigridlayout(f);
g.RowHeight = {'1x'};
g.ColumnWidth = {'1x'};
% create table
dataTable = uitable(g);
% add data to table
dataTable.Data = data;
%% figure() test
% this table can be used without any lag
% Create and stack magic data
data = magic(100);
data = repmat(data, 20, 1);
% create figure
f = figure('Name', 'Test');
% create table
dataTable = uitable(f);
% add data to table
dataTable.Data = data;
  8 commentaires
Bruno Luong
Bruno Luong le 23 Jan 2023
Modifié(e) : Bruno Luong le 23 Jan 2023
The performance issue is related to HG2 engine and technology behind it. It manifests in various forms since it appears in R2015, TMW improves it but it won't catch the HG1 anytime soon. It won't be solved in the next release IMO. Either it's acceptable for you either you would stay with the old system, like me.
What I find intestering and somewhat puzzeling in your question is that the container uifigure matters, and not really the uitable itself.
Thomas Kötter
Thomas Kötter le 23 Jan 2023
I understand it like this (but I am not a professional in this topic):
figure() and uifigure() are working on a completly different framework underneath. If you use uitable() it automatically detects the type of figure/uifigure. If you use figure() as top parent it will spawn the oldschool, fast, reliable table. If you used uifigure() as top parent the new fancy but slow table will be created. The command is the same but it checks its top parent and does something totally different depending on that.
But I think you guys know way more about this than I do :) Thanks for the help.
Now we know that we can postpone our switch from figure() to uifigure() for quite some time. We maintain and develop a plattform which hosts several tools and has a pretty fancy gui. If we switch now this would not work at all since everything is way too slow with the new system.

Connectez-vous pour commenter.

Réponses (1)

Shuba Nandini
Shuba Nandini le 31 Mar 2023
I understand that you are facing problem with “uifigure” function, but this is a known issue, and my colleagues are already working on this and it might get fixed in the future release.
I hope this helps!


En savoir plus sur Develop uifigure-Based Apps dans Help Center et File Exchange




Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by