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.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #1 from testelor@yahoo.com 2012-10-31 09:53:14 CDT --- Created attachment 42352 --> http://bugs.winehq.org/attachment.cgi?id=42352 Bug II, case #1
Trying to type will not let you see ahead.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #2 from testelor@yahoo.com 2012-10-31 09:55:33 CDT --- Created attachment 42353 --> http://bugs.winehq.org/attachment.cgi?id=42353 Bug II, case #2a
Pressing either 'S' or 'T' and filling up more than the line expects to, will get you this. Normally, Ctrl+Enter resolves it, but for larger blocks of text/parameters/etc resizing s needed which is screenshots 5 and 6.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #3 from testelor@yahoo.com 2012-10-31 09:57:08 CDT --- Created attachment 42354 --> http://bugs.winehq.org/attachment.cgi?id=42354 42353: Bug II, case #2b
Behind you see a monster function, less-likely to have in reality, and the dialog shows the I-beam at the beginning which will not move (arrow keys, mouse click, nothing).
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #4 from testelor@yahoo.com 2012-10-31 09:58:54 CDT --- Created attachment 42355 --> http://bugs.winehq.org/attachment.cgi?id=42355 42353: Bug II, case #2b (bis)
The proper way to break the lines, but it leaves you scrolling through the whole ordeal, you can't resize.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #5 from testelor@yahoo.com 2012-10-31 09:59:40 CDT --- Created attachment 42356 --> http://bugs.winehq.org/attachment.cgi?id=42356 Resizing
Resizing bug for #1
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #6 from testelor@yahoo.com 2012-10-31 10:00:11 CDT --- Created attachment 42357 --> http://bugs.winehq.org/attachment.cgi?id=42357 Resizing
Resizing bug for #2
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #7 from testelor@yahoo.com 2012-10-31 10:03:05 CDT --- Created attachment 42358 --> http://bugs.winehq.org/attachment.cgi?id=42358 Traces left behind when moving
Pressing F8 (here) and moving the four devices will leave these things behind. Here, it's not as troublesome as it would be in a large schematic. The traces will "reset" to zero if the schematic is zoomed in and you move the mouse (still grabbing the devices) towards the edge, making the view shift in a new direction, but tey'll continue from there on.
http://bugs.winehq.org/show_bug.cgi?id=32114
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #8 from Bruno Jesus 00cpxxx@gmail.com 2012-10-31 13:19:03 CDT --- Hi, can you please help testing other ltspice bugs and give an update to bug 30100, bug 24873 and 23450?
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #9 from testelor@yahoo.com 2012-11-01 04:13:55 CDT --- (In reply to comment #8)
Hi, can you please help testing other ltspice bugs and give an update to bug 30100, bug 24873 and 23450?
Hello Bruno
For 30100 (replied there), in short I don't get those things, for 24876 (no reply) that never happened to me except some rare occasions when it proved to actually be a bug within LTspice itself, and for 23450 (no reply) I may have something vaguely similar, but not with the focus problem, with editing a line: place a component (press 'F2' and select "bv" for example), right-click on it to bring the general model's properties and, let's say that "SpiceLine" has V=sin(2*pi*time) (this can be changed by right-clicking on the symbol's name, directly). Now, double-click on the line to edit it, but then press escape, the line's content dissappears, but only until you close the dialog and then re-open it. However, this is a very minor glitch that I didn't even consider reporting it.
If you need replying to the other two, I will, but I saw that they were from 2 years back.
Vlad
http://bugs.winehq.org/show_bug.cgi?id=32114
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://ltspice.linear.com/s | |oftware/LTspiceIV.exe
--- Comment #10 from Bruno Jesus 00cpxxx@gmail.com 2012-11-02 20:54:40 CDT --- Thank you very much for the tests. I have used your data to update the bugs.
(In reply to comment #9)
... place a component (press 'F2' and select "bv" for example), right-click on it to bring the general model's properties and, let's say that "SpiceLine" has V=sin(2*pi*time) (this can be changed by right-clicking on the symbol's name, directly). Now, double-click on the line to edit it, but then press escape, the line's content dissappears, but only until you close the dialog and then re-open it. However, this is a very minor glitch that I didn't even consider reporting it.
This is exactly what happens in Windows for me, what did you expect to happen?
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #11 from Bruno Jesus 00cpxxx@gmail.com 2012-11-02 21:32:22 CDT --- (In reply to comment #0)
- I -
Please attach a demo project to make it easier for others to reproduce.
- II -
- 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)
The same happens in XP for me in the one line table entry (or I did not understand it properly).
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;
I can confirm this issue.
- This only has problems with resizing (see below).
I can confirm the resizing issue.
- 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.
I can't reproduce this with an intel card (driver 2.20), wine from git and gnome2.
http://bugs.winehq.org/show_bug.cgi?id=32114
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Dialog resizing glitches, |LTSpice: Dialog resizing |slow panning when zooming, |glitches, slow panning when |minor traces |zooming, minor traces
--- Comment #12 from Bruno Jesus 00cpxxx@gmail.com 2012-11-03 19:06:10 CDT --- Renaming the bug to make it easier to find.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #13 from testelor@yahoo.com 2012-11-04 02:51:35 CST ---
This is exactly what happens in Windows for me, what did you expect to happen?
My expectance was the line's contents shouldn't disappear, but if you say this happens in Windows, too, then this is just a minor inconvenience (even if it was a WINE problem), therefore already forgotten.
As for the others, well, if you want a demo project for the 1st bug, I attached some mockup schematic (demo.asc) that needs zooming in order to see the slow-down caused by the panning, but in order to actually see the effect you'll have to use the newer versions of wine, from 1.5.13 (including), up.
Now that I'm writing these, I realize I haven't said what hardware/software I have, so here it is: HP Pavilion dv7-1053ez (C2D P8400, no overclock/undervoltage, 4GB RAM DDR2, GeForce 9600M GT 512MB RAM DDR2) which runs Linux Mint 13 x64 (Gnome, but I'm using Xfce 4.10 ppa), with ppa for WINE from http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu . Currently, I have wine1.5-amd64_1.5.12-0ubuntu1_amd64 , downgraded everytime a newer version came along because of the panning thing.
Lastly, about the traces left behind, now that you say it doesn't happen with a different graphic card, it may well be because of nVidia's drivers, so I'm at their mercy (I use Xfce's compositing feature for the shadows -- they make working with unmaximized windows much easier for me -- but it doesn't affect the result).
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #14 from testelor@yahoo.com 2012-11-04 02:54:44 CST --- Created attachment 42379 --> http://bugs.winehq.org/attachment.cgi?id=42379 A mockup schematic
Zoom in (mouse wheel) then click-drag to pan (move) it. For WINE > 1.15.12, it should be slow, sluggish.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #15 from testelor@yahoo.com 2012-11-05 00:46:42 CST --- (In reply to comment #11)
I can't reproduce this with an intel card (driver 2.20), wine from git and gnome2.
It just occured to me: did you run "wine LTspice.exe -nowine" for this?
Vlad
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #16 from Bruno Jesus 00cpxxx@gmail.com 2012-11-05 16:26:55 CST --- (In reply to comment #15)
It just occured to me: did you run "wine LTspice.exe -nowine" for this?
You're right, I missed the -nowine. So now I can see the yellow dust in wine-git.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #17 from testelor@yahoo.com 2012-11-11 02:34:56 CST --- Today's update brought wine-1.5.17 and, while I don't know what has been working upon, when, or where, the mentioned bugs still exist.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #18 from Bruno Jesus 00cpxxx@gmail.com 2012-11-11 05:51:11 CST --- We need to split this bug, the wine bugzilla rule is one issue per bug. We can make this one for the slow panning/zooming. So 3 others bugs are needed as far as I can see: one for the crumble-like traces while moving components, one for the multiline edit and another for the internal window resizing.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #19 from testelor@yahoo.com 2012-11-12 03:07:41 CST --- Should I do it, splitting into parts and renaming? If so, there's a question: how to keep/rename this one given that it already has replies? I can add the other three, but I'm afraid this one will need to be deleted and the fourth re-added. But only **after** I copy all the content (pictures), I don't have them anymore.
I'll wait for your reply.
Vlad
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #20 from Bruno Jesus 00cpxxx@gmail.com 2012-11-13 19:27:12 CST --- (In reply to comment #19)
Should I do it, splitting into parts and renaming? If so, there's a question: how to keep/rename this one given that it already has replies? I can add the other three, but I'm afraid this one will need to be deleted and the fourth re-added. But only **after** I copy all the content (pictures), I don't have them anymore.
You can follow the example of bug 32218. We can rename this bug later and the other bugs can refer to comments/attachments in this bug.
http://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #21 from testelor@yahoo.com 2012-11-14 01:45:34 CST --- (In reply to comment #20)
You can follow the example of bug 32218. We can rename this bug later and the other bugs can refer to comments/attachments in this bug.
Right, I made two new bugs (32221 and 32222) and uploaded the relevant pictures for each, there, so anyone reading them will not get headaches and I tried to follow your short description. The only thing left is to keep this one regarding the panning/zooming and then to rename it (maybe delete the extra attachements?).
Vlad
https://bugs.winehq.org/show_bug.cgi?id=32114
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned?
--- Comment #22 from Ken Sharp imwellcushtymelike@gmail.com --- Is this still an issue in Wine 1.7.45 or later?
https://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #23 from testelor@yahoo.com --- I have Linux Mint 17.1 (based on Ubuntu Trusty) and use the official repository for Wine. However, I checked the official "ubuntu-wine" ppa and, listed under Trusty, there's only version 1.7.44-0ubuntu1. Is this version good enough to test or is there another ppa I can use? I don't want to mess up the installation but, if it provides useful answers to this bug (referring to the rest, too: 32221, 32222, 32224), then I will install it and test it. With this version (1.6.2), it still happens, though it may be because the program itself has glitches? No idea.
https://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #24 from testelor@yahoo.com --- I still see no other .deb higher than 1.7.44 even though searches bring up results listing ubuntu-wine/ppa as a source. Still, I installed 1.7.44-0ubuntu1 as it is there, but the problems (#32114, #32221, #32222, #32224) still persist.
However, there is one other problem now:
- Run LTspice either with "-nowine" or without, it doesn't matter. - New schematic. - Press "F2" and 2xClick on BV, LClick to place. - Replace "F(...)" with "1", it should look like "V=1" now. - Press "G" and place it on the lower pin, attached to it. - Press "S" and write ".tran 1", LClick to place on the schematic. - Press run (the running man in the toolbar). - After the simulation has finished (the running man is grayed out no more), bring up the log with "View > SPICE Error Log" or by pressing "Ctrl+L" with the schematic active -- the fonts are badly rendered.
Again, this is 1.7.44-0ubuntu1, I see no higher versions on ubuntu-wine/ppa and using "sudo apt-get install wine1.7-dev" installs the same version.
https://bugs.winehq.org/show_bug.cgi?id=32114
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #25 from super_man@post.com --- I think you should be able to fetch 1.8 or 1.9 version of wine now. Or wine-staging 1.9.7 version.
https://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #26 from testelor@yahoo.com --- (In reply to super_man from comment #25)
I think you should be able to fetch 1.8 or 1.9 version of wine now. Or wine-staging 1.9.7 version.
Sorry for the late response. A few days ago, I switched to Archlinux, with its 1.9.9 version. Unfortunately, all the symptoms are still there (#32114, #32221, #32222, #32224).
All four imply running either "wine scad3.exe", or "wine scad3.exe -nowine". For my part, only one needs fixing -- either resizing glitches without "-nowine", or search highlighting with "nowine".
I'll also say it again: these are not work-breaking bugs. The way I dealt with them all these years, I can deal with them from now on, but, *if* they can be ironed out, I won't mind, at all...
https://bugs.winehq.org/show_bug.cgi?id=32114
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #27 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-4.1?
https://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #28 from testelor@yahoo.com ---
Does the bug still occur with wine-4.1?
For current Archlinux wine 4.4, only one of them, and only a part of what initially was. I've added a comment to #32222.
https://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #29 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-5.2?
https://bugs.winehq.org/show_bug.cgi?id=32114
--- Comment #30 from testelor@yahoo.com --- Sorry for the late reply, I don't check this mail very often. No, they're gone (for LTspiceXVII, but since LTspiceIV is no longer supported/updated, it doesn't count anymore). I checked the other issues for the other bugs I filed (I'll update them, too), they seem to be gone (Wine is 5.4 now). Thank you.
https://bugs.winehq.org/show_bug.cgi?id=32114
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #31 from Gijs Vermeulen gijsvrm@gmail.com --- Marking FIXED. (Comment #30)
https://bugs.winehq.org/show_bug.cgi?id=32114
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #32 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 5.5.