There is a lot of waste coming from every purchase of fast food - bags, boxes, wrappers, etc.
What if, instead of throwing everything away every time, we could use a reusable bag, just like the trend is starting at grocery stores?
One problem with this is that the bag may get dirty over time from the french fries, grease, and other materials.
Some solutions:
- Recycle the bag after it has been used so many times.
- Wash the bag.
- Have better wrappers for food put inside of bag.
- Make it a self-cleaning bag. Read more.
The above handles at least the to-go bag.
Another problem is the wrappers and boxes that the main sandwiches/hamburgers go in. Even if they are made out of paper or cardboard, they are still thrown away. So, how do you make a reusable box if it keeps getting dirty/soiled by the sandwich.
Solution: Add a super hydrophobic and/or another non-stick surface to it. Here's one example for superhydrophobic. As for non-stick, I've seen a few videos of ketchup (and more things) not sticking to the insides of bottles or other places with the added non-stick surface.
~ Danial Goodwin ~
Showing posts with label problem. Show all posts
Showing posts with label problem. Show all posts
2013-12-15
C2: [Bug Fix] Windows Phone Export Doesn't Go Full-Screen or Landscape Mode
So, in my quest to create 100 Windows apps, I'm finding more solutions to bugs/issues/problems with the export of Windows Phone from Construct 2.
Problem: No Fullscreen. Here's how to fix it:
1. After you have exported the app from Construct 2, open MainPage.xaml
2. Find the line that says:
shell:SystemTray.IsVisible="True"
And, change it to:
shell:SystemTray.IsVisible="False"
Problem: No Landscape Mode. Here's how to fix it:
1. After you have exported the app from Construct 2, open MainPage.xaml
2. Find the line that says:
SupportedOrientations="Portrait" Orientation="Portrait"
And, change it to:
SupportedOrientations="Landscape" Orientation="Landscape"
That should do it! =]
UPDATE: The landscape mode problem has now been fixed! (2013-12-19)
~ Danial Goodwin ~
Problem: No Fullscreen. Here's how to fix it:
1. After you have exported the app from Construct 2, open MainPage.xaml
2. Find the line that says:
shell:SystemTray.IsVisible="True"
And, change it to:
shell:SystemTray.IsVisible="False"
Problem: No Landscape Mode. Here's how to fix it:
1. After you have exported the app from Construct 2, open MainPage.xaml
2. Find the line that says:
SupportedOrientations="Portrait" Orientation="Portrait"
And, change it to:
SupportedOrientations="Landscape" Orientation="Landscape"
That should do it! =]
UPDATE: The landscape mode problem has now been fixed! (2013-12-19)
~ Danial Goodwin ~
2013-07-17
Things People Should Know: Parkinson's Law Of Triviality
(For people that have to work in groups or have a "project manager")
Also sometimes referred to as the "Bike Shed Problem" or "bikeshedding".
This is the newest phenomenon that I have added to my great list of Things People Should Know. It is not a new concept (first mentioned in 1957) and I have known about it for awhile, but recently I have been noticing it more.
What is the Bike Shed Problem? Let me provide an example: (From Parkinson's book, as quoted in Wikipedia)
So, now that you know about Parkinson's Law Of Triviality, hopefully you will be able to better recognize when others do it and when you do it yourself. It is a natural thing to want to give input when you can, but don't let it become a hindrance to getting the most important things done.
If you know ultimately that a feature really doesn't matter, then make sure you work on the important stuff first. Also, be aware, don't always think you know better than others.
More Reading:
- Coding Horror
- Wikipedia
~ Simply Advanced ~
Also sometimes referred to as the "Bike Shed Problem" or "bikeshedding".
This is the newest phenomenon that I have added to my great list of Things People Should Know. It is not a new concept (first mentioned in 1957) and I have known about it for awhile, but recently I have been noticing it more.
What is the Bike Shed Problem? Let me provide an example: (From Parkinson's book, as quoted in Wikipedia)
In the third chapter, "High Finance, or the Point of Vanishing Interest", Parkinson writes about a finance committee meeting with a three-item agenda.
The first is the signing of a £10 million contract to build a reactor, the second a proposal to build a £350 bicycle shed for the clerical staff, and the third proposes £21 a year to supply refreshments for the Joint Welfare Committee.
The £10 million number is too big and too technical, and it passes in two minutes and a half.
The bicycle shed is a subject understood by the board, and the amount within their life experience, so committee member Mr. Softleigh says that an aluminium roof is too expensive and they should use asbestos. Mr. Holdfast wants galvanized iron. Mr. Daring questions the need for the shed at all. Mr. Holdfast disagrees.
Parkinson then writes: "The debate is fairly launched. A sum of £350 is well within everybody's comprehension. Everyone can visualize a bicycle shed. Discussion goes on, therefore, for forty-five minutes, with the possible result of saving some £50. Members at length sit back with a feeling of accomplishment."
Parkinson then described the third agenda item, writing: "There may be members of the committee who might fail to distinguish between asbestos and galvanized iron, but every man there knows about coffee – what it is, how it should be made, where it should be bought – and whether indeed it should be bought at all. This item on the agenda will occupy the members for an hour and a quarter, and they will end by asking the Secretary to procure further information, leaving the matter to be decided at the next meeting."
So, now that you know about Parkinson's Law Of Triviality, hopefully you will be able to better recognize when others do it and when you do it yourself. It is a natural thing to want to give input when you can, but don't let it become a hindrance to getting the most important things done.
If you know ultimately that a feature really doesn't matter, then make sure you work on the important stuff first. Also, be aware, don't always think you know better than others.
More Reading:
- Coding Horror
- Wikipedia
~ Simply Advanced ~
2013-03-11
GameMaker Versus GameMaker Studio
This post will answer the following questions and more like them:
A quick search on the Internet for the above queries and the like do not give an answer. So, I just downloaded both of them and messed with available functions to figure it out. The following gives a basic overview of the differences between the two, which would have helped me when I was first starting. These are all the problems that I encountered when beginning.
I hope this helps.
~ Simply Advanced ~
- "What is the difference between GameMaker 8.1 for Windows and GameMaker Studio?"
- "Can I upgrade from GameMaker for Windows/Mac to GameMaker Studio?"
- "Why doesn't the GameMaker licence key work?"
A quick search on the Internet for the above queries and the like do not give an answer. So, I just downloaded both of them and messed with available functions to figure it out. The following gives a basic overview of the differences between the two, which would have helped me when I was first starting. These are all the problems that I encountered when beginning.
- The regular GameMaker 8.1 for Windows (version 7 for Mac) is only for creating executables (.exe's) of games and easy exporting to YoYo Games for showcase. This is the version that can be upgraded for $39.99.
- No, GameMaker for Windows/Mac is different than the GameMaker Studio suite. I purchased the GameMaker: Studio™ Standard, got the licence key, and tried it multiple times in the GameMaker 8.1 Lite, but it didn't work.
- The GameMaker licence key probably doesn't work because you are trying to use a Studio key on the basic version or vise-versa. You need to download the GameMaker Studio version, then input the licence key there. There is also a link to download the proper version in the confirmation email that you will receive.
I hope this helps.
~ Simply Advanced ~
2012-12-14
Idea: Everybody Wear Headphones in Speaking Class
Problem: I have to work with many groups of people and give presentations with them. A few members don't speak up so that the entire room can hear them.
Solution: My suggestions have been to practice presenting outside at least five meters apart from each other. Another suggestion is to make everybody in the group wear large headphones. This will force everybody to speak up and get used to speaking louder.
~ Simply Advanced ~
Solution: My suggestions have been to practice presenting outside at least five meters apart from each other. Another suggestion is to make everybody in the group wear large headphones. This will force everybody to speak up and get used to speaking louder.
~ Simply Advanced ~
Subscribe to:
Posts (Atom)