Oleg Bolshakov
|
Re: Framebuffer concept in QNX4.25
|
Oleg Bolshakov
12/17/2014 8:14 AM
post112712
|
Re: Framebuffer concept in QNX4.25
Hello,
You can create at least two configurations with Photon components to achieve your target. You can disable (just do not
launch) all unneeded Photon components like pdm, pwm, etc and create PtRaw-based application maximized to whole screen.
Also you can try to launch Hydra.ms to switch to graphics mode and access framebuffer directly using framebuffer pointer
. To get framebuffer pointer you can use show_pci or show_vesa utils.
What is a reason to do not use Photon? If you describe your question more details then I'll try to suggest more
appropriate option.
Respectfully,
Oleg
15 дек. 2014 г., в 8:44:31, Honey S. <community-noreply@qnx.com> написал:
> Dear all,
> Is there any framebuffer concept in QNX4.25?
> We need to check if any graphics applications can be run in QNX4.25 without using Photon GUI toolkit support
> and by accessing framebuffer directly.
> We understood that QNX6.4.x supports SDL (libSDL) and using this we can get a framebuffer interface.
> But is SDL supported in QNX4.25?
>
> Thanking you,
> Honey S
> Senior Software Engineer
> QuEST Global Engineering Services Pvt Ltd
> Technopark
> Trivandrum
>
> Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended
recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly
prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your
systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the
recipient to make sure that it is virus/malicious code exempt.
>
> The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If
you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not
liable for any errors or omissions in the content of this message.
>
|
|
|