Thread: Disable screen capture function in Primo

It is a "stock" Civic pack with an added 800x480 res from another package in the data.zip.

The problem is when Primo is minimized and I am in the shell that the device comes with changing brightness for example, when I maximize Primo again it takes a screenshot with the "Screen Captured" box appears. It probably makes some virtual input to put Primo in the foreground by tapping on that specific area, and it is really annoying and fills up the storage for no reason. Disabling the Capture screen or forcefully disabling it with the sys line didn't help. It does the same with the original 480x272 Civic pack.

Tried with [Only registered and activated users can see links. ] and it doesn't register anything when tapping the top left corner. Which is good. If I am not mistaken, it is some invisible UI element, the problem is finding it.

Your info is definitely better. Gotta find a solution to change that date to show 2023.

Where does it save the screen captures?
If it's Primo responsible they usually are stored somewhere in Primo's directory, the folder captures in the root directory I see in one of the WinCE versions I use.
If it's Windows doing it they might be found elsewhere, and it would probably also show the same behaviour without Primo running.

But even when Screen Capture is disabled in the extra settings and the sys.txt line provided by lunapark added it still takes a screenshot when tapping near the battery icon

That is exactly what I found when assisting someone to disable it with the Tomsoft skin, it just ignored those settings and the only way I found to completely disable it was to comment out that line in the .ui file.
From memory I think adding the line 'capture=0' to sys.txt stopped it from saving the screen capture anywhere but the popup saying the screen had been captured still appeared.

In the root, where the primo.exe is. Definitely not Windows because I tried with other full screen programs. It does save them even with the line added.

Yep ok, sounds like it's Primo itself not Windows, and I imagine it's one of the .ui files the function is in.
I guess it'll have to be found and commented out to stop it.

Perhaps try searching navigatemap.ui for <BUTTON screen_captt or maybe <BUTTON screen_captt class=txt_20 or maybe even some more of that line I commented out above, to see if you find anything that might be it.

@Gjon
You will temporarily place this in the sys.txt, this will allow us to obtain technical information on the different stages of the execution of primo (no personal data is collected during this operation, only technical data on the progress of primo.)

[debug]
log_1="Gjon_log.txt::5"

you will start primo normally then carry out the various operations leading to the unwanted screenshot, then you will exit primo normally using the button on the main panel

you will retrieve the previously named log file from the exe directory to place it as an attachment in a message

remember to deactivate the log line in this way because it could be used later

[debug]
;log_1="Gjon_log.txt::5"

When you have posted the log file and deactivated the sys.txt line, remember to delete it from the root directory of your primo for new future use.

if no information leading to your problem is found in the log, I will provide you with an unmodified data.zip which will allow you to determine if the capture originated in yours.

If the problem disappears with this data.zip, you can either keep it as is and make customizations externally, or send us your data.zip to find the origin of the unwanted capture.

Originally Posted by lunapark

......if no information leading to your problem is found in the log, I will provide you with an unmodified data.zip which will allow you to determine if the capture originated in yours.

If the problem disappears with this data.zip, you can either keep it as is and make customizations externally, or send us your data.zip to find the origin of the unwanted capture.

Gjon mentions above

Tried with [Only registered and activated users can see links. ] and it doesn't register anything when tapping the top left corner.

Tends to suggest it's within Gjon's data.zip.
I was going to suggest Gjon gave us a look at the data.zip but didn't because it contained contact info that they probably wouldn't want shared with anyone.
Perhaps they could give us a look at just the ui files from common\ui folder and 800x480(or whatever resolution)\ui folder, no identifying stuff in that as far as I know.

I'm sure I remember with iGO8 there used to be a way to make iGO8 run like it was using a skin, even if there was no skin in the content\skin folder, by putting the contents of a skin in the branding.zip folder.
No idea of that works in Primo or not though as I've never tried it, might be somewhere else to look for the code that's causing it?

It is interesting that I have been using this package and this emulator for years and I have never noticed such behavior. And not just this package.
Clean sys file, minimal data.zip, with or w/o skin no matter. I don't have an option to minimize in any variant although I use multitasking in emulator

not being able to determine the origin of the problem with the little information, what I can suggest is to simply block the screenshot in all circumstances if it is indeed of origin due to an action since first

by redefining the function which calls on the screenshot primitive not only will the message no longer appear but no image will be created on disk.

in zip form, it is obviously a ux which will be used in the directory dedicated to this use.

it's minimalist but can temporarily solve Gjon's problem without any change on his primo

You're still hiding content like a snake its legs

I clicked the previous evening in the emulator as much as you want, on both the 800 and the 480 package, in every corner, started additional processes in background, etc...
The data zip I'm using is the same, the redundant resolutions are thrown out. These are the data.zip posted here as a minimum with both packages.

Post the sys file, upload those modifications without your personal elements so we can take a look at them.