In ped, I am using FixedFont to edit source files. If I type the two lines:
12345678901234567890
unsigned int xyz;
where there is a space between the ‘unsigned’ and the ‘int’ and a character between the ‘int’ and the ‘xyz’, the ‘xyz’ shows up right next to the ‘int’. It should appear that there are 3 space character widths between the ‘int’ and the ‘xyz’.
Please fix.
PS. My tab width is set to 4.
Bill Caroselli
BTW, this is with both 6.0 and 6.1.
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote in message news:9oflm4$hku$1@inn.qnx.com…
In ped, I am using FixedFont to edit source files. If I type the two lines:
12345678901234567890
unsigned int xyz;
where there is a space between the ‘unsigned’ and the ‘int’ and a character between the ‘int’ and the ‘xyz’, the ‘xyz’ shows up right next to the ‘int’. It should appear that there are 3 space character widths between the ‘int’ and the ‘xyz’.
Please fix.
PS. My tab width is set to 4.
Bill Caroselli
Hi Bill,
Unfortunately this is a known issue. The reason it is occurring is because
once you have typed unsigned int you are only one pixel away from where the
next character(tab stop) will be because the tab stops are set to 4 characters wide.
Sorry
Brenda
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
BTW, this is with both 6.0 and 6.1.
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message news:9oflm4$hku$> 1@inn.qnx.com> …
In ped, I am using FixedFont to edit source files. If I type the two lines:
12345678901234567890
unsigned int xyz;
where there is a space between the ‘unsigned’ and the ‘int’ and a character between the ‘int’ and the ‘xyz’, the ‘xyz’ shows up right next to the ‘int’. It should appear that there are 3 space character widths between the ‘int’ and the ‘xyz’.Please fix.
PS. My tab width is set to 4.
Bill Caroselli
Is there a workaround?
Can I use some other fixed width font that won’t exhibit this?
Will there be a fix any time soon?
It is curious that it also happens with different letters too, not just
‘unsigned int’. That just happens to be my specific example.
“Gui Group” <gui@qnx.com> wrote in message news:9ofqru$je1$1@nntp.qnx.com…
Hi Bill,
Unfortunately this is a known issue. The reason it is occurring is
because
once you have typed unsigned int you are only one pixel away from where
the
next character(tab stop) will be because the tab stops are set to 4
characters wide.Sorry
Brenda
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
BTW, this is with both 6.0 and 6.1.“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message
news:9oflm4$hku$> 1@inn.qnx.com> …
In ped, I am using FixedFont to edit source files. If I type the two
lines:
12345678901234567890
unsigned int xyz;
where there is a space between the ‘unsigned’ and the ‘int’ and a
tab> character between the ‘int’ and the ‘xyz’, the ‘xyz’ shows up right
next to the ‘int’. It should appear that there are 3 space character widths
between the ‘int’ and the ‘xyz’.
Please fix.
PS. My tab width is set to 4.
Bill Caroselli
Hi Bill,
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
Is there a workaround?
Unfortunately there is no work around
Can I use some other fixed width font that won’t exhibit this?
No, unfortunately not.
Will there be a fix any time soon?
A fix is in the works and should be available soon.
It is curious that it also happens with different letters too, not just
‘unsigned int’. That just happens to be my specific example.
It is because the tab stops are set for example if it is set to 4 then
with the string “one twothree” the tab will only be one pixel because
of the character count. For example one twothree
1234123 4 1234
So when you hit tab after the ‘o’ it goes to the begin of the next character
which is at the last 1 thereby leaving only one pixel space.
I hope this helps explain why it is happening.
Regards
Brenda
“Gui Group” <> gui@qnx.com> > wrote in message news:9ofqru$je1$> 1@nntp.qnx.com> …
Hi Bill,Unfortunately this is a known issue. The reason it is occurring is
because
once you have typed unsigned int you are only one pixel away from where
the
next character(tab stop) will be because the tab stops are set to 4
characters wide.Sorry
Brenda
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
BTW, this is with both 6.0 and 6.1.“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message
news:9oflm4$hku$> 1@inn.qnx.com> …
In ped, I am using FixedFont to edit source files. If I type the two
lines:
12345678901234567890
unsigned int xyz;
where there is a space between the ‘unsigned’ and the ‘int’ and a
tab> character between the ‘int’ and the ‘xyz’, the ‘xyz’ shows up right
next to the ‘int’. It should appear that there are 3 space character widths
between the ‘int’ and the ‘xyz’.Please fix.
PS. My tab width is set to 4.
Bill Caroselli
GG > “Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
Is there a workaround?
GG > Unfortunately there is no work around
Can I use some other fixed width font that won’t exhibit this?
GG > No, unfortunately not.
Will there be a fix any time soon?
GG > A fix is in the works and should be available soon.
I don’t want to rush anyone, but will this ever be fixed?
This was reported back in Sept of 2001 for version 6.1.
I hope you don’t think I’m too picky, but text editing is a pretty
basic operation of a software development system. Thank God I’m not
writing in COBOL or some language where which column is which really
matters.
It is curious that it also happens with different letters too, not just
‘unsigned int’. That just happens to be my specific example.
GG > It is because the tab stops are set for example if it is set to 4 then
GG > with the string “one twothree” the tab will only be one pixel because
GG > of the character count. For example one twothree
GG > 1234123 4 1234
GG > So when you hit tab after the ‘o’ it goes to the begin of the next character
GG > which is at the last 1 thereby leaving only one pixel space.
GG > I hope this helps explain why it is happening.
GG > Regards
GG > Brenda
GG >
GG >
“Gui Group” <> gui@qnx.com> > wrote in message news:9ofqru$je1$> 1@nntp.qnx.com> …
Hi Bill,Unfortunately this is a known issue. The reason it is occurring is
because
once you have typed unsigned int you are only one pixel away from where
the
next character(tab stop) will be because the tab stops are set to 4
characters wide.Sorry
Brenda
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
BTW, this is with both 6.0 and 6.1.“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message
news:9oflm4$hku$> 1@inn.qnx.com> …
In ped, I am using FixedFont to edit source files. If I type the two
lines:
12345678901234567890
unsigned int xyz;
where there is a space between the ‘unsigned’ and the ‘int’ and a
tab> character between the ‘int’ and the ‘xyz’, the ‘xyz’ shows up right
next to the ‘int’. It should appear that there are 3 space character widths
between the ‘int’ and the ‘xyz’.Please fix.
PS. My tab width is set to 4.
Bill Caroselli
–
Bill Caroselli – Q-TPS Consulting
1-(626) 824-7983
qtps@earthlink.net
Let me ask again, this time without the sarcasm.
Will this ever be fixed?
It is a real pain to use ped with a fixed pitch font and not know what
column your in.
Bill Caroselli <qtps@earthlink.net> wrote:
BC > GG > “Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
Is there a workaround?
BC > GG > Unfortunately there is no work around
Can I use some other fixed width font that won’t exhibit this?
BC > GG > No, unfortunately not.
Will there be a fix any time soon?
BC > GG > A fix is in the works and should be available soon.
BC > I don’t want to rush anyone, but will this ever be fixed?
BC > This was reported back in Sept of 2001 for version 6.1.
BC > I hope you don’t think I’m too picky, but text editing is a pretty
BC > basic operation of a software development system. Thank God I’m not
BC > writing in COBOL or some language where which column is which really
BC > matters.
It is curious that it also happens with different letters too, not just
‘unsigned int’. That just happens to be my specific example.
BC > GG > It is because the tab stops are set for example if it is set to 4 then
BC > GG > with the string “one twothree” the tab will only be one pixel because
BC > GG > of the character count. For example one twothree
BC > GG > 1234123 4 1234
BC > GG > So when you hit tab after the ‘o’ it goes to the begin of the next character
BC > GG > which is at the last 1 thereby leaving only one pixel space.
BC > GG > I hope this helps explain why it is happening.
BC > GG > Regards
BC > GG > Brenda
BC > GG >
BC > GG >
“Gui Group” <> gui@qnx.com> > wrote in message news:9ofqru$je1$> 1@nntp.qnx.com> …
Hi Bill,Unfortunately this is a known issue. The reason it is occurring is
because
once you have typed unsigned int you are only one pixel away from where
the
next character(tab stop) will be because the tab stops are set to 4
characters wide.Sorry
Brenda
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
BTW, this is with both 6.0 and 6.1.“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message
news:9oflm4$hku$> 1@inn.qnx.com> …
In ped, I am using FixedFont to edit source files. If I type the two
lines:
12345678901234567890
unsigned int xyz;
where there is a space between the ‘unsigned’ and the ‘int’ and a
tab> character between the ‘int’ and the ‘xyz’, the ‘xyz’ shows up right
next to the ‘int’. It should appear that there are 3 space character widths
between the ‘int’ and the ‘xyz’.Please fix.
PS. My tab width is set to 4.
Bill Caroselli
BC > –
BC > Bill Caroselli – Q-TPS Consulting
BC > 1-(626) 824-7983
BC > qtps@earthlink.net
–
Bill Caroselli – Q-TPS Consulting
1-(626) 824-7983
qtps@earthlink.net
Bill Caroselli <qtps@earthlink.net> wrote:
BC > Let me ask again, this time without the sarcasm.
BC > Will this ever be fixed?
BC > It is a real pain to use ped with a fixed pitch font and not know what
BC > column your in.
For the record, this isn’t a “ped” issue. It is a Photon issue.
I.E. Every other editor I’ve tried (under photon) also screws up the
same way.