Feature request: Change scope to module declaration so sticky scroll sticks on submodule declaration when viewing IO

[WearyExploration]

Request Description:

• Have module declaration show in the sticky scroll window when sticky scroll is enabled

Example:

• Suppose we've declared a module u_module with thousands of io pins, and that these pins were not connected with SystemVerilog's .* connection operator. We scroll down 570 some lines. The scroll window might look something like this:

|-----------------------------------------------------------|
|     .net576(net576)                                       |
|     .net577(net577)                                       |
|     .net578(net578)                                       |  
|     .net579(net579)                                       |
|     .net580(net580)                                       |
|-----------------------------------------------------------|

It would be nice, if instead, an extension could scope to the declared module when sticky scroll is enabled. The desired output would look like this:

|-----------------------------------------------------------|
| submodule_def submodule_dec                               |  <- stickied to top of scroll window of module declaration
|-----------------------------------------------------------|
|     .net577(net577)                                       |
|     .net578(net578)                                       |  <-- scroll window is still down in port connection space
|     .net579(net579)                                       |
|     .net580(net580)                                       |
|-----------------------------------------------------------|

Current behavior:

Enabling sticky scroll looks like the following:

------------------------------------------------------------|
| module top_module (                                       |  <- stickied to top of scroll window of module *definition*
|-----------------------------------------------------------|
|     .net577(net577)                                       |
|     .net578(net578)                                       |  <-- scroll window is still down in port connection space
|     .net579(net579)                                       |
|     .net580(net580)                                       |
------------------------------------------------------------|

NOTE: current behavior gives the module definition of the file which means the scope is still pointing to the top level module of the file on the first few lines and not the submodule.