General > General Technical Chat
LTspice IV - can't drag whole area!
RoGeorge:
The UI is very productive for a CAD, use/set keys shortcuts and use them instead of clicking menus and icons. In any CAD is the same, use the keyboard or suffer.
Set M for Move, D for Drag, R for resistor, C for Capacitor, P for place Part, W for Wire, Space to fit full view, and so on, a single key press for each action or components. Use the mouse wheel to zoom, and disable schematic autodrag.
They all can be changed from LTspice's control panel, avoid CTRL or other key alterators, though I have CTRL+M for Mirror, and CTRL+R for Rotate.
eti:
--- Quote from: RoGeorge on November 08, 2022, 01:35:24 am ---The UI is very productive for a CAD, use/set keys shortcuts and use them instead of clicking menus and icons. In any CAD is the same, use the keyboard or suffer.
Set M for Move, D for Drag, R for resistor, C for Capacitor, P for place Part, W for Wire, Space to fit full view, and so on, a single key press for each action or components. Use the mouse wheel to zoom, and disable schematic autodrag.
They all can be changed from LTspice's control panel, avoid CTRL or other key alterators, though I have CTRL+M for Mirror, and CTRL+R for Rotate.
--- End quote ---
I agree. You soon get used to it after an hour or so, it’s trivial. Lacking modifier key combos is a boon; single key to learn = faster muscle memory training.
I’m still not gonna be using “Wine” though, as I explained the reason to be that I need a “solid foundation” (Win 7, and not Win XP as someone erroneously assumed I’d meant) for future software installs.
I know Dave has had a similar experience with editing suites with people telling him “you should try X software, no, you really should try, no, you really really really really need to try it!!” and with respect, as good as it is; this works flawlessly for me, and I’m happy not wasting more time on something I don’t need.
I’ve tried restoring this old HP ProBook 6460b to factory Win 7, using the original HP discs, and it has this infuriating habit of deciding to sometimes fully shut down and sometimes not, under ALL versions of Windows I’ve tried (And yes, I fully reset the BIOS).
Time sunk can’t be reclaimed, and since I am always using Linux, and the bash shell is VASTLY superior AND Ubuntu shuts the laptop down first time EVERY SINGLE time, then I’m using it and that’s that. My life is precious to me and I have a hatred of wasting it pandering to idiotic problems which are nearly always IT-based.
eti:
--- Quote from: RoGeorge on November 07, 2022, 07:13:52 am ---To install wine in Linux (Debian-like Ubuntu and such) you open a terminal and type two lines:
--- Code: ---sudo apt update
sudo apt install wine64
--- End code ---
That's all, no mess and no multi GB virtual machines.
Then you download the LTspice 64bits for Windows from its official distributor
https://ltspice.analog.com/software/LTspice64.exe
Then double click the downloaded 'LTspice64.exe' installer, and it will start and run just as if it were Windows. Nothing to adjust or to fuss around with. Nothing stops you to install other tools later (in wine, or) in a VM if you prefer so.
Then you double click the LTspice icon straight from Linux, no virtual machine to start/stop, nothing to tune.
What operating system does your PC have? Wine is rock solid nowadays, it is not like it was many years ago. Wine is also more backwards compatible with native Windows programs than the current Windows itself is. ;D
--- End quote ---
I know how to do this, but for anyone else reading this, your guide fell at the first hurdle; double-clicking "LTSpice64.exe" opens it in "archive manager"; one needs to run "wine LTspice64.exe" from a shell.
I concede that it works very well in wine... I shall test and report back if errors arise. Many thanks, I swallowed my pride and tried... (if rhyme were a crime I'd be doing time...)
[UPDATE]: The "help" (Windows "CHM" filetype) viewer DOES NOT work. Bye Bye Wine, time waster.
Rhetoric, but in case I’m “taken to task” on this (not that I care), here’s more evidence that a VM is just simpler and more reliable; I don’t care about all this “freedom” nonsense (delusional thinking) or “nasty” proprietary hogwash spiel, I want a tool to work, and a VM works as expected, wine does not. I’ve had mixed success with 🍷 wine over the years, having only seen it as “ahhh, how quaint, bless ‘em”
>> https://unix.stackexchange.com/questions/7072/wine-vs-virtualbox#:~:text=VirtualBox%20takes%20a%20lot%20more,works%20very%20well%20in%20VirtualBox.
Just use the proper, genuine tool, not a kinda-sorta-maybe halfway house like wine.
This is similar to why people buy a Mac. You can mess about with “Hackintosh” (and I have A LOT) but when you want work done, you buy the right tool for the job, and trying to get Linux to do what only a Mac can do with all these freetard tools? Uh, nope, tried since 2007, time sink!
RoGeorge:
--- Quote from: eti on November 08, 2022, 04:36:29 am ---I know how to do this, but for anyone else reading this, your guide fell at the first hurdle; double-clicking "LTSpice64.exe" opens it in "archive manager"; one needs to run "wine LTspice64.exe" from a shell.
--- End quote ---
To me it works exactly as I wrote. Double click on any .exe to run it, including installers, it even executes .msi with double click from Linux. While it is possible to start the installer from the terminal, there is no need to type "wine LTSpice64.exe". Double click the file from Dolphin and it will ask you if you want to run it, and if you allow that it will install LTspice.
Most probably wine was not allowed to make its file associations, that's probably why CHM files doesn't work either.
For me Wine worked flawless so far with zero maintenance, while VirtualBox will ask once in a year or so to update Guest addition and update both the guest and the host, had to be started/stopped manually, and VMs are rather large. But I do use them quite often, to preserve the toolchain for various devboards over the years.
My point was to say WineHQ is behaving rock solid in my experience, not to force WineHQ on everybody else.
Of course you should use whatever setup is more productive for you.
Zero999:
--- Quote from: eti on November 07, 2022, 12:21:01 am ---
--- Quote from: RoGeorge on November 07, 2022, 12:05:19 am ---If you are on Linux, Mac or FreeBSD, there is no need for VirtualBox or any other virtualisation. Install WineHQ, then download the Windows version of the newest LTspice and double click the .exe installer. This will install LTspice under WineHQ, without any virtual machine.
WineHQ is not a virtual machine, it translates low level OS calls from the ones that were destined to Windows, to OS calls for your native OS. Many other Windows games and programs will work just fine under WineHQ, sometimes even faster than on a native Windows install.
LTspice installed under WineHQ will be fully functional and able to run, save, auto-update and so on, just as if it were on a Windows machine.
--- End quote ---
Thanks, appreciate the guidance, and yes, I know Wine of old, but prefer a SOLID foundation (Windows) as opposed to "one which LOOKS like concrete but ain't" (Wine) - and I have other tools I want to install later, and cannot entertain more Linux hoop-jumping, unnecessarily (the aim is to create a schematic, not to spend a day learning obscure Linux fu, as adept as I am at it, after 20 years :) )
Every second I spend fannying around in software, is a second wasted, which I could've spend doing the actual thing, versus preparing to setup the tools to prepare the other tools to DO the thing... if ya catch my drift?
--- End quote ---
LTSpice is specifically designed to run under WINE. It's much more reliable than an emulator. It's not the same as running a random piece of software, which isn't designed for WINE.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version