Glitch

[paraflu]

I've built an application using cef and when I go over an input field with the mouse I get the glitch in the attachment.

Same with the clientapp test application and on every other machine I've tried.

I've search on forum and web for some information or issue but nothing found.

Some one have the same issue?

The version is 3.1750.1738.0

Thanks

Andrea

[magreenblatt]

What OS? Does the problem reproduce with the cefclient test app downloaded from http://cefbuilds.com?

[paraflu]

OS is Windows7 but also in Windows XP and Windows2003 Server (Terminal client).

Now I'll give a try to cefbuild.

[paraflu]

The dev version hasn't the problem. I've tried also the cefclient of my version and there is no problem.

So only the one built from my machine have the problem.

I need to reset all and retry the building process.

thanks

[paraflu]

When I built the cefclient I get this error

Impossibile aprire il file inclusione 'winapifamily.h': No such file or directory

So I've found the header in the directory C:\Program Files (x86)\Windows Kits\8.1> but if I build the package with this header I give this error

1>C:\Program Files (x86)\Windows Kits\8.1\Include\um\winnt.h(5671) : error C2220: avviso utilizzato come errore - nessun file 'object' generato
1>C:\Program Files (x86)\Windows Kits\8.1\Include\um\winnt.h(5671) : warning C4163: '__cpuidex': non disponibile come funzione intrinseca

I need to download the 8.0?

Thanks

[magreenblatt]

I need to download the 8.0?

It should work using 8.1. Check the cefclient project configuration to see if it's hard-coding a path to the 8.0 API.

[paraflu]

Strange I've tried to modify libcef_wrapper path with 8.1 sdk but I've the same problem. I've updated 8.0 and now compile. The glitch problem remain in my application but dissapered in cefclient app


If someone have any idea is welcome!

Andrea

[paraflu]

I've realling libcef.dll, libcef.lib ecc from the release branch but I've the same glitch problem.

I compile with vs2008 version, I've tried so many configuration settings... but none resolve!

[magreenblatt]

Does the manifest for your application match cefclient? Cefclient includes cefclient.exe.manifest and compatibility.manifest. You can view the manifest resource compiled into the executable using Resource Hacker.

[paraflu]

This is cefclient manifest

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
    <dependency>
        <dependentAssembly>
            <assemblyIdentity type="Win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*"/>
        </dependentAssembly>
    </dependency>
    <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
        <security>
            <requestedPrivileges>
                <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
            </requestedPrivileges>
        </security>
    </trustInfo>
    <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
        <application>
            <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
            <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
            <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
            <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
        </application>
    </compatibility>
</assembly>

and this is mine

Code: Select all

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
  <dependency>
    <dependentAssembly>
      <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
    </dependentAssembly>
  </dependency>
</assembly>

The only difference is <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> this can resolve the glitch?