|
clwprogrammer wrote: I am very frustrated with the approval system for an article to syick around
My first article was is a disaster. Frustrated like hell. PIEBALD was not happy with my effort. I kept improving it based on his comments and learned a lot. It's still visible, and I won't take it down either.
Mr. PIEBALD kept insisting I improve; as if I could do better. Three times MVP by now, so he was right.
Try again. And again. They're patient and will help you if you ask 
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Articles are as much about the development process as they are about the code. A few bullet points and an image or two do not really qualify as an article.
Instead of seeing it as a withering attack, use the criticism to do it better. I've actually changed code after I started writing the article because trying to explain something to someone else often brings flaws to light.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: trying to explain something to someone else often brings flaws to light.
similar to the Rubber Ducky process, which I use often for the same reason. I have solved many issues and problems by just talking about it out load.
|
|
|
|
|
I call it "talking to the dogs".
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I've found that starting to write an article usually triggers a new phase of code refinement. When my explanation becomes too wordy and complex, I find myself returning to the code to remove complexity so I don't have to write so much about it. It results in better code and a more readable article. It sometimes requires changing design fundamentals and deep refactoring but I've got used to that now.
|
|
|
|
|
Can a member of staff please delete my message. I dont think i can do so once it has replies. You see, I dont write articles. I am not good at putting my thoughts to words at all. This is why i only give a brief overview. I only wanted to share the library. I have deleted all of my uploads and will no longer fret on it.
CLWPROGRAMMER
|
|
|
|
|
clwprogrammer wrote: Can a member of staff please delete my message. I dont think i can do so once it has replies. You see, I dont write articles. I am not good at putting my thoughts to words at all.
I wasn't either.
clwprogrammer wrote: This is why i only give a brief overview. I only wanted to share the library.
Then you got more than you wanted.
You've put effort in the library. So, yes, I'd like to hear about how you done it. What was the reason to write it? What problem does it solve? How?
You can answer those questions? Write it down, even if you think no one wants to read it. Because they do. And they download the code, use it in their own projects.
Get up. Try again. I'll look at both code and article.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
With IoT widgets you often have far more RAM in your frame buffer of your display controller than you do in your MCU.
While you're not using the display, you could theoretically take advantage of it by "drawing" memory to the display and then reading it back off. If you did it with the backlight off it would be somewhat slow and less efficient than using local RAM but in some cases this means an extra 768kB, like you get with the RA8875.
Then I realized how silly this is. Just because you *can* do something doesn't mean you should.
Real programmers use butterflies
|
|
|
|
|
Exactly. "Because I can" is very rarely a good reason to do something.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
That's why the approach in the OP won't go past conception. 
Real programmers use butterflies
|
|
|
|
|
Monty Python Flying Code - It's too silly.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Actually, if I remember correctly, some time ago I read an interview with a guy that was a developer in the 1980s or 1990s (I think I got the decade right) that used their very limited graphics (compared to today) to, not only store, but do calculations.
I can not remember what they calculated but he described that their CPU was very limited for the amount of data in terms of speed, so they used their unused graphics card for bulk storage and processing.
Each (8-bit grayscale) pixel corresponded to a variable and they would write from RAM to the graphics card an entire screen (320x200?!?) at a time as a memory page. Then they would do the same operation on all pixels (variables) and read back the memory page (screen) into RAM.
I searched my browsing history but can not find the link  . I did not bookmark it because I thought of it as just a curiosity.
I do not know if something like this would apply to your case or if reading and writing in bulk to your IoT screen would be fast enough to be useful but when you can not stretch the hardware it is time to get silly inventive
|
|
|
|
|
Well that's certainly a unique way to reinvent and modernize CRT memory.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
Old computer history can display some amazing memory technologies. Another one, from about the same time as CRT storage, is mechanical waves in a mercury filled tube (Wikipedia: Delay Line Memory[^]) - far from random access, but the 1948 EDSAC[^] actually used them for working storage.
After the Apollo 11 crew left a reflector on the surface of the moon, I saw some apparently serious proposals to use such reflectors with a pulsed laser as an optical delay line for data storage. You can fit quite a few bits in a single laser beam 385,000 km & return with a 10 Gbps laser ... I guess those making the proposals live in sunny areas ... I never heard of any realization of the idea.
|
|
|
|
|
I'm going to be offline for a while (probably some weeks). I might get online every several days but it won't be much.
See you around.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek wrote: offline for a while
Not a bad thing sometimes, enjoy the time.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Thank you.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Great! Enjoy yourself, smell the roses so to speak.
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
Thanks.
I am doing it
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Quote: What I have tried:
I have gotten a good night's sleep.
I have had a good breakfast and drank plenty of fluids.
I am not going to try anything because I mighht break something.
Posted recently on QA: I won't link to it because ... well ...
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
Getting good sleep is my priority too.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Well, just the other day I recommended that someone get some food and rest and then have a fresh look at the simple logic error he had written.
|
|
|
|
|
|
Mmm.. I should try those hey! 
|
|
|
|
|
BillWoodruff wrote: I am not going to try anything because I mighht break something.
This is the most important thing to beat out of the heads of many trainees.
I blame academy for this: they teach you that you have only one go, from start to finish, without material, in a short time and on paper (good luck debugging it) so either you know how to resolve the assignment or you don't.
I am thankful for what I learned in my Computer Egnineering studies, but ![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif) knows if there aren't a bunch of things I would change.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
