– Daddy, I have few questions to answer for my software engineering class, can you help me?
– Sure, say it.
– Define “workaround”.
– Do you remember the restroom door of your aunt Greta?
– Wow. Sure.
– That’s it.
Sometimes I wonder if it is not a better idea to take a nap…
I coded what you can see in the screen shot below, and it does not worked: nothing appears on screen…
I checked:
a. I removed the image meant to be displayed,
b. I read the code back:
I created the offscreen Picture
I draw the x,
I add the error string…
Everything is here.
Close the project, relaunch, run: still nothing.
I took a coffe, look thru the (bathroom) window, and be back to the code.
Light coming: I only forgot to assign the Picture top the Canvas’ Backdrop !
Not “great”. OOTB thinking is great when you solve COMPLETELY something in a unusual way, using less resources, or rearranging improper resources in a way it solves the problem. That person introduced a new ugly problem to the “project”, and then made it “work”, but it’s still ugly and problematic (that “tab” on the wall can cause accidents and avoid large square boxes to pass through, for example). A workaround does not solve (correctly) a thing, it makes that thing “useful” applying a bridge over flames on a path instead of extinguishing the flames there.
