Vojtěch Bubník comments

Results 185 comments of


                                            Vojtěch Bubník

Desktop integration could be better documented or less frictionful

At the end of the day, we implemented desktop integration into PrusaSlicer as part of the "Install wizard" process. This also allows our users to switch between PrusaSlicer versions, to...

Desktop integration could be better documented or less frictionful

@azubieta > This is precisely what libappimage is for, you may take a look at it on https://github.com/AppImage/libappimage/ Cool. How come we did not stumble over it?

Desktop integration could be better documented or less frictionful

> appimaged is a workaround. It is better to have native support in the desktop environment and file manager. AFAIK appimaged is not being promoted by common distros to be...

Select which executable inside an AppImage to run based on argv[0]?

I wonder how the AppImage handles multiple processes started 1) From the same AppImage. We see that the AppImage squashfs is mounted twice. Do the two processes then share their...

Select which executable inside an AppImage to run based on argv[0]?

Thanks @probonopd @TheAssassin for your comments. > > From the same AppImage. We see that the AppImage squashfs is mounted twice. Do the two processes then share their program space...

Select which executable inside an AppImage to run based on argv[0]?

> Or am I thinking too simplistic here? I am worried about race conditions when the "primary" is closing up while the "secondary" is starting a binary from the already...

Select which executable inside an AppImage to run based on argv[0]?

> Wouldn't it be sufficient to add a couple of sleeps in the checking code? I would not sleep well doing that. In my experience, if something could get wrong,...

Select which executable inside an AppImage to run based on argv[0]?

This is the process tree of our current master packed in AppImage, where the first process started one instance of another PrusaSlicer and one instance of a new G-code viewer...

Select which executable inside an AppImage to run based on argv[0]?

Now it is getting interesting. The process tree in my previous post is real. The AppImage starter gets daemonized while the prusa-slicer application is execve'd on the initial process, therefore...

Select which executable inside an AppImage to run based on argv[0]?

The timeout seems to be off in the AppImage runtime. It should be sufficient to add the timeout parameter to fusefs_main() to shut down by polling the number of open...