On Oct 11, 6:06 am, andie <andiekurnia...@gmail.com> wrote:
> Hi guys,
>
> I got a weird problem with the CameraCaptureDialog feature.
>
> I am using an i-mate JAMin device to develop an application for one of
> my client. The solution structure contains several projects (one
> Windows Application Type and 2 Class Library classes).
>
> I called the CameraCaptureDialog from one of the ClassLibrary classes.
> It throws InvalidOperationException.
>
> I then tested using a new solution with a single Windows Application
> project to test the CameraCaptureDialog itself. Just want to make sure
> that CameraCaptureDialog is supported. Using the exactly same
> properties to call the CameraCaptureDialog, the later works.
>
> Anyone has any suggestion to get a workaround on this?
>
> Regards,
> Andie

On 11 oct, 10:05, CraigGRA <Craig...@gmail.com> wrote:
> On Oct 11, 6:06 am, andie <andiekurnia...@gmail.com> wrote:
>
>
>
>
>
> > Hi guys,
>
> > I got a weird problem with the CameraCaptureDialog feature.
>
> > I am using an i-mate JAMin device to develop an application for one of
> > my client. The solution structure contains several projects (one
> > Windows Application Type and 2 Class Library classes).
>
> > I called the CameraCaptureDialog from one of the ClassLibrary classes.
> > It throws InvalidOperationException.
>
> > I then tested using a new solution with a single Windows Application
> > project to test the CameraCaptureDialog itself. Just want to make sure
> > that CameraCaptureDialog is supported. Using the exactly same
> > properties to call the CameraCaptureDialog, the later works.
>
> > Anyone has any suggestion to get a workaround on this?
>
> > Regards,
> > Andie
>
> I have previously had problems with this when a device is low on memory- =
Masquer le texte des messages pr=E9c=E9dents -
>
> - Afficher le texte des messages pr=E9c=E9dents -

On Oct 12, 3:09 am, Fabien <fab_00_2...@msn.com> wrote:
> Hi,
>
> Yes, me too, it was a problem of memory, if you kill some process, it
> will be probably OK.
>
> Fabien Decret (Device Application Development MVP)
> Windows Embedded Consultant
>
> ADENEO (ADESET)http://www.adeneo.adetelgroup.com/|http://fabdecret.blogsp=
ot.com/
>
> On 11 oct, 10:05, CraigGRA <Craig...@gmail.com> wrote:
>
>
>
> > On Oct 11, 6:06 am, andie <andiekurnia...@gmail.com> wrote:
>
> > > Hi guys,
>
> > > I got a weird problem with the CameraCaptureDialog feature.
>
> > > I am using an i-mate JAMin device to develop an application for one of
> > > my client. The solution structure contains several projects (one
> > > Windows Application Type and 2 Class Library classes).
>
> > > I called the CameraCaptureDialog from one of the ClassLibrary classes.
> > > It throws InvalidOperationException.
>
> > > I then tested using a new solution with a single Windows Application
> > > project to test the CameraCaptureDialog itself. Just want to make sure
> > > that CameraCaptureDialog is supported. Using the exactly same
> > > properties to call the CameraCaptureDialog, the later works.
>
> > > Anyone has any suggestion to get a workaround on this?
>
> > > Regards,
> > > Andie
>
> > I have previously had problems with this when a device is low on memory=
- Masquer le texte des messages pr=E9c=E9dents -
>
> > - Afficher le texte des messages pr=E9c=E9dents -- Hide quoted text -
>
> - Show quoted text -