In electron, I can easily create a kiosk window by just adding a param kiosk: true.
But in tauri, is there any way to achieve that? I searched their official doc and couldn't find any.
Note: Here I'm referring to creating a window in fullscreen without topbar/ header and borders and it prevents the users to interact with other OS functionalities unless the user exists/ closes the app.
In tauri.conf.json you can find and modify window params like
"windows": [
{
"fullscreen": true,
"height": 600,
"resizable": true,
"title": "main",
"width": 800,
"alwaysOnTop": true,
"maximized": false,
"decorations": false
}
]
for mas details read this: https://tauri.app/v1/api/js/window/#windowmanager
Related
Is there a way to enable Microsoft Edge extensions during debug sessions? This is a Vue 3 application and I'm using the following launch.json:
{
"name": "Frontend",
"type": "pwa-msedge",
"request": "launch",
"url": "https://localhost:8080/",
"webRoot": "${workspaceFolder}/src",
"breakOnLoad": false,
"sourceMaps": true,
"pathMapping": {
"/_karma_webpack_": "${workspaceFolder}"
},
"sourceMapPathOverrides": {
"webpack://vue4/./src/*": "${webRoot}/*",
"webpack://vue4/src/*": "${webRoot}/*",
},
},
For some reason, Microsoft Edge does not load any extensions when I press F5 in VSCode. Not only that, there is no extension shown in Edge Settings either. Looks like VScode instructs Edge to load with some no-extensions argument, but I can't figure out where and how to change that.
I'm primarily concerned about the Vue tab in DevTools. This tab (and all other extensions) loads automatically when I open Edge normally, but not when launched from VSCode.
I'm using the selenium IDE for Chrome on Mac Big Sur. I want to add a puse in between commands to see why something isn't executing properly. This is in my ".side" file
}, {
"id": "32f35ed7-1a28-4540-a93d-3cb8ba0e012a",
"comment": "",
"command": "pause",
"target": "",
"targets": [],
"value": "100000"
}, {
I have put a really high value but when I play back my test, it just breezes through it without pausing at all, although it tells me the command was successfully run
What's the right way to pause my test?
Use Target instead of Value, Like below
Target: 100000
instead of
value: 100000
Also,
Set speed to fastest (Actions --> Fastest), otherwise it won't work.
I'm building an electron app, and the above image on the left is how my icon looks in the app when i'm testing it with electron and on the right is after I've compiled it into an executable using "yarn dist".
(these are screenshots of them from my windows bar at the bottom of the screen).
It seems like the resolution of the icon in the executable is worse than in the raw electron app. The file itself is quite high resolution:
The icon is called during development by the "main.js" file:
mainWindow = new BrowserWindow({
// frame: false,
title: "Collector: Kitten " + app.getVersion(),
icon: __dirname + "/logos/collector.png", //<--- This line
webPreferences: {
//contextIsolation: true, //has to be false with the way I've designed this
enableRemoteModule: true,
preload: path.join(__dirname, 'preload.js'),
worldSafeExecuteJavaScript: true
}
})
And is identified by the builder in the package.json "win":
"build":{
"win": {
"target": "nsis",
"icon": "logos/collector.png"
}
}
Is there a way to prevent this loss in resolution when using the electron-builder?
I solved this by converting the .png into a .ico file and using that instead.
I moved to VSCode from ST3 about 6 or 7 months ago now and overall am loving it. But I'm really struggling with inconsistencies in how Emmet/VSCode expands text...
For example: (these examples are as per the cheat sheet)
fl should give me float:left, but instead i get flex: gif
m:a should give me margin:auto - although since ST3 i've always used m- for this. However in VScode: I get max-block-size: gif
ttu should give me text-transform:uppercase, but instead I get text-underline-position:
p20-40 should give me padding: 20px 40px but in this case, nothing happens - doesn't recoginize it at all
w100p should give me width:100% but again, doesn't even recognize it <-- probably the most annoying one because I use this so often.
and even HTML borks out quite often: .div-class becomes .div-class<?php <-- no idea whats going on here... gif
It almost seems that VSCode has its own built-in Emmet, which is always conflicting with actual Emmet. I'll be the first to admit that it might be a conflicting option in my settings.json, so here is my settings file:
{
"editor.tabSize": 2,
"editor.minimap.enabled": false,
"editor.acceptSuggestionOnEnter": "smart",
"editor.wordBasedSuggestions": false,
"editor.quickSuggestions": {
"other": true,
"comments": false,
"strings": true
},
"editor.tabCompletion": true,
"editor.renderWhitespace": "boundary",
"editor.snippetSuggestions": "top",
"editor.occurrencesHighlight": false,
"editor.selectionHighlight": false,
"editor.renderIndentGuides": true,
"editor.autoIndent": true,
"php.suggest.basic": false,
"php.validate.executablePath": "/usr/local/php5/bin/php",
"workbench.colorTheme": "Bimbo Theme",
"workbench.iconTheme": "vs-seti",
"workbench.startupEditor": "none",
"workbench.editor.tabCloseButton": "left",
"workbench.commandPalette.preserveInput": true,
"workbench.tips.enabled": false,
"window.zoomLevel": 0,
"git.enableSmartCommit": true
}
I have removed settings relating to font sizes and themes etc.
Other Info:
VSCode Version 1.15.1 (1.15.1)
Extensions
Would really appreciate it if someone who isn't experiencing these issues could share their settings file so I can fix my frustration and carry on loving VSCode?
Thanks :)
That's because Emmet is interfering with autocomplete. Try typing any of these commands and execute from command palette Emmet: Expand Abbreviation.
You can remap keybinding for emmet command editor.emmet.action.expandAbbreviation
You can disable autocomplete for css (to show autocomplete when needed Trigger Suggest Ctrl+Space)
"[css]": {
"editor.quickSuggestions": {
"other": false,
"comments": false,
"strings": false
}
}
From version 1.16 August 2017 you can move emmet snippets on top and still have autocomplete:
"emmet.showSuggestionsAsSnippets": true,
"editor.snippetSuggestions": "top"
I'm trying develop Google Chrome App(or extension, not sure) to use DigitalPersona fingerprint reader on Windows.
Following :
https://developer.chrome.com/apps/usb
https://github.com/GoogleChrome/chrome-app-samples/tree/master/usb
var DEVICE_INFO = {
"vendorId": 1466, //0x05BA
"productId": 10 //0x000A
};
chrome.usb.findDevices(DEVICE_INFO, call_method);
Result is "App was granted the 'usbDevices' permission, but device not found".
p.s. the usb information above was found in windows device manager.
Don't know why this happened.
Does Google Chrome not support DigitalPersona fingerprint reader?
p.s. Chrome://inspect said "No devices detected."
The content of manifest.json is the same as the example of knob, but vendorId and productId:
{
"name": "USB Spinner Sample",
"version": "0.3",
"manifest_version": 2,
"minimum_chrome_version": "23",
"app": {
"background": {
"scripts": ["background.js"]
}
},
"permissions": ["usb"],
"optional_permissions": [ {"usbDevices": [{"vendorId": 1466, "productId": 10}]}]
}
As noted on the usb-label-printer sample Chrome App:
Some Windows device drivers take ownership of the device and don't allow Chrome to connect to them. If openDevice or findDevice doesn't work for you, you can try to use a generic low level driver instead.
This theory was confirmed by chiahao, as installing a generic low-level USB driver with the Zadig tool resolved the problem.