Eeschema does not show information of the selected wire.

[yoneken]

When I click some wire, Eeschema should show the information ( label name etc.. ) of the wire in the bottom bar.
However, the RC does not show it.
See an attached figure.

Application: kicad
Version: (2015-09-17 BZR 6202)-product release build
wxWidgets: Version 3.0.2 (debug,UTF-8,compiler with C++ ABI 1002,GCC 4.2.1,STL containers,compatible with 2.8)
Platform: Mac OS X (Darwin 13.4.0 x86_64), 64 bit, Little endian, wxMac
Boost version: 1.54.0
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=ON
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON

Maybe, it's a new function? I don't remember the function was already implmented or not.

[Wayne Stambaugh (stambaughw)]

This is not a bug per se in that there is no message panel output function for wires. Most likely this is due to the fact that nets are only generated when the net list is generated so there would be no information to display without maintaining an net list internally which would require some pretty serous code changes to eeschema. It's something we can think about in the future.

[Chris Pavlina (pavlina-chris)]

I'd love to see this in the future. I've been considering a bit of research into the possibility of implementing net highlighting in eeschema, which would similarly require keeping track of which wires go to which nets, so perhaps the two could be implemented together. It's something that might have to be held onto until some future cleanup work in eeschema, though.

[Wayne Stambaugh (stambaughw)]

@Chris, please hold off on this. I am in the process (albeit slowly due
to the time demands of the stable release) of refactoring all of the
eeschema internals so that there is a coherent top level schematic
object that encompasses the entire design. Once this is done, there
will a be a place to maintain the net list as the schematic is modified
which will be required to implement net highlighting.

On 9/22/2015 9:51 AM, Chris Pavlina wrote:
> I'd love to see this in the future. I've been considering a bit of
> research into the possibility of implementing net highlighting in
> eeschema, which would similarly require keeping track of which wires go
> to which nets, so perhaps the two could be implemented together. It's
> something that might have to be held onto until some future cleanup work
> in eeschema, though.
>

[Jeff Young (jeyjey)]

Cool feature, Jon!