LCDproc development and user support list

Text archives Help


[Lcdproc] MtxOrb v0.4.5 - bug fixes


Chronological Thread 
  • From: SvenDowideit AT home.org.au (Sven Dowideit)
  • Subject: [Lcdproc] MtxOrb v0.4.5 - bug fixes
  • Date: Mon Sep 13 12:33:02 2004

best to assume that it hallened on 4.5 until i find out for sure

i was running 4.3 or something from the debian package before

good work though :)

sven

On Mon, 2004-09-13 at 21:37, Chris Lansley wrote:
> What is odd is I haven't changed the backlight code.
> If you are REALLY sure that the backlight acts differently with the default
> 0.4.5 MtxOrb driver compared to mine, then I will start investigating.
>
> Chris.
>
>
> > -----Original Message-----
> > From: Sven Dowideit
> > [mailto:SvenDowideit AT home.org.au]
> > Sent: 13 September 2004 12:34
> > To: Chris Lansley
> > Cc:
> > lcdproc AT lists.omnipotent.net
> > Subject: RE: [Lcdproc] MtxOrb v0.4.5 - bug fixes
> >
> >
> > aaargh
> >
> > the backlight turned off later on - and now does it every time i start
> > the client
> >
> > weird
> >
> >
> >
> > On Mon, 2004-09-13 at 21:01, Chris Lansley wrote:
> > > I've sent you a new source file.
> > >
> > > Adding the option "dontlinewrap=yes" will hopefully fix your
> > problem with using less than the full display.
> > >
> > > Chris.
> > >
> > >
> > > > -----Original Message-----
> > > > From: Sven Dowideit
> > > > [mailto:SvenDowideit AT home.org.au]
> > > > Sent: 13 September 2004 11:27
> > > > To: Chris Lansley
> > > > Cc:
> > > > lcdproc AT lists.omnipotent.net
> > > > Subject: RE: [Lcdproc] MtxOrb v0.4.5 - bug fixes
> > > >
> > > >
> > > >
> > > > ok - later i'll test it on my full sized screen too ;)
> > > >
> > > > I assumed that if i the user set a screen size, it should
> > always use it.
> > > >
> > > > sven
> > > >
> > > > On Mon, 2004-09-13 at 19:57, Chris Lansley wrote:
> > > > > I've just realised that your changing the screen size to
> > 18x2 when in
> > > > > fact your screen is larger is going to cause problems (with
> > > > both versions) -
> > > > > that's because they both make use of the linewrap feature of
> > > > your display
> > > > > - i.e they will both write past the end of a line and assume it
> > > > will linewrap
> > > > > automatically to the next line which it won't on your
> > display (if that
> > > > > makes sense).
> > > > >
> > > > > It's an easy change to make but I think it should be
> > configurable in the
> > > > > config file.
> > > > >
> > > > > Chris.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From:
> > > > > > lcdproc-admin AT lists.omnipotent.net
> > > > > > [mailto:lcdproc-admin AT lists.omnipotent.net]On
> > > > > > Behalf Of
> > Sven Dowideit
> > > > > > Sent: 13 September 2004 10:39
> > > > > > To: Chris Lansley
> > > > > > Cc:
> > > > > > lcdproc AT lists.omnipotent.net
> > > > > > Subject: RE: [Lcdproc] MtxOrb v0.4.5 - bug fixes
> > > > > >
> > > > > >
> > > > > > yep.
> > > > > >
> > > > > > and i spoke too soon with the no corruption
> > > > > > this time I have a surious 'i' in the CPU screen (second line just
> > > > > > before the 'U')
> > > > > >
> > > > > > and i'm not sure about the Time screen - I get
> > > > > > '/13 19:44:36' on the second line. I assume that something
> > > > is awry with
> > > > > > the screen size calculation due to my size=18x2 - but the
> > other screen
> > > > > > "seem" ok - I need to confirm what they should look like
> > > > > >
> > > > > > sven
> > > > > >
> > > > > > On Mon, 2004-09-13 at 19:25, Chris Lansley wrote:
> > > > > > > Thanks for your help!
> > > > > > >
> > > > > > > The "backlight bug" - does that only happen with my code?
> > > > > > > [I don't recall changing anything to do with backlights...]
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From:
> > > > > > > > lcdproc-admin AT lists.omnipotent.net
> > > > > > > > [mailto:lcdproc-admin AT lists.omnipotent.net]On
> > > > > > > > Behalf Of
> > > > Sven Dowideit
> > > > > > > > Sent: 13 September 2004 10:07
> > > > > > > > To: Chris Lansley
> > > > > > > > Cc:
> > > > > > > > lcdproc AT lists.omnipotent.net
> > > > > > > > Subject: RE: [Lcdproc] MtxOrb v0.4.5 - bug fixes
> > > > > > > >
> > > > > > > >
> > > > > > > > ok, there are definatly improvements.
> > > > > > > >
> > > > > > > > I've been running it now for 6+ hours, with no corruption
> > > > that I can
> > > > > > > > see.
> > > > > > > >
> > > > > > > > With pure lcdproc4.5 I would see some corruption in under 10
> > > > > > mins, with
> > > > > > > > it getting worse over time.
> > > > > > > >
> > > > > > > > however. this is on my usb MX2 but where I have set the size
> > > > > > to 18x2 as
> > > > > > > > there is less screen visible in the case I have.
> > > > > > > >
> > > > > > > > I have not tested this with anything other than the
> > > > lcdproc client..
> > > > > > > >
> > > > > > > > (more results should follow over then next week - I have to
> > > > > > find time to
> > > > > > > > test the buttons too)
> > > > > > > >
> > > > > > > > one Bug? - when a client connects (with Backlight=open in the
> > > > > > .conf) it
> > > > > > > > seems to turn the backlight off (running LCDd and
> > lcdproc with no
> > > > > > > > params)
> > > > > > > >
> > > > > > > > Cheers
> > > > > > > >
> > > > > > > > Sven
> > > > > > > >
> > > > > > > > On Mon, 2004-09-06 at 05:19, Chris Lansley wrote:
> > > > > > > > > I've made some (local) changes. My own tests
> > suggest that my
> > > > > > > > improved driver is better.
> > > > > > > > >
> > > > > > > > > And it's not just bug fixing: For example during a 1 minute
> > > > > > > > test, the old driver sent 20Kb
> > > > > > > > > of data and issued 123 define character commands,
> > whilst my one
> > > > > > > > sent 7Kb of data and issued
> > > > > > > > > 17 define character commands to display the same
> > stuff. This
> > > > > > > > was obtained in part from better
> > > > > > > > > custom character handling. [Stats are from a
> > protocol decoder
> > > > > > > > I've written].
> > > > > > > > >
> > > > > > > > > Clearly such a change needs beta testers! Just in case it's
> > > > > > > > worst than the previous driver on
> > > > > > > > > some models. Please BETA test if you can. [Thanks
> > to Sven for
> > > > > > > > offering to help!]
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Chris.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From:
> > > > > > > > > > lcdproc-admin AT lists.omnipotent.net
> > > > > > > > > > [mailto:lcdproc-admin AT lists.omnipotent.net]On
> > > > > > > > > > Behalf Of
> > > > > > Chris Lansley
> > > > > > > > > > Sent: 04 September 2004 10:16
> > > > > > > > > > To:
> > > > > > > > > > lcdproc AT lists.omnipotent.net
> > > > > > > > > > Subject: [Lcdproc] MtxOrb v0.4.5 - bug fixes
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > [This email is referring to LCDproc version 0.4.5
> > > > (and maybe some
> > > > > > > > > > before that)]
> > > > > > > > > >
> > > > > > > > > > Hi,
> > > > > > > > > >
> > > > > > > > > > I've noticed a number of bugs in the MtxOrb
> > driver - I've
> > > > > > > > > > examined the code and have some
> > > > > > > > > > fixes available.
> > > > > > > > > >
> > > > > > > > > > I've noticed:
> > > > > > > > > > 1, BigNums can cause random characters to
> > > > appear (or for
> > > > > > > > > > areas not to be cleared).
> > > > > > > > > > [From examining the code - almost
> > > > anything could go
> > > > > > > > > > wrong on the
> > > > > > > > > > Matrix Orbital side; because the driver
> > > > is sending
> > > > > > > > > > random command sequences]
> > > > > > > > > >
> > > > > > > > > > 2, Areas of the screen stop updating, and
> > > > some random
> > > > > > > > > > characters may appear.
> > > > > > > > > >
> > > > > > > > > > 3, Special chars (user defined
> > characters) are being
> > > > > > > > > > redefined even though they
> > > > > > > > > > are already defined (ie. sends unneeded
> > > > updates over
> > > > > > > > > > serial link).
> > > > > > > > > > [This could be a client problem - not
> > sure yet]
> > > > > > > > > >
> > > > > > > > > > Before I do anything with these fixes - I need
> > to know if
> > > > > > > > > > other Matrix Orbital users
> > > > > > > > > > are seeing these problems. Secondly I would like
> > > > some people
> > > > > > > > > > to offer to be beta
> > > > > > > > > > testers for the fixed driver - just to be sure
> > > > that my changes
> > > > > > > > > > improve the driver!
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Chris.
> > > > > > > > > > [I'm currently working on updating PalmOrb]
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > > LCDproc mailing list
> > > > > > > > > > LCDproc AT lists.omnipotent.net
> > > > > > > > > > http://lists.omnipotent.net/mailman/listinfo/lcdproc
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > LCDproc mailing list
> > > > > > > > > LCDproc AT lists.omnipotent.net
> > > > > > > > > http://lists.omnipotent.net/mailman/listinfo/lcdproc
> > > > > > > > --
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > LCDproc mailing list
> > > > > > > > LCDproc AT lists.omnipotent.net
> > > > > > > > http://lists.omnipotent.net/mailman/listinfo/lcdproc
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > --
> > > > > >
> > > > > > _______________________________________________
> > > > > > LCDproc mailing list
> > > > > > LCDproc AT lists.omnipotent.net
> > > > > > http://lists.omnipotent.net/mailman/listinfo/lcdproc
> > > > > >
> > > > >
> > > > >
> > > > --
> > > >
> > > >
> > >
> > >
> > --
> >
> >
>
>
--





Archive powered by MHonArc 2.6.18.

Top of page