Search results

As mentioned in the main post, running App.exe --load-extension=myextfolder from windows command prompt works well and the extension is loaded as expected. That would mean CEF does support loading unpacked extensions from commandline - it is just that the same parameter does not work when added...

This flag doesn't prevent popups from appear either.

WebSocket connection is somehow rejected (probably the same reason as why visiting localhost:9000 shows a blank page) so I cannot use it. Anyway, I managed to run CDP commands by creating my own chrome extension, but need some help loading it on app startup. I have posted a bug thread here.

Hello, I developed a small chrome extension that lets webpages to call chrome extension APIs in the background (thus enabling me to run CDP commands), but am not able to load it with the EXE app created by ExeOutput. I am trying to load the unpacked extension from its folder, NOT the packed CRX...

Does not help, the popup(s) still appear.

I found how to reproduce this issue - and why it happens: When the app unexpectedly crashes, the next time we open it the "Continue where you left off" setting kicks in and shows the previously open tab(s) which is the app homepage. Upon visiting chrome://settings/onStartup we can see that...

Also the random popup issue still remains - you can see the main app window (maximized) in the background, and the same index page in an unwanted popup on application startup. (Using latest CEF 131.3.5 with EXORun.dat patch and PHP 8.4)

Understood. I think it was 8.3, but not entirely sure. Will update if I face that error again.

Using the latest ExeOutput / CEF versions. Also using the EXORun.dat patch provided by you. I have enabled Devtools and Devtools in Popup in my rendering engine properties. When I click Developer Tools from the context menu, it works fine (see below image). But when I visit...

I think I found the problem. I was using the old .exop file (i.e. already existing exop project file with the latest ExeOutput). I created a new project from scratch with the exact same settings from existing project, and then this issue was resolved. I guess at least some part of the old .exop...

2 completely different EXOP projects / exe files.

Update: Also tried with CEF v109 (support for Win7) in both apps, with and without the patched EXORun.dat file - the issue persists. It seems that the “Just a moment, please…” issue might be related to ExeOutput v2024.2.0 itself and not CEF. Please guide further - I just want to be able to...

Overwrote EXORun.dat file with the one you provided here, compiled both appas again but the issue persists. After opening either one app first, the second app gets stuck at “Just a moment, please…” screen. Although the “about:blank” popup does not appear anymore.

Hello, Just upgraded to ExeOutput 2024.2.0, compiled 2 different projects. Now I cannot run both those EXEs at the same time - only one of them can run at a time. Notes: They are completely different projects with different application GUIDs. None of them use DevTools. Either of these apps...

Thanks for a prompt reply. Although this is more of a feature request than an issue. ExeOutput is already passing port 9000 as an argument to chromium, so to change it a simple global variable or a port setting in the editor should be fine.

So, is this going to be fixed or not?

Context: I want to develop a real-time web app that uses WebSocket. One app will be running on main PC (let’s call it server) - it will start a websocket listener in PHP. Other “client” app will be running on other PCs in the same network, and will connect to the main PC via javascript’s...

The Application Settings > Rendering Engine tab allows to turn on Developer Tools, and when the application starts, the chromium instance is started with arg --remote-debugging-port=9000 and devtools can be accessed at http://localhost:9000 My concern is this: I have developed an app (let’s...

Hi @gdgsupport any updates on this??

Hi, I am using ExeOutput 2020.2, we have an issue with javascript prompt() function. The input box in the prompt() function is not the fixed size, and gets longer with longer message. It also causes issues when we have new lines in the message. For example see these screenshots This...