http://bugs.winehq.org/show_bug.cgi?id=32114
Bug #: 32114 Summary: Dialog resizing glitches, slow panning when zooming, minor traces Product: Wine Version: 1.5.16 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: testelor@yahoo.com Classification: Unclassified
Hello
And my apologies for any language errors, I'll "do my best", though.
- I -
Since version 1.5.12 (Linux Mint 13, current version 1.5.16), LTspice seems to suffer from a slow "click-and-drag" panning after zooming, which seems to be related to font smoothing. Not being a guru, I reverted to the last version (1.5.12) which, even if the text isn't anti-aliased after zooming it over a certain amount (I use these customized settings: http://www.sharpfonts.co.cc/ , sharp fonts), it allows for smooth panning. I can't screenshot the sluggishness, but it can be easily verified by lacing a fair amount of devices, creating a schematic which, after pressing space (zoom to fit), will make the fonts barely readable. Then use the mouse-wheel to scroll and the pan.
- II -
Another problem is since I can't remember when, but it's not something that really gets in the way, it can be overcome, but now that I'm here I may as well mention them:
1. Placing a component on the schematic and Ctrl-right-clicking on it; 2. Adding a SPICE directive ('S' key) or a text ('T' key) 3. Ctrl-right-clicking on a component's name
All will make use of some dialog windows which allow text entries: 1 has table-like entries, 2 has a multi-line entry and 3 uses a one-line entry. The problem arises when launching LTspice with the simple "wine LTspice.exe" command (terminal, launcher, etc), which makes use of LTspice's built-in detection of a WINE environment.
1. In the dialog window that opens, a line that takes more than the default window (entry) width will be cropped. Nothing unusual, but the line of text normally follows the last typed characters, to be able to see what you're currently doing; instead, the line of characters seems anchored to the first one leaving you typing blindly ahead. (screenshot1.png) 2. Typing a full line and beyond will make things just like above. You can Ctrl-enter for a new line, but it's the same, all the way down. However, here you will get to see the "current typing" line. (screenshot2.png) There's a nastier glitch if you have a mile long line among the others, because when right-clicking on it to edit it, the I-beam cursor will not move it's position, furthermore delete or backspace are invisible; this can be avoided by breaking it into multiple lines with ctrl-enter and adding "+ " at the beginning of the new line, for SPICE directives. (screenshot3.png, screeshot4.png) 3. This only has problems with resizing (see below).
Trying to resize the dialog windows will let you do so, but the internal area won't (I can only imagine what alien description will this seem to you) (screenshot5.png, screenshot6.png). Therefore for #1 you won't know what happens if (e.g.) you have a rather long formula to be implemented, for #2, if there are lots of parameters to be defined, you're left scrolling like crazy, not being able to see more than 4 lines and cropped, too, while for #3, well, I suppose that won't matter as much if #1 gets done, because #1 displays all possible lines (where there's the case).
Now, using "wine LTspice.exe -nowine" (LTspice specific switch) will get around these problems -- and it's the current way of launching for me -- in that it will allow proper resizing of dialog windows, but not the cropping of the longer test line, however...
- III -
...the price to pay will be that using F8 to move a component will leave crumble-like traces behind (F5, copy, F7, cut, the same) (screenshot7.png). Minor glitch, though.
PS: I'll add the screenshots after this, it seems to only allow one attachement.