This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 77078 - [ProfilingPoints] Confusing results view of stopwatches
Summary: [ProfilingPoints] Confusing results view of stopwatches
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks: 79229
  Show dependency tree
 
Reported: 2006-05-30 14:01 UTC by ehucka
Modified: 2007-03-23 14:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (1.65 KB, image/png)
2006-05-30 14:02 UTC, ehucka
Details
screenshot (4.00 KB, image/png)
2006-06-02 19:37 UTC, ehucka
Details
screenshot (4.34 KB, image/png)
2006-06-29 16:46 UTC, ehucka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2006-05-30 14:01:37 UTC
For example:

there are many numbers with the same values and the last number is shifted to
the left because of units name position (ms).
Values should have appropriate resolution (granularity), it should be clear
which value is assigned to which peak on the x axis. Units name can be placed
below the values.
Comment 1 ehucka 2006-05-30 14:02:18 UTC
Created attachment 30669 [details]
screenshot
Comment 2 Maros Sandor 2006-05-31 09:56:54 UTC
It seems that these values are so similar that the difference is not important.
Yes, we can use labels "1990", "1991", "1992" but I think user impact is
minimal, thus lowering priority.
The rightmost label is somewhat misplaced. How can we work around it Jirko?
Comment 3 Jiri Sedlacek 2006-05-31 10:22:46 UTC
Comment on rightmost label: The chart ensures that rightmost value won't 
interfere with axis description, but second- etc. rightmost values aren't 
checked. I would suggest to follow these 2 rules:

 1/ last (rightmost) mark should have its value displayed (in general, first 
and last mark should always have its value displayed in any chart)
 2/ use lower number of columns instead of not displaying values of some marks. 
If there is too much marks that their values doesn't fit, the chart will be 
most likely not well-readable to the user

If the above won't be enough to solve described problem, additional logic can 
be added to the chart checking interferences between displayed values.
Comment 4 ehucka 2006-06-02 19:36:27 UTC
I think it is p3.
Comment 5 ehucka 2006-06-02 19:37:10 UTC
Created attachment 30759 [details]
screenshot
Comment 6 ehucka 2006-06-29 16:45:25 UTC
Another screenshot. I think such view of results is unusable. I can see only
'1.0' second but Profiling Points windows shows 999,7 ms average.
Comment 7 ehucka 2006-06-29 16:46:14 UTC
Created attachment 31520 [details]
screenshot
Comment 8 Jiri Sedlacek 2007-03-22 14:01:19 UTC
Doesn't occur after Profiling Points reimplementation - in fact only results 
listing is currently available, no graphs. Will take into account when 
designing graphs for new Profiling Points.
Comment 9 ehucka 2007-03-23 14:37:19 UTC
verified