In an earlier post, I had talked about a potential design issue, along with a follow up on that here. In the follow up, I had described how I couldn't reproduce the issue in practical ways. It turned out, I was able to reproduce it with a different project. The first demo below is a demonstration of that, along with how to get around the problem during build time. But, as mentioned in the earlier follow up, it only pushes the problem to runtime. The second demo below describes how to circumvent the issue during runtime as well. Here are the conclusions, having investigated the issue -
Demo I :
Demo II :
Below is a follow-up on a previously published post. In that, I talked about what I thought to be a design issue. I still consider it a design issue, although I can no more reproduce it in practical ways, surprising enough. I mentioned that as well in the preface to that post.
I wish I had recorded the issue then and as I was chasing it, and before concluding the design constraint that forced it. But, I didn't expect the issue to just disappear. So, I didn't record it then. There are enough moving parts in this to suspect an accidental change to have positively impacted the problem, thus making it vanish. Also, this is the kind of issue where I would be more inclined to blame my own oversight, which I still suspect. However, I would more assertively say that with a connecting thread of change to pin to the issue. Failing that, I am unwilling to overlook the previous observations, the easiest thing to do, and because the problem appears to have disappeared. It is exactly this kind of magical and seemingly positive changes that are momentarily inexplicable that pops up again at crunch time. So, I figured I would record its current state. This can only help with a future brainstorming on this topic, perhaps at a later time and when feasible.
Following is a recording of the problem:
[Following is an excerpt from conversation between Elsa Snow'ed-in, we will call [Elsa] and Enlightened Sock [Sock], discussing the zombie in her device.]
[Elsa]: Hello! I am excited to start a conversation on a topic that seems to interest you and frustrate you at the same time.
[Sock]: Good to be here.
[Elsa]: So, tell us more about this project #prismnotes.
[Sock]: When I encounter technical issues that I find inexplicable, I am hoping to note it under #prismnotes.
[Elsa]: By technical issues, you mean, the zombie in your device that gives you grief?
[Sock]: It is a journal of technical issues I am unable to explain to myself. Some of them could be oversight on my part. Rest obviously inexplicable.
[Elsa]: I find the name project #prismnotes interesting. Is there an underlying connotation?
[Sock]: Prism is a three dimensional object that interest me.
[Elsa]: I understand. But is it a light hearted take on something that could be more controversial?
[Sock]: It happens to be a polyhedron, a solid in three dimensions with flat polygonal faces, straight edges and sharp corners or vertices.
[Elsa]: <Annoying stream of giggles> I have access to Wikipedia... You haven't answered my question?
[Sock]: The word polyhedron comes from the classic greek as poly-(stem of "many") + -hedron (form of "base" or "seat").
[Elsa]: <Annoying stream of giggles> Alright. Moving along. Do you expect us to be having frequent conversations? Because.... that could be fun... given how it's going thus far...
[Elsa] : Good... Good <sign of relief> Do you expect to be filing a lot under #prismnotes?
[Sock]: The plan is not to inundate.
[Elsa]: Ok. Can you tell me why you are doing this then?
[Sock]: In future, I would like to avoid having to answer some obvious questions that the better breed won't bother asking.
[Elsa]: Like what...? On the matter of timeline... activities... correlating it with output etc.?
[Sock]: It is purely for the benefit of a deep thinking community that prefer not to insult each others intelligence by asking the obvious questions while helping themselves to a better perception. It is good, as a record, for posterity.
[Elsa]: Have you started on it yet?
[Sock]: I could have started sometime back. My depth of perception hadn't broadened yet, plus I was worried about challenge to cerebral depth if I go down that path.
[Elsa]: Ok, looking forward to it! <Fake giggles> Bye.