Object IO labels missing

#1

Although I report this for 1.0.10, it's not a 1.0.10 specific issue as I've seen in in previous versions:

For some objects the input and/or output labels are missing. I've seen this in factory objects and my own objects. Trying to change the names doesn't help. At one point when using 1.0.9, I discussed this with a mate, and did some refreshing, and suddenly the label appeared - I can't remember exactly what I did or which object it was, but it wasn't a real change to anything structural or syntactical IIRC. There may be some intentional mechanism at play that I'm not aware of, but I'd like those labels to show.

Examples:
axoloti-factory/objects/lfo/square => "out" label missing
axoloti-contrib/objects/drj/osc/phasor_pm_pr_b => "out" label missing

Axoloti version : 1.0.10-0-gf8ed51d-dirty build time : 10/05/2016 20:18:33 CEST, Link to firmware CRC 3DB31696
Platform: Win 7 64 bit

#2

Labels are not shown if there is only one inlet or outlet. always been this way. afaik
or do you mean something else?

I guess the reasoning is usually if there is only one, its often 'obvious' what the inlet/outlet does, so less screen clutter? I personally think this is true for many objects (e.g. +1) but perhaps not necessary clear with others?

personal preference though, I guess some will prefer this way, and others will prefer to see labels.

#3

Aha! I should have spotted the pattern... :telescope:

My personal preference is as stated that labels are always shown, I don't think it's obvious in all cases and for me it aids the readability of a patch - the module title is a bit "cramped" and low contrast, and with the small text size and not optimal eyesight, the labels would make it more clear what's going on. Perhaps it's worth considering adding a noLabel attribute to inlets and outlets, which would be true by default?

#4

I hadn't realised that rule, either.
I'd say maybe a compromise; hide by default if only one inlet/outlet, but allow them to be shown if you (object developer) want.

In terms of screen-space, the worst offender is that objects stretch horizontally to accommodate the full name and path from their library. I think this really should be fixed. There's no good reason for an object to take up several times as much space, just because it has a long name, or is inside a couple of sub-directories. Just the name, and a rollover tooltip to display the full path is all that's needed, I think.

a|x