Closed KaktusXY closed 1 month ago
I view this more like a statically defined thing... similar to the lables... not everything has to have a coding interface... the stuff that is reasonable... right now i cant see a reason on why someone would want to change the text of it programmatically... as its text usually is defined by what machines are connected to the power network... and that doesnt change programmatically...
I came here also for this request, hopefully you decide to implement it despite not seeing a need for it yourself.
right now i cant see a reason on why someone would want to change the text of it programmatically... as its text usually is defined by what machines are connected to the power network... and that doesnt change programmatically...
At least getSignText() would be useful to me. Then it's a lot easier to differentiate power switches from one another. (I know I can give it a nickname with the network manager, but there seems to be an issue with blueprints when I do that...and the computer and power switches are in a blueprint. On startup, I could figure out which switch is which using the text of the switch.
right now i cant see a reason on why someone would want to change the text of it programmatically... as its text usually is defined by what machines are connected to the power network... and that doesnt change programmatically...
At least getSignText() would be useful to me. Then it's a lot easier to differentiate power switches from one another. (I know I can give it a nickname with the network manager, but there seems to be an issue with blueprints when I do that...and the computer and power switches are in a blueprint. On startup, I could figure out which switch is which using the text of the switch.
Can you elaborate on "an issue with blueprints"? Especially since the latest update brought blueprint parameters.
@OHB
Well, perhaps it's worth trying again. I had a blueprint and used the network scanner tool to set nicknames for things. I saved the blueprint, cleared, and loaded it back into blueprint designer and it crashed. It seemed to happen only when nicknames were set. I assumed, perhaps incorrectly, that the nicknames weren't persisting correctly because network items placed in a blueprint all have a UUID of 00000000000000000000000000. When I place the blueprint, I need a way of knowing which switch is which and without nicknames or access to the display name, I'm using coordinates and math to identify each device based on its position relative to each other. :)
But, if you have guidance on a better approach, I'm all ears! Should assigning nicknames to devices in a blueprint work? Should I try that again?
BTW, this mod is life, thanks so much. Can't wait to share my finished blueprints!
I can not reproduce this issue... I have tried with both parametric and non-parametric nick-names and it does not crash. I both saved and loaded blueprints... The 000... UUID is normal, that is how it should be in a blueprint. All placed network adapters should have that. My HyperNetNodes have 20 components with nick-names set, they load and place just fine? O.o
edit. Maybe create a new ticket for this and attach logs?
Closing due to inactivity
Describe the feature Ability to access and modify the "SIGN MODULE" of the Power Switch (turn it on/off & set/get name/text)
With e.g.