03-31-2006 07:45 AM
04-03-2006 07:08 AM
Hi Chilly Charly,
could you send me a vi and a word document example in which you deal with this kind of behavior.
Thanks a lot,
Benjamin M
NIF
04-03-2006 09:05 AM
04-03-2006 09:30 AM
04-04-2006 02:19 AM
Hi Chilly Charly,
A workaround to this bug could be to use the invoke node "Get image" to save the graph to a jpeg file. Using this invoke node the image is saved with the zoom property.
Regards,
Benjamin
04-04-2006 05:52 AM
This solution works perfectly at run time, but of course can't be used on a stopped vi. I agree that this bug is only a minor bug, and that disabling autoscale is already a simple workaround. However, it can (should ?) be regarded also as one more bug affecting graphic display... And as usual, I wonder what sort of other malfunctions this could be symptomatic of ?..
Benjamin M a écrit: ...A workaround to this bug could be to use the invoke node "Get image" to save the graph to a jpeg file. Using this invoke node the image is saved with the zoom property.
04-05-2006 02:27 AM
I think it is a safe assumption that this is a bug in the evaluation of the clipboard image at the time of the copy operation which ignores the current zoom setting. As such I would not expect this bug to have any influence outside of graphs which have been zoomed. In fact it shows us that the copy operation is not just making a screen dump of the image buffer but really evaluating the image anew and that I would consider a bonus.
@chilly charly wrote:
And as usual, I wonder what sort of other malfunctions this could be symptomatic of ?..
04-05-2006 12:04 PM
Hey ! Wait a minute ! You mean these huge black things circling around are not helicopters ?
rolfk a écrit: ...Of course there are many more other bugs in LabVIEW but to expect this bug to cause other problems in non-zoomed graphs would seem quite paranoid to me. Maybe check out for the black helicopters circling above your house...