GithubHelp home page GithubHelp logo

Comments (7)

rafaelmardojai avatar rafaelmardojai commented on August 9, 2024 1

I don't know how is the state of auto start in Flatpak.

But for now a will add the --hidden flag to launch the app hidden.

from blanket.

 avatar commented on August 9, 2024

Thank you very much @rafaelmardojai 👍

I am using Archlinux and blanket is installed via AUR so i guess it will work.

from blanket.

archisman-panigrahi avatar archisman-panigrahi commented on August 9, 2024

blanket --hidden works with the daily builds PPA as well.

from blanket.

bilelmoussaoui avatar bilelmoussaoui commented on August 9, 2024

I don't know how is the state of auto start in Flatpak.

But for now a will add the --hidden flag to launch the app hidden.

Flatpak has a portal for autostart/running in the background.

from blanket.

rafaelmardojai avatar rafaelmardojai commented on August 9, 2024

Flatpak has a portal for autostart/running in the background.

You know what is the best way to implement this? I have to call EnableAutostart directly with D-Bus?

from blanket.

bilelmoussaoui avatar bilelmoussaoui commented on August 9, 2024

You need to use the RequestBackground dbus call https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-method-org-freedesktop-portal-Background.RequestBackground. One thing to be aware of is that the portals waits for a user interaction (approval/or not of the interaction). The way it's handled is that each portal request, sends you an object path (mostly a dbus path) that you can call and wait for a response signal. The response contains the result of the interaction (whether the user approved it or not)

from blanket.

rafaelmardojai avatar rafaelmardojai commented on August 9, 2024

You need to use the RequestBackground dbus call https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-method-org-freedesktop-portal-Background.RequestBackground. One thing to be aware of is that the portals waits for a user interaction (approval/or not of the interaction). The way it's handled is that each portal request, sends you an object path (mostly a dbus path) that you can call and wait for a response signal. The response contains the result of the interaction (whether the user approved it or not)

I see, I was looking to the wrong documentation.

You know if there are future plans to implement this at the toolkit level?

from blanket.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.