Hints for GUI

Developer
Oct 8, 2010 at 1:29 AM
  1. Don't keep asking us, it kinda bothers us, you won't learn anything. read pervious threads for more
  2. Make sure to keep reference to Cosmos.Hardware
  3. Use VGAScreen.SetPallet() to load pallet
    1. see http://www.tayloredmktg.com/rgb/ for a good rgb color chart
    2. Colors are through 63, so be careful
  4. You will run out of memory sooner or later

your welcome, non gui people!

Oct 8, 2010 at 7:33 PM

pffffffffffffffffffffffffffffffffffffffffffffffffffffft!!!!!!!!!!!!

says the guy who made me like a million offers for dud3s gui xD

Developer
Oct 8, 2010 at 10:36 PM

uhh. ssh!

Oct 11, 2010 at 1:55 AM

"4.   You will run out of memory sooner or later"

YES * 10000000000000.9

though there is a quick and dirty workaround... 

But if you make a working GUI, you will figure it out eventually.

Oct 11, 2010 at 3:46 AM

sadly i have difficulties with realising things that dont work well but i would like work around

Oct 11, 2010 at 4:20 AM

basically, reset where the memory is. So far (as far as I know) memory just keeps getting used up until you run out. (Which is, as we know, not good.)

So I just told it to go back in memory and overwrite before you reach the end. (and also not overwrite the kernel what's in the memory, because overwriting the kernel would be bad...)

Cosmos.Kernel.Heap.mStartAddress
Cosmos.Kernel.Heap.mEndOfRam
are pretty useful. (or it was back in revision 38782, I wasn't able to run current revisions until now, now that I have Visual Studio 2010.)
(Also, I had to change the two variables above from private to public.)

Coordinator
Oct 11, 2010 at 8:30 AM
When you change the mStartAddress value, please consider that any
object which might still be in use will be overwritten...

On 10/11/10, aaronlego2 <notifications@codeplex.com> wrote:
> From: aaronlego2
>
> basically, reset where the memory is. So far (as far as I know) memory just
> keeps getting used up until you run out. (Which is, as we know, not good.)So
> I just told it to go back in memory and overwrite before you reach the end.
> (and also not overwrite the kernel what's in the memory, because overwriting
> the kernel would be bad...)Cosmos.Kernel.Heap.mStartAddress
> Cosmos.Kernel.Heap.mEndOfRam
> are pretty useful. (or it was back in revision 38782, I wasn't able to run
> current revisions until now, now that I have Visual Studio 2010.)
> (Also, I had to change the two variables above from private to public.)
>
>
Coordinator
Oct 11, 2010 at 10:01 AM

Wow. That is really not a good idea :) as mterwoord explains.

Oct 11, 2010 at 7:28 PM

wait... i dont get it... why is it a bad idea?

Oct 11, 2010 at 8:22 PM

because you dont know whats in that memory space you could be overwriting very import stuff or even variables objects and other things like that. im not sure but you might even beable to erase your booting iso.

Oct 12, 2010 at 2:32 AM

yep... it will still crash eventually, but it will prolong its life for a while.