[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

3676.0. "TM Tasks print incorrectly" by KERNEL::VANRIXTELE (Emma van Rixtel) Fri Dec 17 1993 15:32

    
    I have managed to reproduce a very strange customer problem, and just
    wondered if anyone else could reproduce it?
    
    The problem is, in TM when you create a task and fill in both lines of
    the description (it is clearer if you fill the whole line with characters 
    but will still happen if you don't)
    
    When you print or read the task (to any printer or the terminal) the second
    line of the description moves along one character to the right, thus 
    causing the two lines to be mis-aligned.
    
    The funny thing is though, if you select a couple of tasks and choose
    the multiple print option, this does not happen and they are perfectly
    aligned!!
    
    All I want to know is, can anyone else see this? Has anyone ever
    noticed this before? Is it supposed to behave like this?
    
    Thank you,
    
    Emma.

T.R	Title	User	Personal Name	Date	Lines
3676.1		AIMTEC::ZANIEWSKI_D	Why would CSC specialists need training?	`Fri Dec 17 1993 19:48`	6
	Hi Emma, Good observation. I look at that every day and never noticed. I tested against version 3.0A. Dave Zaniewski
3676.2	how do you fix it?	KERNEL::VANRIXTELE	Emma van Rixtel	`Mon Dec 20 1993 14:39`	7
	So it was obviously not supposed to do that, but does anyone know how to correct this?? thnak you, Emma.
3676.3		AIMTEC::ZANIEWSKI_D	Why would CSC specialists need training?	`Tue Dec 21 1993 13:18`	10
	Hi Emma, I won't comment about it being a bug. Element TMPRITASK.BLP was modified for version 3.0. I'll let the engineer, that made the modification, comment. As for returning the original functionality, modify the boilerplate and change each of the <&TAB 16> back to <&TAB 15>. Dave Zaniewski
3676.6	Please report it	IOSG::MAURICE	I left my heart in Alcatraz	`Wed Dec 22 1993 14:23`	23
	Hi, If you consider this to be a bug then please raise a problem report. The reason we keep asking for them is that it is hard for us to justify the time spent fixing problems reported unofficially in Notes Conferences when we have a few Customer reported problems still to fix. In case you or anyone else gets the wrong impression, it is right to still report problems unofficially here for many reasons, e.g. . It has been reported before . There is a fix or workround available . It doesn't turn out to be a problem, and thus saves the company money with one less problem report to process In your case unfortunately none of the above apply, and so we need the problem report. Thanks Stuart
3676.8		FORTY2::ASH	Mail Interchange Group, Reading	`Wed Dec 22 1993 16:40`	7
	.4 is just pointing out that the last developer in this area has left. So it looks like you should try .3, and then reread .6 to see if it's worth raising a bug report. (Actually, I'd suggest raising the report anyway, as someone else is bound to find the problem again, and IOSG are probably desperate for work to do!) g
3676.10	now what??	KERNEL::VANRIXTELE	Emma van Rixtel	`Wed Dec 22 1993 17:05`	6
	Ok, I have tried making the modifications as suggested in .3 and they do not work. So has anyone got anymore suggestions, or would you like me to go ahead and raise a bug report regardless?? Emma.