Community
Participate
Working Groups
This is what a scenarioto view the memory data based on the currently behaviour of Memory Browser: 1. Open Memory Browser. 2. Start a debug session 3. Select a target 4. Enter an expression in the Go To Address box and click Go What our customers want to do is: 1. Open Memory Browser 2. Start a debug session. 3. Select a target. 4. A rendering is automatically opened and jump to address that was previously viewed. 5. If a rendering for the same is removed by the users and the same target is selected again, memory browser does not need to automatically open a rendering again. The following changes can be implemented in Memory Browser: 1. Whenever users enter an expression to the Go To Address field, Memory Browser will store the expression and tne memory space id in the launch configuration. 2. Currently, Memory Browser creates a tab folder only when a valid context is selected and a tab folder for the context has not yet been created. We can add an additinal task there to open a memory rendering and jump to the address that has been stored from the previous step.
Created attachment 196603 [details] patch to open a rendering automatically
Alain I applied the patch and it works as advertised. I guess I am wondering if this is the right thing to do. What you have saves and restores the last expression/renderer selected/created. Why just the last. Had you considered saving and restoring all of them. Doing one or all is quite a change from existing behavior. I like it by the way, but again wonder if it is enough. Also I am wondering, since this is a pretty significant UI workflow change, had you considered making this a preference that the user could use to decide if they want this behavior or not. Randy
(In reply to comment #2) > Alain > I applied the patch and it works as advertised. I guess I am wondering > if this is the right thing to do. What you have saves and restores the > last expression/renderer selected/created. Why just the last. Had you > considered saving and restoring all of them. Doing one or all is quite > a change from existing behavior. I like it by the way, but again wonder > if it is enough. Also I am wondering, since this is a pretty significant > UI workflow change, had you considered making this a preference that the > user could use to decide if they want this behavior or not. > Randy Randy, Did you mean to restore all renderings that were left opened in the last session? I think this is a good approach if I didn't misundertand you. I also agree that we should let users decide whether they want this behaviour or not.
Alain yes, I meant restoring all renderers for a particular context. Whether or not you decide to do this, I think the patch should make it an option and I think you should query the CDT community ( cdt_dev ) about putting in this more significant change. For sure it needs to be a preference option. Whether or not the default is ON or OFF, should be decided by the community. Randy
Created attachment 197046 [details] patch to incorporate Randy's suggestion
Created attachment 197541 [details] patch to incorporate Randy's suggestion
