As mediaportal is reaching RC3 phase, i'd like to point out some thoughts
about going to RC4/Release version.
I'm very happy about Mediaportal, no guestion about it. even though
i have 15 y's of c# experience, i cannot take part of developing
Mediaportal at the moment.
First thing that comes to mind when i use MP based HTPC as primary STB
for dvb-s is overall stability. i have latest svn and building enviroment installed,
so i can actually debug and analyze logs. But. Well when kids want to
watch tv there is no time to explain that daddy has to tweak something....
Well back to the point. When going to 1.0.0 release i'd like to see
improvement on Error handling, Recovery of a fatal errors, and of course
those Channel is Scrambled and No Audio/Video available
errors. As i know they are just bugs.
In my humble opinion is that So far Developers have done a great job,
but before reaching 1.0.0 Release, i would go trough the code
for looking and checking mutexes, locks, WaitOne clauses without timeout defind.
General Exception catching.
catch(Exception e)
{
....
}
catches all exception and it is effective for hiding some other errors that
actually needs to take care of and should not be hidden. These kind of code lines are the ones
that cause problems in error hunting, at least in projects i've been in.
I think that specific Exception should be used to trap only that exception
we can do something in that part of code.
When using mutex it would be a good idea to implement try/catch/finally and release mutex in finally
statement.
Some other mysterious hangs are for example when scrolling mini epg, or full epg MP sometimes just hangs and i have to reboot.
to developing team.
Regs,
te3hpurp
about going to RC4/Release version.
I'm very happy about Mediaportal, no guestion about it. even though
i have 15 y's of c# experience, i cannot take part of developing
Mediaportal at the moment.
First thing that comes to mind when i use MP based HTPC as primary STB
for dvb-s is overall stability. i have latest svn and building enviroment installed,
so i can actually debug and analyze logs. But. Well when kids want to
watch tv there is no time to explain that daddy has to tweak something....
Well back to the point. When going to 1.0.0 release i'd like to see
improvement on Error handling, Recovery of a fatal errors, and of course
those Channel is Scrambled and No Audio/Video available
errors. As i know they are just bugs.
In my humble opinion is that So far Developers have done a great job,
but before reaching 1.0.0 Release, i would go trough the code
for looking and checking mutexes, locks, WaitOne clauses without timeout defind.
General Exception catching.
catch(Exception e)
{
....
}
catches all exception and it is effective for hiding some other errors that
actually needs to take care of and should not be hidden. These kind of code lines are the ones
that cause problems in error hunting, at least in projects i've been in.
I think that specific Exception should be used to trap only that exception
we can do something in that part of code.
When using mutex it would be a good idea to implement try/catch/finally and release mutex in finally
statement.
Some other mysterious hangs are for example when scrolling mini epg, or full epg MP sometimes just hangs and i have to reboot.
to developing team.
Regs,
te3hpurp