firefighter | build firecracker and run a firecracker micro | Serverless library

Try this:

you cant just set properties that way. You need to access them within a constructor and or by instantiating the class then setting the inherited property.

so a way to do this would be :

There are many ways you can do this. Here is one simple example. Enums can be a useful choice here because they have a name and numeric value and can be treated as Int32 types because that is their value under the hood.

With regards to storyboards vs. code, I generally find working with code to be cleaner and quicker. Especially when there isn't a complicated design to work out by code. Even if I wanted to set up my entire app graphically, I generally work with View Controllers attached to their own Xib files so as to avoid having a super large storyboard that becomes annoying to work with as it gets too large.

With regards to your question, if I understood correctly you just want to use your enum to source your picker and your collection view, rather than having to set the information manually each time. You were quite close (you commented out the conformance to the CaseIterable protocol).

I made some adjustments to your code: For the enum I conformed to CaseIterable which allows you to access a property called allCases on the enum. This just returns all your cases in an array. I also added a variable to the enum that directly provides you with the image saved. I'm force unwrapping it (!) because the image should be there 100% of the time. So I'm not worried of it ever being nil. I also added a numberOfItems variable but this could easily be replaced with allCases.count. Anyway, either one of these will allow your numberOfItemsInSection to automatically reflect the amount of JobRoles you have.

If we store your results in its own variable, we then have 2 options right off the bat.

I ran it on jsfiddle and got the following error:

"ReferenceError: buttonClicked is not defined"

You have some formatting issues in your code, I believe. I moved your button up in the page and it started working. Check out the fiddle.

Your "not working" code is actually writting out all the data. But your nextrow logic is flawed, so some data is being overwritten.

Rather than try to fix that code, I would suggest an alternative method

Okay so I've managed to find a solution with node.js. I've used the geolib package. In it you'll find a function called orderByDistance(point, arrayOfPoints). point refers to your target coordinate (in my example, the location of the fire fireCoordinates). And arrayOfPoints refers an array of coordinates to sort (in my example, the volunteers array). I had to change my volunteers array a bit, placing the latitude and longitude outside of the variable origin in fields that have to be called latitude and longitude specifically (any other field names wont work). In short, in order for the orderByDistance function to work, I changed my volunteers array to look like this

volunteers = [{name:"john",age:"32",latitude:(some number),longitude:(some number)},{name:"tony",age:"34",latitude:(some number),longitude:(some number)},{name:"timothy",age:"27",lat:(some number),lng:(some number)},{name:"pat",age:"35",latitude:(some number),longi:(some number)]

Finally, using the function is easy:

It doesn't make any sense at all. If you look at your levels now: