LordJashin Posted July 31, 2012 Share Posted July 31, 2012 (edited) You killed me adding that many files Freddy, 23.22mb, and 3 minute transfer lols. Sounds pretty cool though. Are you using google chrome or what? I see chrome.pak? 333 post ftw. EDIT: Try this in 3.36 [sCAR] program New; var A: TSCARWebClient; begin A := TSCARWebClient.Create(500, 500); A.Navigate('scar-divi.com'); end. [/sCAR] Edited July 31, 2012 by LordJashin Quote Link to comment Share on other sites More sharing options...
FHannes Posted July 31, 2012 Share Posted July 31, 2012 Yeah, embedded chromium Quote Link to comment Share on other sites More sharing options...
Janilabo Posted August 1, 2012 Share Posted August 1, 2012 Happy to see this was integrated to SCAR. Size of the chromium isn't a problem to me at all.. Works well! Thanks. Quote Link to comment Share on other sites More sharing options...
FHannes Posted August 1, 2012 Share Posted August 1, 2012 This client is actually one of the things I had in mind when designing the new client system. I'm still experimenting to find the best way to implement it though. Quote Link to comment Share on other sites More sharing options...
FHannes Posted August 3, 2012 Share Posted August 3, 2012 (edited) Right now all input is available, do note that the keystate functions may not behave properly as it's somewhat difficult to determine. Keyboard input might require some tweaking, but works overall. Let me know if there are any issues. Only TypeTextEx can input characters as CEF can't type characters with only KeyDown/KeyUp events, it does send those for regular characters though, if this ends up being an issue, let me know. Edited August 3, 2012 by Freddy Quote Link to comment Share on other sites More sharing options...
FHannes Posted August 4, 2012 Share Posted August 4, 2012 I'd also like to point out that if you have a site crashing SCAR with the TSCARWebClient,this is probably because currently the chromium embedded framework for Delphi doesn't support CEF3, which is required to render WebGL content. Once the framework is updated in the near future, there shouldn't be a problem with that anymore. Quote Link to comment Share on other sites More sharing options...