whims | A Web Hyperspace Interface via MQTT over Socket.IO | Socket library

I would like to get rid of the fringes in the emacs minimap buffer. Specifically the line continuation arrows. I would still like them for my main buffers but find them pointless in the minimap.

I have tried to add the following to my ~/.emacs file:

I have read all answers to similar questions and none of them address my issue. As you can see in my code snippet below and attached screen-shot, I have done everything advise for success but no luck.

1. I am retrieving photos from Flickr with https:// and valid api key (see code)
2. All the needed photos are successfully retrieved and stored in var imadeData (see screenshot)
3. FlatList used to list the items in 3 columns via photo id. Screenshot shows the 3 columns but no photos.

Photo.js

There is an embedded Linux system with an externally connected (ethernet) device which sends lots of UDP data, once it's started by a command. At startup, I have one thread which is to continuously receive UDP data for the remainder of the program runtime. As I see it, for reliability in principle, not just by accident, it must be ensured that the UDP reception loop must make its first call to recv() before the external data source is started, or the first packet or so might me lost, depending on scheduler whims. (this is all in a very local, purposefully simple network setup - packet loss is normally not an issue and not handled - speed is king) Currently, right before calling that UDP reception code, I start a temporary thread which delays for some time, then enables the data source to send UDP data. This is currently the way to "ensure" that the first UDP packet arrives when the reception thread is "armed", i.e. within a recv() call, the OS waiting for data.

Even if I, say, set a condition variable, right before the first call to recv() to tell the rest of the program "ok, you can enable the data source now, I'm ready" - it could, in theory, happen that there is some scheduling induced delay between that signal flagging and the actual call to recv (or/and for the internals of recv actually being ready).

Is there a more elegant / proper way to solve this, than using some "empirical delay time"?

Pseudo code for illustration:

I have multiple RouterFunctions which I register as beans (one per section of code).

One of them is /** for dynamic routing for React. Basically, if no other route matches, I want it to go to that one.

The problem is sometimes, depending on the whims of what order they are used, the /** will block another endpoint.

Is there a way to order the separate RouterFunctions or a better way to deal with having everything that doesn't match something else go to a specific route?

I've been developing a library on a Fedora 23 box using g++ 5.3.1, and successfully building this on a Windows box using mingw (I can fetch the version here if necessary). I handed this code off to a coworker today interested in using it. He tried compiling it in Visual Studio 2013 (his IDE of choice), and it blew up. Below I've created an MCVE of the problem:

I have been following a tutorial to get data from an API, but currently it does not seem to be working on my own model. It fetches the data as follows:

For example, the user can perform action A, action B or action C in a tool. Whether they choose A, B or C, the order of these actions and how many times they are repeated is up to the user and the reason why they choose A,B or C and why they are chosen in a particular order isn't clear. Also any action can be repeated again after another action has been done by the user.

EDIT: A more concrete example would be the creation of an image. The user can draw a shape, choose a new shape, choose a new colour and save the image. While drawing these 4 actions can be performed intertwined in any random order and in any random quantity, only guided by the whims of the user. There is also the choice of creating a new image from scratch or editing an existing image to create a new image.