If you do a refactoring of a package and e.g. want to encapsulate parts of the code into functions/procedures the content view sometimes compeletely disappears due to the package being invalid.
Is there a way to preserve the structure of the package in the content tree besides just the function/proceduere that invalidates the package?
This would be a major improvement for the refacturing use case, because while you are building up a new function/procedueres the most needed feature is to jump to other code in the package tor gather parts of the code.
This could partly be achieved by bookmarks or search, but for the former you are bound to set them in advance and for the latter you need to know exactly what you are searching for. So, a smarter content tree would be very helpful.
Is there a way to preserve the structure of the package in the content tree besides just the function/proceduere that invalidates the package?
This would be a major improvement for the refacturing use case, because while you are building up a new function/procedueres the most needed feature is to jump to other code in the package tor gather parts of the code.
This could partly be achieved by bookmarks or search, but for the former you are bound to set them in advance and for the latter you need to know exactly what you are searching for. So, a smarter content tree would be very helpful.
