Formerly KiCAD is wrapped around wxGtk
Which happens to be a C++ toolkit
I think it is great considering the status of Qt after being bought
If you have not seen it yet there is an alternate bundle to wxGtk with an embed Python interpreter called wxPython
https://www.wxpython.org/
<PS> Specifically https://docs.wxpython.org/wx.glcanvas.1moduleindex.html
where an enthusiastic folk can render any sort of view in 2 minute pythonish
I am not a python fan much because I deal with PERL for more than 20y+..
so last time I checked (what they call now legacy wxPython) you could
just as in PERL object oriented wrappers (auto made with higher order converters
e.g. formerly http://www.swig.org/) just interface any sort of API .
Done that in PERL Gtk and that is a very very powerful
method to achieve such short goals on large projects..
<END PS>
Well if anyone for some reason
Can not see how you open a secondary
view of a large pcb using that method..
Well that is beyond what i can reason
Method is explained to the best i can
with my own setup and extensive considerations...
Paul
I don't think you have much to contribute to the OP's question.
But I do enjoy your Haikus.
Not sure if I understand ...
What? sitting and wait some Python sweet heart craft a thing
that attach the KiCAD API to display a secondary window?
Wait even longer so the underlay toolkit will care about Xinerama
support ( instead of tinkering that wayland confused side track ) ?
What the reason to wait .. I had that dual display session working
on the bench w/2 SVGA monitors.. used to be simpler because
the setup required less GPU vendor support and you could mix
a dozen different brands SiS, ATI, S3, Matrox, Trident...
they all died and we are doomed to 2 may be 3 gpus of choice.
Chances are that mixing their crappy drivers won't even boot.
So dual display - being Xinerama or not - are still feasible
with some careful considerations as explained.
If the OP will sit and wait some Python thing or some hacks
on the toolkit... well I can not argue.
I have mine already working
I haven't seen an application that uses X Windows in ages. It's a dead technology.
Formerly KiCAD is wrapped around wxGtk
Formally (not formerly, as this information is current)
Kicad already uses wxPython -- it's how Kicad presents the python scripting console!
perl? That's hilarious.
Dude, you still haven't figured out that the underlying issue is that Kicad displays the layout in only one view. If someone stepped up and proposed how to have the application display two separate views of the layout, then it can be implemented. It's not a python thing at all. It requires support at the toolkit level.
I haven't seen an application that uses X Windows in ages. It's a dead technology. Nobody cares
Clumsy workaround: open the same project in two instances of KiCAD, turn off autosave, and take care to do a save+reload cycle every time you are making a change to the design. Not nice, but if you really only need two independent views or zoom-levels of the same things, this works. If all you do is reviewing a design, not editing it, you are probably fine.
Folks, I don't think any of this is helpful, you are completely off topic...
Maybe it would be good if a mod could lock this thread?
Short answer: You can currently not open two independent views in KiCAD, we all agree it would be great.
Clumsy workaround: open the same project in two instances of KiCAD, turn off autosave, and take care to do a save+reload cycle every time you are making a change to the design. Not nice, but if you really only need two independent views or zoom-levels of the same things, this works. If all you do is reviewing a design, not editing it, you are probably fine.
Sorry if this is not the kind of answer you would like, but hey, you can always contribute to PCBnew and add a 2-window/2-viewport feature...
You haven't yet offered a solution - only bragged about having one and gone on long pointless rants about 'losing X11' when most everyone still uses X, complete with misinformed unrelated rants about systemd being 'designed for autologin'.
So, yes, clumsy overblown workaround which doesn't resolve the fundamental issue of KiCAD not being designed to handle having the same project open by two sessions. Plus rant and thinly veiled insults. Amazingly, you didn't go on about perl in this post for a change.
Open both your sessions. In session 1, run a new trace. Does it appear in session 2?
Save session 2. Close both. Open them. Is the trace still there?
Open both your sessions. In session 1, run a new trace. Does it appear in session 2?
Save session 2. Close both. Open them. Is the trace still there?
Well I think you are reasonably clever enough
to understand that ...
- WITHOUT MESSING A SINGLE LINE OF CODE...
- THERE IS A WAY TO SEE 2 or 3 PARTS OF YOUR PCB..
- change them at will compare them.. save them wo messing..
What you want obviously is a DEEP modification of the project...
Which I am afraid to disappoint you should not happen so soon.
Although possible.. it should take time and introduce far
more bugs the folks can handle.
If you prefer to stay sit on that... your call
Paul
And as explained far earlier in the thread, you can do this without all your messing about and whining about systemd and wayland. But then you don't get to rant about them.
And as explained far earlier in the thread, you can do this without all your messing about and whining about systemd and wayland. But then you don't get to rant about them.
My dear... get yourself a cup of coffee.. strong..
You are REQUIRED to have your apps compiled with full X11 stack.
You are REQUIRED to drop systemd for the sake of having no thingy
starting unwanted stuff in your setup..
Did your took you meds today?
I am not ranting.. these are requirements..
Paul
Errr.. required by what? Why?
You are REQUIRED to fully explain yourself and provide references. You're going to need a lot of coffee.
So what you're telling me is that due to 'requirements', I can't take a stock install of a systemd- and wayland-crippled distro like Ubuntu (I even enabled autologin, which is off by default and a single click to change! Such tinkering!), install the latest version of KiCAD, and open two instances of pcbnew on the same file?
Looks like I just did exactly that to me. No perl. No custom compiling. No chroot. No messing with X config. Running under Wayland, on a systemd distro, with autologin enabled. HOW?!
So what you're telling me is that due to 'requirements', I can't take a stock install of a systemd- and wayland-crippled distro like Ubuntu (I even enabled autologin, which is off by default and a single click to change! Such tinkering!), install the latest version of KiCAD, and open two instances of pcbnew on the same file?
Looks like I just did exactly that to me. No perl. No custom compiling. No chroot. No messing with X config. Running under Wayland, on a systemd distro, with autologin enabled. HOW?!
No my dear YOU ARE SAYING this.. to make me look like fool
As you always do.
I have not figure out what is your problem ... yet.
You can do all this.. it is your head to bang..
The solution I presented is safe - you will not mess your files..
as long as you (like my 6y old nephew) do not insist in making
things the odd way..
Paul
*sigh*
You've yet to explain, then, how having two instances of the program open the same file doesn't pose a risk of one overwriting changes made in the other. And how that's connected to X.
*sigh*
You've yet to explain, then, how having two instances of the program open the same file doesn't pose a risk of one overwriting changes made in the other. And how that's connected to X.
That is the easiest part as long as you ask politely ..
The reason for that is that THEY ARE NOT 2 INSTANCES
of the "same program on same file"
While one runs on regular file system the other "instance"
is running on my chroot scratch using the newest wxGtk toolkit
(aka 3.1 while other 3.0)
My workstation have such thing ready..
So they both run concurrently without even knowing about each other.
Hope to satisfy your persistent rant about all things i post..
Paul