How Can I display a Polish chars in my application running under QNX 6 in
text mode?
Any tricks and comments are welcome.
Regards,
Jacek
Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:
How Can I display a Polish chars in my application running under QNX 6 in
text mode?
I don’t think devc-con supports that. Even if you managed to change the
character bitmaps on the card, devc-con will mess up your output by
translating characters from 8859-1 to what it thinks the hardware is
displaying (i.e. the default code page 437).
Any tricks and comments are welcome.
Run Photon and a full-screen pterm?.. 
Pozdrowienia,
Wojtek
“Wojtek Lerch” <wojtek_l@yahoo.ca> wrote in message
news:bdv618$pa2$1@inn.qnx.com…
Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote:
How Can I display a Polish chars in my application running under QNX 6
in
text mode?I don’t think devc-con supports that. Even if you managed to change the
character bitmaps on the card, devc-con will mess up your output by
translating characters from 8859-1 to what it thinks the hardware is
displaying (i.e. the default code page 437).Any tricks and comments are welcome.
Run Photon and a full-screen pterm?.. >
Can pterm be run in Kiosk mode?
Bill Caroselli <qtps@earthlink.net> wrote:
“Wojtek Lerch” <> wojtek_l@yahoo.ca> > wrote in message
news:bdv618$pa2$> 1@inn.qnx.com> …
Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote:
How Can I display a Polish chars in my application running under QNX 6
in
text mode?I don’t think devc-con supports that. Even if you managed to change the
character bitmaps on the card, devc-con will mess up your output by
translating characters from 8859-1 to what it thinks the hardware is
displaying (i.e. the default code page 437).Any tricks and comments are welcome.
Run Photon and a full-screen pterm?.. >
Can pterm be run in Kiosk mode?
What’s Kiosk mode? 
“Wojtek Lerch” <wojtek_l@yahoo.ca> wrote in message
news:bdvbkn$28q$1@inn.qnx.com…
Bill Caroselli <> qtps@earthlink.net> > wrote:
“Wojtek Lerch” <> wojtek_l@yahoo.ca> > wrote in message
news:bdv618$pa2$> 1@inn.qnx.com> …Run Photon and a full-screen pterm?.. >
Can pterm be run in Kiosk mode?
What’s Kiosk mode? >
LOL
I thought that was a QNX term (at least back in the days of QNX Windows) for
no window frame at all.
I know this can be dome on applications that we develop ourselves but I was
wondering if it could also be done on pterm (or any other photon app for
that matter).
Bill Caroselli <qtps@earthlink.net> wrote:
“Wojtek Lerch” <> wojtek_l@yahoo.ca> > wrote in message
news:bdvbkn$28q$> 1@inn.qnx.com> …
Bill Caroselli <> qtps@earthlink.net> > wrote:
Can pterm be run in Kiosk mode?
What’s Kiosk mode? >LOL
I thought that was a QNX term (at least back in the days of QNX Windows) for
no window frame at all.
Probably it was… I’ve never used QNX Windows. I’ve only ever heard
about “kiosk mode” in the context of Phindows, and I think it meant
running a single app without a Photon frame, with the Phindows window
resizing itself automatically to the size of the Photon app’s window, to
make it look like a Windows window. Or something like that… Which is
more or less what you meant I guess, except the resizing part, but I had
to make sure…
I know this can be dome on applications that we develop ourselves but I was
wondering if it could also be done on pterm (or any other photon app for
that matter).
It’s easy to run any app without a window frame – just don’t start the
window manager.
The setup I was thinking of was something along the lines of
Photon
crttrap start
inputtrap starp
while true
do pterm -c -w100% -h100% login
done
It looks practically like a text-mode console, except it has a mouse
cursor.
Wojtek Lerch <wojtek_l@yahoo.ca> wrote:
Bill Caroselli <> qtps@earthlink.net> > wrote:
“Wojtek Lerch” <> wojtek_l@yahoo.ca> > wrote in message
news:bdvbkn$28q$> 1@inn.qnx.com> …
Bill Caroselli <> qtps@earthlink.net> > wrote:
Can pterm be run in Kiosk mode?
What’s Kiosk mode? >LOL
I thought that was a QNX term (at least back in the days of QNX Windows) for
no window frame at all.Probably it was… I’ve never used QNX Windows. I’ve only ever heard
about “kiosk mode” in the context of Phindows, and I think it meant
running a single app without a Photon frame, with the Phindows window
resizing itself automatically to the size of the Photon app’s window, to
make it look like a Windows window. Or something like that… Which is
more or less what you meant I guess, except the resizing part, but I had
to make sure…
We used that term under Photon for QNX4 at least. You could run an
Xserver in “kiosk” mode – same with ICA, and they would take up
100% of the virtual console they were on. No window borders, no
window frame, etc – but you could still have a window manager
running.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Hi Wojtek,
I don’t think devc-con supports that. Even if you managed to change the
character bitmaps on the card, devc-con will mess up your output by
translating characters from 8859-1 to what it thinks the hardware is
displaying (i.e. the default code page 437).
Thank you for explanation. Any plans for the future devc-con extension?
Any tricks and comments are welcome.
Run Photon and a full-screen pterm?.. >
Could you tell something more about configuration procedure
(especialy under embedded Photon)?
Pozdrowienia,
Wojtek
Z pozdrowieniami,
Jacek
Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:
Hi Wojtek,
I don’t think devc-con supports that. Even if you managed to change the
character bitmaps on the card, devc-con will mess up your output by
translating characters from 8859-1 to what it thinks the hardware is
displaying (i.e. the default code page 437).Thank you for explanation. Any plans for the future devc-con extension?
Not that I know of. (If anyone does know of any such plans, could you
speak up please…)
Of course, there’s the possibility that someone willing to pay us money
may order it as a custom engineering job. But otherwise, I have the
feeling that it’s not considered a high-priority thing to do.
Any tricks and comments are welcome.
Run Photon and a full-screen pterm?.. >
Could you tell something more about configuration procedure
(especialy under embedded Photon)?
The experiment I made on my 6.2.1 desktop was pretty simple: from a
telnet session, I added add /usr/photon/bin to my PATH and ran Photon,
crttrap start, inputtrap start, and pterm -w100% -h100%. And it just
worked, without any special configuration.
Of course, for an embedded system you might want to find out which files
are unnecessary, and start certain pieces by hand instead of running
inputtrap/crttrap. Isn’t there a chapter in the docs that describes how
to do that?..
The experiment I made on my 6.2.1 desktop was pretty simple: from a
telnet session, I added add /usr/photon/bin to my PATH and ran Photon,
crttrap start, inputtrap start, and pterm -w100% -h100%. And it just
worked, without any special configuration.
I will ask you in another way.
I set my keyboard to the Polish layout. After it I can type Polish letters
under ped, phAB, etc. Why the same chars don’t appear on the pterm and why
‘z’ and ‘y’ chars were exchanged?
Polish layout = “typist” keyboard. Am I right?
Is there possible to change keyboard layout to programmer mode? Using the
following keys combination:
Alt + a = ±
Alt + o = ó
…
could be more comfortable.
Of course, for an embedded system you might want to find out which files
are unnecessary, and start certain pieces by hand instead of running
inputtrap/crttrap. Isn’t there a chapter in the docs that describes how
to do that?..
My embedded Photon works fine with en_US_101.kbd and en_US_101.kdef
definition files. If I change them into the Polish eqivalents - keyboard
doesn’t work at all. Why? How can I activate it?
Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:
The experiment I made on my 6.2.1 desktop was pretty simple: from a
telnet session, I added add /usr/photon/bin to my PATH and ran Photon,
crttrap start, inputtrap start, and pterm -w100% -h100%. And it just
worked, without any special configuration.I will ask you in another way.
I set my keyboard to the Polish layout. After it I can type Polish letters
under ped, phAB, etc. Why the same chars don’t appear on the pterm and why
‘z’ and ‘y’ chars were exchanged?Polish layout = “typist” keyboard. Am I right?
Yes. That’s all you mean by ‘z’ and ‘y’ being exchanged, right?
Pterm can’t display all Unicode at the same time – it only supports a
subset of 256 characters. By default, it’s the ISO 8859-1 character set
(I’m simplifying it a bit here). Setting up a Polish keyboard mapping
allows you to generate Photon key events containing characters from
outside of that subset, but pterm will ignore them. You can change
pterm’s character set to one that includes Polish characters (like
8859-2) – you can do that by building a character set description file
(see the docs for ptermcs) and pointing pterm at it (look for a Browse
button in the Customize font list dialog). You can find more details of
how pterm handles different character sets in the description of
PtTerminal in the docs.
Is there possible to change keyboard layout to programmer mode? Using the
Sure you can; it’s just that you’ll have to write the layout file
yourself. But since it’s just the US layout with a few modifications,
it should be much easier that writing the “typist” layout yourself would
be…
following keys combination:
Alt + a = ±
Alt + o = ó
…
could be more comfortable.
Perhaps (not to me – guess why it was the other Polish mapping that
made it to the Photon distribution?..). But notice that with this
mapping, you lose the ability to distinguish the letter ‘ó’ from the
hotkey Alt-o, and so on.
Of course, for an embedded system you might want to find out which files
are unnecessary, and start certain pieces by hand instead of running
inputtrap/crttrap. Isn’t there a chapter in the docs that describes how
to do that?..My embedded Photon works fine with en_US_101.kbd and en_US_101.kdef
definition files. If I change them into the Polish eqivalents - keyboard
doesn’t work at all. Why? How can I activate it?
I don’t know; my guess is that something is not configured correctly.
The Polish mapping works on a desktop system (I know it does on mine),
therefore there must be some difference between a desktop and your
embedded setup that makes it stop working. I don’t know enough about
your setup to guess which particular difference is responsible…