Current Project: HUD7
| Issue ID# 260 | Let the oHUD display status-messages while restarting. | |
| Status: Abandoned | Version: 7.4.10 | Priority: 3 |
| Assigned to: | Submitted by: Miriam Himanez | Attached file: |
| Type: Feature Request |
Submitted: 14/05/2017 19:25:13 PDT |
Last Update: 19/06/2017 03:21:44 PDT |
| Description: Whenever restarted, Signature HUD and uHUD display status-messages in chat. It would be nice for the user to receive such messages when restarting the oHUD as well, so one could see, that the restart was successful afterwards. | ||
Note ID# 1207:
| User: | Lulu | Submitted: | 18/06/2017 | ||
|
Unlike the uHUD or main HUD, the oHUD restart is usually a lot quicker. When restarting, the oHUD picture will fade away and fade back if successful. I'd think this is sufficient visual feedback that the restart is successful? I could issue a chat feedback like "Your Owner HUD has successfully restarted..." but this involves more code to detect that a restart has occurred, etc. (it's not super easy). I'm just not sure it's necessary given there are 100 other more pressing things I should have done yesterday 🙂 |
|||||
Note ID# 1208:
| User: | Lulu | Submitted: | 18/06/2017 | ||
|
Updated status to Need Info from New. |
|||||
Note ID# 1210:
| User: | Miriam Himanez | Submitted: | 18/06/2017 | ||
|
Yes, it restarts way faster than Main HUD or uHUD. Of course the fading away and fading back of the oHUD picture would be sufficient visual feedback that the restart is successful but just if it's definitely impossible, that this effect could occur on a failed/incomplete restart as well. This brings me to the additional code being needed to detect a successful restart: If it's impossible, that the fading away/back could occur on a failed/incomplete restart, I conclude the code being already there and just a chat-message would be needed to append to it. To me this would look like a minor task then, which could be done by a littleness however. (Possibly I'm viewing things too simple, because of lacking the knowledge to script myself.) If it's possible instead, it would mean, that the user never can be completely sure, if the oHUD really has properly restarted or not. In this case the matter actually would look serious to me, which would vindicate a significant amount of work to clear it away. |
|||||
Note ID# 1211:
| User: | Lulu | Submitted: | 18/06/2017 | ||
|
When you see the blank away and refresh, the restart is definitely successful. The problem is, without additional coding (which bloats the memory and creates more memory problems leading to stack-heap collisions) it is actually quite difficult to distinguish between a user restart and an automatic one (where LULU bots fix the stack-heap collisions). So the cost is not just time to code and test, but memory bloat, and I'm not sure the benefit justifies the cost, since by blanking out and coming back, it is 100% restarted. |
|||||
Note ID# 1213:
| User: | Miriam Himanez | Submitted: | 18/06/2017 | ||
| If a restart was always successful when the picture has faded away and comes back again, the benefit from adding a chatmessage would be small actually. If additional code is needed to distinguish between a manual and an automatic restart, the effort wouldn't be worthwile at all and to me the risk of additional memory problems is a strong argument against it anyway. So I'd be very fine with just closing this issue. | |||||
Note ID# 1214:
| User: | Lulu | Submitted: | 19/06/2017 | ||
| ok thanks 🙂 | |||||
Note ID# 1215:
| User: | Lulu | Submitted: | 19/06/2017 | ||
|
Updated status to Abandoned from Need Info. |
|||||