Yes, this is a limitation of CA. A new variable length string type should be
placed on the list.
Jeff
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Heinrich du Toit
> Sent: Wednesday, December 05, 2007 2:26 AM
> To: [email protected]
> Subject: Re: string monitoring in medm
>
> Aint this another one of those nasty limits in Channel Access?
>
> Do you really need it as 1 long string?
> How about splitting it up into multiple smaller strings?
>
> -Heinrich
>
> Umashankar Panda wrote:
> > Dear Sirs,
> >
> > I am usuing medm as the user interface. I have some async record in
> > string format whose character size is more than 40. I am getting the
> > value in precord after modifying the base code for handling strings
> > upto 80 characters. But, now my problem is that this data is not
> > getting fully displayed in medm. The size is limited upto 40 in medm.
> > This also happens in probe too.
> >
> > Can anybody please suggest a solution for this problem?
> >
> > Ultimately, I need to display the strings in a message box with
> > srcolling facility also. The data is the status of the helium
> > liquefier printed in ASCII format through a serial port.
> >
> > Thanking you
> >
> > With regards
> >
> >
> > Umashankar Panda
> >
> > Variable Energy Cyclotron Centre
> > India.
> >
- References:
- string monitoring in medm Umashankar Panda
- Re: string monitoring in medm Heinrich du Toit
- Navigate by Date:
- Prev:
Re: device support for output connected to volatile device John Dobbins
- Next:
RE: Multiple IOC Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: string monitoring in medm Heinrich du Toit
- Next:
Re: string monitoring in medm nda
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|