See into S60
» Subscribe
» Favorite Links
» What is S60?
» Freeware & Trials
» S60 devices
» Hints and tips

» About this blog
» Blognotes (15)
» Bugs and Workarounds (4)
» Build tools (5)
» Carbide.c++ 1.1 (4)
» Carbide.c++ 1.2 (8)
» Carbide.c++ 1.3.x (9)
» Carbide.c++ 2.0.x (12)
» Carbide Plug-Ins (4)
» CodeWarrior (2)
» FAQ (6)
» Future directions (25)
» General (48)
» Off-topic (5)
» On-device debugging (13)
» Performance Investigator (2)
» Product features (18)
» Product releases (16)
» Screencast (14)
» Support (36)
» Tool setup (6)
» UI Designer (8)
» Usability (18)
» Work in Progress (14)
» Write-build-debug (4)
» Tommi's Reports from Wonderland
» Voice of S60
» Creating Carbide C++
» S60 Multimedia Blog
» The Convergence Zone
» Web Browser for S60 Blog
» Consumed by S60
» Java for S60
» Mobile Web Server
» Mobile Security
» See into S60
» Business2GO
» Nokia Podcasting Application Blog
» New Remote Connections View
» Terminating Multiple Processes
» Agile Tuning of the Austin Team
» Introduction to the workspace screencast
» Adding DLLs while Debugging
» September 2008
» August 2008
» July 2008
» June 2008
» May 2008
» April 2008
» March 2008
» February 2008
» August 2007
» May 2007
» April 2007
» March 2007
» February 2007
» January 2007
» December 2006
» November 2006
» October 2006
» September 2006
» August 2006
» July 2006
» June 2006
Subscribe
Links
May 06, 2008 Event secrets in PI Posted by L. Frank Turovich at 03:00 PM | Categories: Performance Investigator, Usability

So I'm sitting in a meeting today discussing how we can improve the UI for Performance Investigator (PI) in future releases. We have a lot of issues to address to improve the usability, clarity, and usefulness of the tool and are working hard to define the changes and when they can be delivered. One of the items to look at struck me by surprise. I didn't know that PI did that and I had actually documented the main feature over a year ago for Carbide 1.2 or so.

Needless to say I was a bit verklempt about the whole issue. Then I realized if I, who worked across the room from the developers didn't know of these features, it was a pretty good bet that the vast Carbide audience hadn't stumbled upon them either.

So, let's talk about them.

As everyone may know, PI provides the ability to gather data into a file using the Profiler application on a device. You then transfer the data file back to the host machine and import it into Carbide using the File > Import > Performance Investigator > Performance Investigator Data wizard. The PI data is then shown in an editor view for analysis. If the file contains button event information it appears in the Thread Load graph as red lines ending in boxes and the event name underneath.

pi_thread_load_01.png

Ok, so feature one is that even if the button event has text there is some additional info you can view. To see it, simply click the button event and a tooltip appears with additional information about the event.

pi_thread_load_02.png

If you double-click the button event, the second feature appears which is an editor dialog where you can edit the name and add a comment to the button event. Click OK to save your changes.

pi_thread_load_03.png

Needless to say I'll be adding info on these two features into the PI manual some time soon. As always, I'm left to wonder how many other 'hidden' features are lurking out there that need documentation. It's the stuff of nightmares.


Permalink |

Comments

TSETTSET

Posted by: TESTTEST | May 7, 2008 03:46 AM


Post a comment







«Back to previous page