Radio: Create new UI for remote useable radio #1437
Conversation
ZenBre4ker
added
status/waiting
|
We should add some sort of indication that the radio supports this kind of stuff, right now no one can figure that out I think |
ZenBre4ker
force-pushed
the
remote_triggerable
branch
from
bb659f3 to
c71a1cb
Compare
ZenBre4ker
force-pushed
the
remote_trigger_radio
branch
from
7289aac to
ee1dd37
Compare
ZenBre4ker
force-pushed
the
remote_triggerable
branch
2 times, most recently
from
f77b943 to
1f90813
Compare
ZenBre4ker
force-pushed
the
remote_trigger_radio
branch
from
c3222f2 to
1354356
Compare
ZenBre4ker
force-pushed
the
remote_trigger_radio
branch
from
1354356 to
d8476d7
Compare
|
This is ready as well now. I added a general name for the translation string, because I could imagine to use this generally for all entities Use / UseOverride / ClientUse and RemoteUse. Normally UI descriptions should be kept shortm if you want more information it should be standing somewhere else. So I dont want to add "this {radio_name}" or "remotely" as this is kinda self explaining if you just try to press E. |
ZenBre4ker
removed
the
status/waiting
|
Could you please put the keybind in the subtitle instead of a "random" description line? Right now it gets kind of lost and it is also not in-line with the other targetID implementations: https://github.com/TTT-2/TTT2/blob/master/lua/ttt2/libraries/targetid.lua#L621-L628 Edit: Ah well, there is no subtitle for marker vision. I can add it in a PR this week and then you can use it. Would that be ok? |
|
I get what you mean, but you could also improve it yourself when its implemented. |
Co-authored-by: Tim Goll <github@timgoll.de>
Co-authored-by: Histalek <16392835+Histalek@users.noreply.github.com>
After testing #1437 I notices that it feels really weird to not have any kind of feedback when interacting with entities. When picking up entities, there already is a sound, but not when opening UIs. Therefore I added `sound.ConditionalPlay` that plays a sound if the sound type is enabled in the settings. I also extended this to body search and UI buttons. See this demo video: https://www.youtube.com/watch?v=c6ixkuFSYfw Note: I also pulled in the changes from #1351 and added them to the same system. They are disabled by default. Menu to disable sounds by type:  --------- Co-authored-by: EntranceJew <EntranceJew@gmail.com>
This is a followup to #1437 where this was initially missed. I've also removed the duplicated `SWEP.EquipMenuData`.
This is a followup to #1437 where this was initially missed. I've also removed the duplicated `SWEP.EquipMenuData`.
This is a followup to #1437 where this was initially missed. I've also removed the duplicated `SWEP.EquipMenuData`.
This is a followup to #1437 where this was initially missed. I've also removed the duplicated `SWEP.EquipMenuData`.
This is a followup to #1437 where this was initially missed. I've also removed the duplicated `SWEP.EquipMenuData`.
Before this you had to navigate to the shop tabs to use it, which is really unintuitive and currently blocks our idea to do a new shop.
Now you can use the 'Use'-Key from any distance on the focussed radio marker
and get the following new UI, which triggers the sounds in the same way as before
This will be waiting for the approval of the remote trigger feature in #1436