Bug 2303 - Monitoring window cannot be resized when "Status" view active
Summary: Monitoring window cannot be resized when "Status" view active
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Sami Wagiaalla
Depends on:
Blocks: 1632
  Show dependency treegraph
Reported: 2006-02-08 21:28 UTC by Rick Moseley
Modified: 2006-11-21 21:11 UTC (History)
0 users

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Rick Moseley 2006-02-08 21:28:22 UTC
When a process is clicked on making the "Status" view part of the monitoring
window active, the window cannot be "grabbed" on either side and reduced in
size.  In addition the "Maximize/Un-Maximize" button has no effect.
Comment 1 Sami Wagiaalla 2006-02-08 21:57:23 UTC
I know a the window cannot be reduced in size becuase the timestrip area
has a minimum size set on it.
Ofcourse one should still be able to "grabbed", and /increased/ in size.
I could removed the size limitations from stripchart if that is desired
and if the above discription is correct.
Comment 2 Rick Moseley 2006-02-08 22:23:31 UTC
Hmmm, I vote for taking the size limitations off of the stripchart.  The problem
I ran into was that the monitoring window opened to a size that was wider than
my screen resolution(1024x768) on my laptop.  When I tried to do a screenshot,
it chopped off the right-hand side because it was beyond the view.

I would also recommend removing the "Observer" from the "Syscall Observer"
label.  It pushes the labels out of the timeline widget window.  For example,
the thunderbird.bin process has 8 threads associated with it and only 4 "Syscall
Observer" labels are visible.
Comment 3 Sami Wagiaalla 2006-02-09 17:36:27 UTC
Restriction remvoed.