EDA > KiCad

KICAD and dual monitors

<< < (11/12) > >>

PKTKS:
No my dear...

IT IS A WHOLE DIFFERENT SYSTEM ...
New glibc  new boost  new everything..

It is a whole environment as said

100% safe thing

Running on the same workstation..
SYSTEMD FREE and far from wayland mess

I deal with 8 KiCAD versions... 4 stable wxGtk branches
and **ONE** a single one unstable entry system.

Currently working under GCC10 LLVM12 MESA 20 and boost 1.76

Paul

Monkeh:
And that's all irrelevant, because the end result is you have another instance of a program operating on a different file. The rest is unnecessary, and it has nothing to do with systemd or Wayland. You could use the exact same binaries running in a chroot or any other form of container to achieve your isolation, and the isolation isn't even needed because they are different files.

Your use-case of running multple different versions of the software is not relevant to the thread. Your hatred of systemd, Wayland, or any other piece of software is not relevant to the thread.

In the current state of KiCAD there are two simple methods to gain a limited second view of a PCB or schematic:

* Disable autosaves, remove the lock files, and run a second instance (dangerous).

* Make a second copy of the project and open it with a second instance of the tool (safe enough).
Your method is the second with additional complications fueled by other specific requirements and/or your own desires.

PKTKS:

--- Quote from: Monkeh on July 07, 2021, 05:05:59 pm ---And that's all irrelevant, because the end result is you have another instance of a program operating on a different file. The rest is unnecessary, and it has nothing to do with systemd or Wayland. You could use the exact same binaries running in a chroot or any other form of container to achieve your isolation, and the isolation isn't even needed because they are different files.

Your use-case of running multple different versions of the software is not relevant to the thread. Your hatred of systemd, Wayland, or any other piece of software is not relevant to the thread.

--- End quote ---

If that makes you happy... ok

all is irrelevant... 

unless that I fetch them from the the same  NAS server  every time
I start to deal with versioning... alas.. they are instantly checked in
and automatic checked out... upon use.

thanks to PERL mods to CVS or SVN

Paul

PKTKS:

--- Quote from: Monkeh on July 07, 2021, 05:05:59 pm ---
Your hatred of systemd, Wayland, or any other piece of software is not relevant to the thread.


--- End quote ---

Nah.. none hatred at all..

I made a MINT system to my 6y old nephew play games..
That is exactly made for him..

POTTERIX systems are for that kind of use.

he just loves it..  :popcorn:

Me too watching his grin  ^-^
Paul

Zero999:

--- Quote from: PKTKS on July 07, 2021, 05:09:04 pm ---
--- Quote from: Monkeh on July 07, 2021, 05:05:59 pm ---And that's all irrelevant, because the end result is you have another instance of a program operating on a different file. The rest is unnecessary, and it has nothing to do with systemd or Wayland. You could use the exact same binaries running in a chroot or any other form of container to achieve your isolation, and the isolation isn't even needed because they are different files.

Your use-case of running multple different versions of the software is not relevant to the thread. Your hatred of systemd, Wayland, or any other piece of software is not relevant to the thread.

--- End quote ---

If that makes you happy... ok

all is irrelevant... 

unless that I fetch them from the the same  NAS server  every time
I start to deal with versioning... alas.. they are instantly checked in
and automatic checked out... upon use.

thanks to PERL mods to CVS or SVN

Paul

--- End quote ---

Please allow the forum software to wrap your posts, rather than adding needless line breaks, which make your posts difficult to read. If you prefer shorter lines, just resize the window. Please don't inflict it on everyone!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version