CF V2 and image rotation

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On the PDC slides about .Net CF V2, I saw "Image rotation" and "Image saving" will be implemented
I downloaded the Whibdey tech preview, the "save" method is well present but not the rotation

So please choose the right proposition about rotation in CF V2
- won't be implemente
- is not implemented ye

Thanks.
 
Sat through Australia MDC today so this is homework to make sure i was
listening :)

I will add a third
- it is implemented

I believe and correct me if I am wrong Chris Tacke, but the hardware does
the rotation not the framework, you have to make sure your form will be able
to rotate.

In v2 it will auto handle it for you but you can assist the resize event if
you dont like the outcome.

- James McCutcheon
 
I believe and correct me if I am wrong Chris Tacke, but the hardware does
the rotation not the framework, you have to make sure your form will be able
to rotate.

Well... I am not Chris Tacke, but I'll try to comment on this stuff :)
If we're talking about screen rotation then it'd be done either on a
hardware or video driver level.

In the case of image rotation on the currently existing PPC
hardware/software it'd be possible on the software/framework level.
 
You're right Alex I'm talking about bitmap rotation not screen
So my question is still valid: why this is not into the CF V2 tech preview
Or where, if I miss it in the System.Drawing.Image class ?
 
It's not part of the original question, but I'll throw in some more info
(becasue info is good).

Rotation can be done 2 ways, either through hardware or software. The most
efficient way to "rotate" permanently is to use an LCD that supports the
orientation you want (there are lanscape and portrait LCDs). The other
efficient way is to physically route the display signals rotated through the
LCD cable.

The third would be to use a micro or some piece of hardware to condition the
signal after it leaves the display driver and before it reached the panel.

A fourth is to use a video accelerator/framebuffer that supports rotation.

All of these are good *if* you can affect hardware design changes.

The next step is through SW. If the device has an accelerator that supports
rotation, a call to the driver *may* be all that is needed. I say may
because even if the chip supports it, the driver still must implement the
feature.

This is a good point ot digress into display controllers. Many processors,
like the SA1110 and PXA255 have internal controllers. They can driver the
LCD themselves without any hardware, and this is typically done becasue it's
cost effective. The downside is that the processor must handle all video
updates plus run all of your apps, so performance can be a problem,
expecially at 640x480 and higher. Greater color depth exacerbates the
problem.

The OEM can add a separate accelerator to handle all of this, which gives
much better video performance and capabilities, but at a cost of $ and board
real-estate.

Yet another way to achieve rotation, which is not great, but the only option
if you have no hardware mechanism to support rotation, is a rotation driver.
The driver either replaces or works with the current display driver. It
takes the display data and does a matrix translation on it to rotate the
bits, then sends it off to the display frame buffer.

While this works, it's a hell of a lot of math, and it usually gives a
pretty bad perf hit. Using Intel's IPP helps if you're using an Intel chip,
but it still can't replace the perf from a separate part.

There you go. The class in Displays 101 is now over. :)
 
Romu,

There's a lot of nice stuff planned for CF2 that isn't in the current tech
preview, so if you've seen some feature announced but it's not there yet,
don't assume it won't be there later.
 
Chris,
The OEM can add a separate accelerator to handle all of this, which gives
much better video performance and capabilities, but at a cost of $ and board
real-estate.

Are you aware of any OEM's planning this ?? or a plethoria of NDA's stopping
telling ??

What was interesting today was listening to James Pratt talk about the
design target of 200ms per page load that ISV's should be attempting to
reach , now I havent gone and attempted to work out this for a device
running .NET CF but I reckon you wouldnt have to add many controls to reach
that specially under a weaker processor unit. It would be nice to see better
video performance in devices
 
I'm not aware of any PPC with hardware acceleration, but we (ADS) have CE
devices with accelerators running 16-bit color and resolutions of 1024x768
and they play video at 30fps. Looks beautiful on a 19" LCD.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top