Error adding a line to an axes
2 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
Andrew Vallejos
le 1 Déc 2017
Réponse apportée : Andrew Vallejos
le 4 Déc 2017
Hi,
I am trying to add a line to a GUI axes. The line function works from the command window, but throws an error when executing it from the GUI. The error I receive is "Vectors must be the same length." Thanks in advance!
%example of line from command window
line([10,10],[0,10],'color','black');
%example of code from GUI.m file
time = VideoObj.currentTime;
y = ylim(handles.axesGraph);
line(handles.axesGraph, [time,time], y, 'color', 'black');
2 commentaires
dpb
le 1 Déc 2017
The conclusion must be one or the other--either time isn't a scalar or y isn't a 2-vector (maybe is empty?).
Set a breakpoint in the debugger and see what isn't as expected inside the routine.
Réponse acceptée
Plus de réponses (1)
Jan
le 2 Déc 2017
Modifié(e) : Jan
le 2 Déc 2017
Use the debugger to identify the problem:
dbstop if error
Now let the code run again. If it stops at the error, examine the used variables again:
size(time)
class(time)
size(y)
class(y)
Maybe handles.axesGraph is not a single axes handle?
3 commentaires
Jan
le 4 Déc 2017
Modifié(e) : Jan
le 4 Déc 2017
What is a "numeric"? I still cannot follow your explanations. Please be so kind and copy&paste the output of:
size(time)
class(time)
size(y)
class(y)
when Matlab stops at the error. Then please post a copy of the complete error message also. If I understand it correctly, the message contains the detail, that in the command
line(handles.axesGraph, [time,time], y, 'color', 'black');
the sizes of "[time, time]" and "y" differ. If they do not differ, the problem must be somewhere else. Then execute the command in parts in the command window during the debugging:
line([time,time], y);
Does this work? If so, try:
line(handles.axesGraph, [time,time], y);
line([time,time], y, 'color', 'black');
What is required to produce the error message? Simply play with this command to find out, where the problem is. This is called "debugging" and it is more efficient than letting the members of the forum try to debug your code remotely by suggesting commands - most of all if you post a rephrased output only.
Matlab is not sensitive. You can squeeze it and punch it with wrong commands, but this will not change its mood. Matlab will remain willing to tell you as much as it knows about the problems. So use its assistance directly.
Voir également
Catégories
En savoir plus sur Graphics Performance dans Help Center et File Exchange
Produits
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!