Topic: better messages about what is BEING made

CrisiusXIII Joined: 2020-09-01, 07:18 Posts: 18 Pry about Widelands	Posted at: 2020-11-10, 06:02 Hello, the metal workshop and other buildings do have a very long lasting "skipping forging" message while another product is already being made. It would be to much to have the actual counter in the display but an little acknowledgement about the momentary product would be nice with eg a simple colour coding in red, yellow and green or perhaps a 3-fase bar. there is some space at the right side from the tab-bar. it could show the product name and icon there aswell with a single word perhaps even in that colour. i have no idear were to find the messages inside the c-script or luna script. although 'printf' works rather simple it probably is a rather large task, i asume. cheers Edited: 2020-11-10, 06:05 Top Quote

GunChleoc Joined: 2013-10-07, 15:56 Posts: 3326 One Elder of Players Location: RenderedRect	Posted at: 2020-11-10, 08:24 The messages are defined by ProductionProgram::ActReturn and you'd have to check into its usages. A better solution for this would certainly be welcome Busy indexing nil values Top Quote

CrisiusXIII Joined: 2020-09-01, 07:18 Posts: 18 Pry about Widelands	Posted at: 2020-11-10, 18:10 Double dots :: does that mean its perl ?? it has the ampersand at the back& I go and try to read it, thank you Top Quote

GunChleoc Joined: 2013-10-07, 15:56 Posts: 3326 One Elder of Players Location: RenderedRect	Posted at: 2020-11-10, 21:00 It's C++. Busy indexing nil values Top Quote

CrisiusXIII Joined: 2020-09-01, 07:18 Posts: 18 Pry about Widelands	Posted at: 2020-12-31, 03:55 Hi i am just reading the remarks and not much more and come to a simple conclusion that a "Busy" return "Result" would be nice `/// Calls a program of the productionsite. /// /// Parameter syntax: /// parameters ::= program {handling_directive} /// handling_directive ::= "on" Result handling_method /// Result ::= "failure" \| "completion" \| "skip" /// handling_method ::= Fail \| Complete \| Skip \| Repeat /// Fail ::= "fail" /// Ignore ::= "ignore" /// Repeat ::= "repeat"` and "Duration" could be mentioned as "busy" value `/// Does nothing. /// /// Parameter syntax: /// parameters ::= duration /// Parameter semantics: /// duration: /// A natural integer. If 0, the result from the most recent command /// that returned a value is used. /// /// Blocks the execution of the program for the specified duration.` but i am not sure at all..... this is where i would start, i guess the most simplistic and common message is " busy for 'X' seconds " with only duration as value i read some off the translation files and that led to severall lua files with comments. somewhere there the "Busy" message probably will have to be added. Top Quote