@kas1e

Amazing ! I hope you will succeed.

Keep up the good work.

Martin

_________________
Theres a time to live and a time to die
When its time to meet the maker
Theres a time to live but isnt it strange
That as soon as you're born you're dying

@kas1e

Keep up good work!

Just wondering....

What do you developers do when a piece of code crashes your Amiga ?
Reset it ?
What if an error cant be found easily, and it keeps crashing. Resetting must be a pain in the ass.
Or do you have a better way to deal with this ?

Martin

_________________
Theres a time to live and a time to die
When its time to meet the maker
Theres a time to live but isnt it strange
That as soon as you're born you're dying

@Metalheart

Reboot of course. 100% reboot. And not only because of fixing of crash, but because if crash happens, your system already "infected" by crappy code , and system already unstable (even if visually its "ok"). So, if not make a reboot, and continue to work, then all the errors which you will have later, can be not because of new code whih you do after crash, but because of first one, which will mess your head.

Of course its still good to have GR, becasue it show you some kind of alarm like "hey, reboot as fast as you can", so you can finish all the stuff, save the code, remember all what you do, reboot , and again :)

Also i for example not have anything in wbstartups, or in system startup scripts (only few little tools), becasue of it reboot its about 5-10 seconds usually.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

So another step solved, very good !

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@Metalheart

Quote:

What do you developers do when a piece of code crashes your Amiga ? Reset it ? What if an error cant be found easily, and it keeps crashing. Resetting must be a pain in the ass. Or do you have a better way to deal with this ?

I never reset unless I have to, which usually means it locked up or is just completely screwed in some way. Normally, if it crashes the GrimReaper shows up and usually gives valuable information for debugging.
So, try to fix the bug and run again. Still crashing, try another fix. Try again. Crash again. Another bug. Fix, Try again.

I never reboot unless the system locks up or is completely ####ed, like swapping low on memory and can't run normally or something.

I think ppl are two scared of corruption in the system after a crash. I have crashes all the time because of programming but it rarely affects the system so I keep running until something locks up. Even if there is some effect you can still usually test your bug until you find it, then perhaps reboot after all the tests before you start on something new.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@Deniil715
I think the reason is that it might cause the debug to be unreliable if you dont reboot.
Doubt it would be fun to try to fix a bug that was caused by a previous crash. At least that is how i understand it.

Rebooting OS4.1 takes less than 10 seconds anyways..

@Deniil715

Ok, so Grimreaper realy made life better for you programmers.
Nice to hear.

I only do stuff using Hollywood or simple scripts, so crashes are not very likely.

Thanks,

Martin

_________________
Theres a time to live and a time to die
When its time to meet the maker
Theres a time to live but isnt it strange
That as soon as you're born you're dying

@Metalheart

Only to the point where you know where to look, of cause you can stop the application from running, if it does something bad, I don’t reboot unless I most.
The application I’m working on now don’t crash in a normal way it just slows down my Amiga to point where GCC becomes useable.

I also have some minor problems whit my KWM that’s annoying, almost every time I boot my Amiga it auto reboots when it does not detect the keyboard, the only way I found to work around this is by pressing Caps Lock while booting. (Anyway the new KWM is better than the old one)

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Tomas

Since I never reboot until I have to, I can tell you and everyone else that it is very very rare that a previous crash cause the next test to crash or misbehave because of it. And I have worked like this for 15 years from OS3.0 up to OS4.1. It is just not justifiable to reboot after every single GrimReaper that pops up. Think about it, if you damage DOS or intuition or something so badly that *they* cause your program to crash the next time, then it is unlikely that your text editor or compiler would run anyway but also crash or hang. And if this is not happening it means there is no damage and there is no point in rebooting.

Remember, the GrimReaper is there to prevent damage to other areas. Only if you press Continue or Ignore DSI you *may* be into deep water depending on the type of fault. 99% of the times the app only damage itself before it is caught by the Reaper.

If the computer reboots in 1 second or 1 minute is fairly irrelevant since it will take you at least a minute more after it booted to start/open the development environment, open all files, find where you were and get into you code again. Completely untolerable interruption in the work for me.

@Metalheart

Yes the GrimReaper often tells you immediately in what function it crashes and what address that caused the crash. If the address is less than 100 or something it pretty much always means you forgot to allocate memory or initalize something properly, or you mistakenly access a NULL pointer because of missing if-statement or something.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@NutsAboutAmiga

Quote:

The application I’m working on now don’t crash in a normal way it just slows down my Amiga to point where GCC becomes useable.

Then it is stuck in a never ending loop.
Use Scout and select Tasks. Then find your task and I bet you it says Ready which means it wants to run all the time. Click Update a few times to be sure. Only idle.task should be Ready at all times.

When this happens, just click Freeze to pause it. Scout is unable to remove a task since OS4.1 so don't try that.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@all
mui-owb progress:

-- with help of Deniil we fix timer stuff (was not so problematic, but still work are too). He also help to rewrite some hooks in vapor.h (what was pretty important should to say), and with who we discuss when he not busy at jobb some stuff :)

-- with everyday help from Fab i understand whole OWB more , write my first mui-test examples with subclasses and so on.

-- and the more enjoyably moment, its that we have very initial window, and there is:

there_is_the_initial_screenshot

Yeah, show nothing, say nothing, but its mean that whole stuff works, main loop works, mui-code, macroses, some hooks, some mos-specific rewriting are works as well. Its empty window in general mean that now we start to deal with bugs and problems which are more interesting and hi-level (mui4 deps, etc).

After we will get rid off from mui4 deps, and everything will works (i.e. windowses spawns, all works), but just without scrollbars, and all the other mui4 deps ,then the last , and maybe much more interesting works will starts (add missing mui4 deps).

But all of you should be sure, that all unpossible to do without Fab's help. If he will say tomorrow "i tired , let's stop", i am almost sure we will not reach final end then. So all "thanks" should going to Fabien.

I even have some kind of "relief" for now, because when we run first working binary, which show that empty window, which resizes, works, and main mui menu works (i.e. all those options, windowses menus are navigatable and can be seen). I even can put marks for example on settings . But its plain intutiion/mui stuff, so nothing surprising, but still.

Still hell of work to be done, but its something. I will keep you all informed, and when something interesting can be shown i will make screen shots or vids (asking for alpha-bins its also pretty early).

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Very OT.... but.... What did you do to change DOPUS's slider knobs ? They look cool. What else did you change ?

Thanks,

also great work your doing... realy !

Martin

_________________
Theres a time to live and a time to die
When its time to meet the maker
Theres a time to live but isnt it strange
That as soon as you're born you're dying

@Metalheart
Its silver-theme (coming with aos4.1u2 only if i remember right). It change sliders, whole looks of windowses, and make them more interesting in compare with default looks (imho of course).

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e
Looks very promising. Thanks again for the update.
And of course thanks to Fab as well.

@kas1e
Good work, very pretty window

_________________

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@kas1e

Excellent! Great progress. Very promising.. Yes FAB IS A MEGA HERO for the Amiga world! Now you too!

Still no word from Joerg? What a jerk...

@realize

I think Joerg said that he wasn't interested in helping with a MUI port. Whatever his reasons, it's his decision, you are in no position to criticise him or call him names.

I have reported you for a "Personal Attack".

_________________
cheers
tony

Hyperion Support Forum: http://forum.hyperion-entertainment.biz/index.php

@realize

Quote:

realize wrote: [...] What a jerk...

That is most inappropriate.