http://bugs.winehq.org/show_bug.cgi?id=11548
Summary: Coastal Explorer launches but has no toolbar or menus Product: Wine Version: 0.9.55. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: pavilion@pinefields.com
Created an attachment (id=10716) --> (http://bugs.winehq.org/attachment.cgi?id=10716) List of stderr o/p from running app
Application Coastal Explorer GPS marine navigation app starts up and will display some functions (e.g., background map) but lacks the needed toolbar and menus across the top of the app's main window. Keyboard commands are honored and some sub-windows will open if called from the keyboard. Effectively, though, the app is close to dead in the water. (Rose Point Navigation Systems - http://rosepointnav.com - see the site's screenshots of V1.1.61 running (shows position from GPS on maps, drives autopilot, and displays data from ship's instruments) - ignore the V2.0 beta stuff)
The installation ran without any surprises. Installation seems to be mostly expanding a ZIP and doing some licensing housekeeping. A desktop icon is created and it will launch the app. The command is: env WINEPREFIX="/home/n5470/.wine" wine "C:\Program Files\Coastal Explorer Trial\Chart.exe"
Using a simple shell script (one liner - as above) to set the environment variable and launch the app from a console, the response is:
The proliferation of toolbar errors is, I suspect, not a little an explanation of why the app won't show its toolbar menus. Doh...
The host system is an old HP laptop - Pavilion N5470, 1 GHz Athlon with 512M and 60G HDD (50+G free). The host OS is openSUSE 10.3, a fresh install. The openSUSE wine (.44) was uninstalled with YaST and .55 was installed manually (usual configure and makes).
http://bugs.winehq.org/show_bug.cgi?id=11548
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Component|-unknown |comctl32 Priority|P1 |P2
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2008-02-11 13:24:23 --- Most likely problem is in comctrl32.dll Can you get native version of that dll and override it with winecfg? Don't forget to (re)move corresponding manifest file from c:\windows\winsxs or Wine won't use the native dll.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #2 from RBEmerson pavilion@pinefields.com 2008-02-11 16:42:51 --- (In reply to comment #1)
Most likely problem is in comctrl32.dll Can you get native version of that dll and override it with winecfg? Don't forget to (re)move corresponding manifest file from c:\windows\winsxs or Wine won't use the native dll.
I need more detail on this. I collected comctl32.dll from an existing WinXP (don't have a Win2K handy) in hopes that would work. I renamed the original file comctl32.dll.original, copied in the native comctl32.dll (same permissions and user info) into the same place as the builtin version (windows/system32), used winecfg to make an override for comctl32.dll (native only), and tried to launch Coastal Explorer. I got "file not found" for comctl32.dll. Now I can't even launch winecfg to undo the "native" setting (same old "file not found" for comctl32.dll). I restored the .original file (time stamp, permission, etc. all as before) and still get "file not found" for comctl32.dll. Editing user.reg to show "builtin" instead of native for comctl32 (and commenting the line out altogether) didn't help. Even a "make install" didn't reset the problem. I can find both the compiled ("builtin") and native files in windows/system32 but wine can't. "I've fallen and I can't get up!"
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #3 from James Hawkins truiken@gmail.com 2008-02-11 16:47:38 --- Read the third sentence of comment #1.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #4 from RBEmerson pavilion@pinefields.com 2008-02-11 17:17:15 --- (In reply to comment #3)
Read the third sentence of comment #1.
Went there, did that, no t-shirt. Specifically, there is only one .manifest file in winsxs\manifest and it refers only to comctl32. I renamed it out existence by adding .original at the back of the file name. Attempting to run winecfg still fails as described above: "comctl32.dll - file not found". I'm sure I'm out of sync between builtin and native versions of comctl32.dll and probably the state of user.reg (with the override for comctl32) is now wrong, too. Short of completely rebuilding wine (make uninstall, ./configure, etc.), I need advice on how to get back in sync and back to seeing the original bug/problem. From there, since all I have here is WinXP, a good source for a native Win2K comctl32.dll would be nice.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #5 from James Hawkins truiken@gmail.com 2008-02-11 17:20:42 --- rm -rf ~/.wine
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #6 from RBEmerson pavilion@pinefields.com 2008-02-11 17:36:13 --- (In reply to comment #5)
rm -rf ~/.wine
ARGH!!!
Will do.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #7 from RBEmerson pavilion@pinefields.com 2008-02-11 18:15:27 --- (In reply to comment #6)
(In reply to comment #5)
rm -rf ~/.wine
ARGH!!!
Will do.
That didn't hurt as much as I thought it might. Coastal Explorer is re-installed and back to its bad habits, as hoped for. Back to sorting out the problem of the missing toolbar, etc...
Googling on comctl32.dll, I don't see "use this version only with Win[XP|2K|ME|whatever]" warnings, so I'll stick with the one liberated from my XP machine for now. On the manifest file, do I remove the entire file or only the <file></file> structure? What about winecfg and the library override control there? Do I invoke the native/builtin option or forget going back to winecfg altogether?
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #8 from James Hawkins truiken@gmail.com 2008-02-11 18:17:52 --- You delete the entire manifest file.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #9 from RBEmerson pavilion@pinefields.com 2008-02-11 19:22:53 --- Created an attachment (id=10720) --> (http://bugs.winehq.org/attachment.cgi?id=10720) stderr output from run with native comctl32.dll in place
No obvious changes from the intial run with the builtin comctl32.dll
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #10 from James Hawkins truiken@gmail.com 2008-02-11 19:25:12 --- A +loaddll will show that you are not running with native comctl32.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #11 from RBEmerson pavilion@pinefields.com 2008-02-11 19:37:18 --- (In reply to comment #10)
A +loaddll will show that you are not running with native comctl32.
You lost me - "+loaddll"?
The builting comctl32.dll and manifest files were changed to [filename].original. A comctl32.dll from a working WinXP system was installed in windows\system32 and the app re-run. No apparent changes in the app's behavior or stderr output (see attachment #2). The other Windows app running at the time (wxtide32, listed in the apps db, v4.7) benefited slightly from the change: a popup window now goes away when the left mouse click ends (problem was the window wouldn't go away, once presented, except when the app was exited). *Something* changed to make wxtide32 respond differently to a left mouse click. The point isn't to debug wxtide32, of course, but it is running at the moment and its behavior changed after tossing the manifest and/or dropping in a different conctl32 and being restarted. Where to go from here?
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #12 from James Hawkins truiken@gmail.com 2008-02-11 19:41:25 --- You still have to set comctl32 to native in winecfg.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #13 from RBEmerson pavilion@pinefields.com 2008-02-11 20:04:36 --- (In reply to comment #12)
You still have to set comctl32 to native in winecfg.
Now set native, builtin (in that order). IIRC, invoking only native seemed to send me back to rm -fr ~/.wave
Also, pls explain "+loaddll"
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #14 from Austin English austinenglish@gmail.com 2008-02-11 20:23:04 --- (In reply to comment #13)
(In reply to comment #12)
You still have to set comctl32 to native in winecfg.
Now set native, builtin (in that order). IIRC, invoking only native seemed to send me back to rm -fr ~/.wave
Also, pls explain "+loaddll"
$ WINEDEBUG=+loaddll wine your_program.exe &> /tmp/log.txt 2>&1
Then attach /tmp/log.txt here.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #15 from RBEmerson pavilion@pinefields.com 2008-02-11 21:06:03 --- Created an attachment (id=10721) --> (http://bugs.winehq.org/attachment.cgi?id=10721) Log of use -ends with an exception
Program ran with menus visible for the first time, a definite step forward. Some functionality appears unreliable but it's hard to say why. The program was scanning all folders for chart (map) files when it collapsed. I missed seeing things go blank and can only refer to log for diagnostic info.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #16 from Austin English austinenglish@gmail.com 2008-02-12 00:27:23 --- (In reply to comment #15)
Some functionality appears unreliable but it's hard to say why. The program was scanning all folders for chart (map) files when it collapsed. I missed
Try removing ~/.wine/dosdevices/z:
And rerunning. That way it won't scan your _entire_ file system.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #17 from RBEmerson n5470@pinefields.com 2008-02-12 07:11:03 --- (In reply to comment #16)
(In reply to comment #15)
Some functionality appears unreliable but it's hard to say why. The program was scanning all folders for chart (map) files when it collapsed. I missed
Try removing ~/.wine/dosdevices/z:
And rerunning. That way it won't scan your _entire_ file system.
This can be controlled inside the program. For now, I'll just avoid hitting the "scan everything" button (easy enough to do). FWIW, as part of normal function, the program watches for changes in specifically listed sub-dirs, looking for new or revised charts. The scan process runs well enough then. Sorta. I can see the status of the scan and a listing of files/charts found. It concludes with no apparent error messages or other signs of problems. However, after the end of the scan, trying to actually view the charts does not work. At this point, the problem feels like a permissions issue, not a wine issue. See the following comment for more on that...
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #18 from RBEmerson n5470@pinefields.com 2008-02-12 08:02:50 --- The good news is the menus in the toolbar are now present. The menus, as tested to date, appear to be functioning as one might expect. At least five different problems remain with the screen presentation, however.
1) All tool icons are missing. There are cutouts or black shapes, on the tool bars, where the icons belong. Clicking on those areas seems to give the expected results. This is, apparently, an issue of not being able to display intended artwork.
2) Two major on-screen displays are presented very poorly. 2a) One display is a GPS status box. If GPS data is being received and the data is lost (the program detects a loss of data), a red translucent box is drawn in the upper right corner of the main display, and a message ("GPS No Data" IIRC) is drawn inside of it. Clicking on the box cancels the alarm message and clears the box.
2b) If the ship's position marker on the displayed chart is moved by the user (this is possible and permissible), a yellow translucent box is displayed in the upper right corner of the main window (same process as 2a, different color, different text), with a legend indicating DR ("dead reckoning") is in use (that is, the ship's position is no longer being driven by real-time GPS data but an estimation of the current position based on course and speed from a known location). Clicking the box clears the alarm message, as in 2a.
3) A rectangle of about the right height is drawn hard against the upper right margin of the main screen. Vertical placement and box height seem about right compared to execution under windows; horizontal placement is wrong and width is wrong (perhaps 5-10% of expected width). Clicking on what is displayed does clear the box as drawn.
In the upper left corner, there should be a rectangular box with two pieces of information: north orientation and chart scale. Additionally, clicking in the box should produce a popup which can control map orientation (north up, course up, heading up), scale (a scrolled, clickable list of scales from roughly 1:10,000 to 1:5,000,000), and chart display centering (follow ship's position [re-center chart about ship] w/ ship in the middle of display, follow ship w/ ship at the bottom of projected route, don't follow ship).
There is a blue arrow in about the right vertical location (as with the alarm box, above) but no box is present, scale information is not written, and there is no response to clicks in the area of the arrow.
4) A sidebar panel on the right side of the screen can be commanded to show different items. Two items work fully: the map overview tool (miniature map with rectangle marking the area displayed in the main screen), and the properties display (showing information about an item clicked on - typically, the ship [position, icon options, and related data], chart features [untested as charts won't fully load, yet], or user-created marks on the chart [to be tested]). Additionally, instruments, including a compass, can be displayed. The compass' background is drawn but numbers at cardinal points are missing. A line indicating ship's true heading (vs. magnetic heading - rarely the same value) is displayed. A "title bar" showing magnetic heading is displayed as expected. The compass, when the ship moves, will rotate and the numbers in the compass will rotate with it. This hasn't been tested yet but, so far, no numbers are shown at all.
5) The program can display tidal data for specific locations. Tide levels are shown inside a diamond. Current direction and force is shown with an arrow. Level diamonds and arrows are placed at their positions as recorded in NOAA databases. Diamonds and arrows are shown (or not) depending on the scale of the displayed chart (show the entire US east coast, only a few points are present, show an area 25-50 miles on a side, many points are shown). Clicking on a diamond or arrow brings up a display of a graph showing time and level or speed. Diamonds are filled with white and a triangle shows rising or falling tides by being placed in the upper or lower half of the diamond, while the current computed water level is displayed next to the diamond.
At present, the diamonds and arrows are shown according to the scale of the background (hardwired, world-wide) chart. Location and orientation appear correct. The diamonds do not have rising/falling tide triangles in them and water levels are not displayed. Clicking for the data window, displayed as a new window under the main window (which shrinks to accept the new window), works. Some labeling appears to be missing but some "click here for more info" functions work.
There seems to be a common theme in the above: some labeling and icon display is not working. Events that create fundamental Windows structures, such as windows and menus seem to work approximately as expected. Events that create customized displays (e.g., the compass or scale/heading display) do not work properly.
Totally untested is the application's handling of data (via serial ports or Internet connections). The room for mischief here is not small...
For those wishing to try this program, a trial edition can be obtained directly from the Rose Point Navigation Systems site: http://rosepointnav.com/CoastalExplorer/Trial/default.htm (Note: RPN is beta-testing V2.0 - ignore it. The trial package delivers V1.1.61, the current release)
The downloaded material includes both enough charts for testing and links to NOAA sites for more charts.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #19 from Vitaliy Margolen vitaliy@kievinfo.com 2008-02-12 08:37:58 --- (In reply to comment #18) Please file all those other issues as separate bugs. This bug is about broken _Wine_ comctrl32 only. Also note that missing/black icons are caused by using native comctl32 (there is nothing to be fixed).
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #20 from RBEmerson n5470@pinefields.com 2008-02-12 16:30:32 --- (In reply to comment #19)
(In reply to comment #18) Please file all those other issues as separate bugs. This bug is about broken _Wine_ comctrl32 only. Also note that missing/black icons are caused by using native comctl32 (there is nothing to be fixed).
My point is that it appears that the five items listed are different manifestations of the same problem / bug. If someone can show another cause, I'll be more than willing to file the appropriate bug report.
I do not understand "missing/black icons are caused by using native comctl32 (there is nothing to be fixed)". In the Windows instance of Coastal Explorer, the icons are present and visible. In the wine instance of Coastal Explorer they're not, only a background shape is. I'd call that broken.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #21 from Vitaliy Margolen vitaliy@kievinfo.com 2008-02-12 21:15:49 --- That means it is not a Wine problem. When you using native dlls it's not guaranteed for everything to work properly. This is one of those cases. Also please use binary Wine (see the download page on winehq.org). We know how it was compiled.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #22 from RBEmerson n5470@pinefields.com 2008-02-12 23:03:48 --- (In reply to comment #21)
That means it is not a Wine problem. When you using native dlls it's not guaranteed for everything to work properly. This is one of those cases. Also please use binary Wine (see the download page on winehq.org). We know how it was compiled.
I'm nor sold on "not a wine problem" - if that .dll works in windows, it should work in wine.
OpenSUSE 10.3's wine binaries are only up to 0.9.44, or *way* behind 0.9.55. In wine documentation, "are you using the latest release?" is part of the "is this a current bug or has it been fixed?" checklist. To ensure I wasn't reporting a bug that had been fixed, I built 0.9.55 from source.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #23 from Lei Zhang thestig@google.com 2008-02-13 13:45:37 --- Have you checked http://software.opensuse.org/download/Emulators:/Wine/openSUSE_10.3/
?? They have up to date builds.
It's currently down for me, but it's mirrored elsewhere:
http://ftp.twaren.net/Linux/OpenSuSE/repositories/Emulators:/Wine/openSUSE_1...
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #24 from RBEmerson n5470@pinefields.com 2008-02-13 14:18:32 --- I'll give the sites a try. I keep this system current, with an updater tool watching for all updates (not just mandatory updates). I also tried forcing an update from the s/w manager "'cause ya never know...". I remained stuck at 0.9.44 until I built .55 by hand (using ./configure and simple makes through "make install", as root - no file editing or arguments added).
- - -
At this point, the summary "no toolbars or menus" is no longer strictly correct. The toolbar is still not properly populated (background fields but no icons, although the fields appear in the expected places) and the menus present oddly on occasion. The five points listed above are still a fair summary of the outstanding problems discovered to date (issues with no added maps, and I/O remain untested - lotsa room for more real bugs). Should I file a new bug that somehow references all the discussion here or...?
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #25 from RBEmerson n5470@pinefields.com 2008-02-13 23:55:16 --- Created an attachment (id=10763) --> (http://bugs.winehq.org/attachment.cgi?id=10763) Run w/ repository version of 0.9.55
Note comment about Common Control - this hasn't been seen before. Native comctl32.dll is present (see directory listing at the start of the attachment) and the manifest file has been disabled (renamed).
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #26 from RBEmerson n5470@pinefields.com 2008-02-13 23:58:08 --- (In reply to comment #25) Toolbar icons are still absent but now the background for each icon is in the shape of the missing icon and not just a black square. Progress!
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #27 from Vitaliy Margolen vitaliy@kievinfo.com 2008-02-14 00:09:20 --- (In reply to comment #26) Good boy. Now left to remove all your cruft and try with empty ~/.wine directory.
http://bugs.winehq.org/show_bug.cgi?id=11548
RBEmerson n5470@pinefields.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://rosepointnav.com/Coas | |talExplorer/Trial/default.ht | |m
--- Comment #28 from RBEmerson n5470@pinefields.com 2008-02-14 21:51:47 --- Applied rm -rf ~/.wine, did winecfg to create .wine, installed native comctl32 (copy file, remove manifest, add override to native file), and no discernible improvement. This process may have slightly worked against WXTide32 (Bug 11562 Bug11563 - Results not yet posted).
At this point, I strongly recommend someone else run this app (URL to trial version added in header) to see the stderr comments as CE launches. Lots of "not fully implemented" and "not implemented" comments...
http://bugs.winehq.org/show_bug.cgi?id=11548
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |download
--- Comment #29 from Austin English austinenglish@gmail.com 2008-02-16 18:20:28 --- Confirming. Native comtcl32 gets the toolbars to appear, but then makes the application crash.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #30 from RBEmerson n5470@pinefields.com 2008-02-16 22:11:36 --- (In reply to comment #29) Interesting to hear about the crash, as that's been very rare for me. Doing the install process that comes in the trial package, there shouldn't be a problem with files being in the wrong place, etc. On re-launching CE, does it recognize a crash has happened? (You'll know, for sure, if it does recognize this) It will be useful to install CE on a Windows system for comparison.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #31 from RBEmerson n5470@pinefields.com 2008-02-22 17:32:37 --- (In reply to comment #29)
Confirming. Native comtcl32 gets the toolbars to appear, but then makes the application crash.
Bump.
Have you (or has anyone else) tried CE under Windows for comparison?
I've been trying more functions (e.g., splitting the screen either with a split screen tool or typing the digits 2, 3, or 4 - 1 returns to a single screen) and "widgets" (instruments on the sidebar while in cruise mode [F12 to toggle between planning and cruise modes]). CE remains surprisingly stable. At this point the biggest missing function is displaying charts (maps) other than the background world map. That is, however, outside of the scope of this bug report.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #32 from RBEmerson n5470@pinefields.com 2008-02-23 12:31:07 --- Created an attachment (id=10924) --> (http://bugs.winehq.org/attachment.cgi?id=10924) App execution w/ native & builtin comctl32 under 0.9.56
The first run is with native comctl32.dll. The second run is with builtin comctl32.dll (not updated, according to directory dates, in going from 0.9.55 to 0.9.56). Long story short, everything remains as broken, with the builtin comctl32, as ever. Moving to 0.9.56 made no functional changes in the app's appearance or performance.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #33 from RBEmerson n5470@pinefields.com 2008-03-04 00:14:11 --- (In reply to comment #29)
Confirming. Native comtcl32 gets the toolbars to appear, but then makes the application crash.
Look in drive_c/windows/profiles/All\ Users/Application\ Data/Rose\ Point\ Navigation\ Systems/Application.log for information on what the app recorded as happening.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #34 from RBEmerson n5470@pinefields.com 2008-03-04 00:24:49 --- Discussion, with the application's author, of the problems related to missing text produced the comment that much of the application uses GDI and GDI+ to achieve its results. The problem areas (with one exception) such as missing tide level labels, missing labels in user-created marks, depths, and place names were all created through GDI+. It was his impression that, if, as was his understanding, Wine maps GDI+ calls back to GDI, things should work better under Wine than under Windows. The notable exception is the toolbar icons, for which there was no suggested explanation as to why they weren't draw correctly.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #35 from RBEmerson n5470@pinefields.com 2008-03-05 12:51:57 --- Created an attachment (id=11128) --> (http://bugs.winehq.org/attachment.cgi?id=11128) +setupapi trace run w/ revised registry keys
The recommended registry changes were made and confirmed as being present. Launching Coastal Explorer with n5470@gazebo:~> WINEDEBUG=+setupapi wine "C:\Program Files\Coastal Explorer\Chart.exe" >& COMTestLog03.txt produced no change in CE's behavior. It still reports "no COM ports found" as before. A copy of the CE Application.log from the run is attached for inspection. The log format is nn.nnn:dd.ddd where nn.nnn is the total elapsed time from start of execution and dd.ddd is the elapsed time between log entries. Note that there is only one mention of COM ports: 7.167:0.003: Created AlarmController: 0x000001e8 (0x19) 29.096:21.929: Enumerating COM ports: 53.518:24.422: Shutting down... 53.563:0.045: Shutdown complete
The shutdown was requested and is normal behavior.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #36 from RBEmerson n5470@pinefields.com 2008-03-05 12:55:17 --- Created an attachment (id=11129) --> (http://bugs.winehq.org/attachment.cgi?id=11129) App's native log from run to create attachment 11128
Application.log, created by Coastal Explorer, during the run that produced the trace shown in 11128. Note there is only one reference to COM ports: 7.167:0.003: Created AlarmController: 0x000001e8 (0x19) 29.096:21.929: Enumerating COM ports: 53.518:24.422: Shutting down... 53.563:0.045: Shutdown complete
That there is no listing of ports below the line at 29.096 is not a good sign: no ports found. Shutdown is normal.
http://bugs.winehq.org/show_bug.cgi?id=11548
RBEmerson n5470@pinefields.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #11128|0 |1 is obsolete| |
--- Comment #37 from RBEmerson n5470@pinefields.com 2008-03-05 12:58:52 --- (From update of attachment 11128) [REMOVED - in wrong Bug]
http://bugs.winehq.org/show_bug.cgi?id=11548
RBEmerson n5470@pinefields.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #11129|0 |1 is obsolete| |
--- Comment #38 from RBEmerson n5470@pinefields.com 2008-03-05 13:00:17 --- (From update of attachment 11129) [REMOVED - in wrong Bug]
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #39 from RBEmerson n5470@pinefields.com 2008-03-08 12:52:45 --- No change in this bug under Wine 0.9.57. ~/.wine was deleted and created from scratch with winecfg after installing 0.9.57. Native comctl32 was removed with the removal of ~/.wine and not replaced for testing under 0.9.57.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #40 from RBEmerson n5470@pinefields.com 2008-03-09 15:01:20 --- (In reply to comment #39)
No change in this bug under Wine 0.9.57. ~/.wine was deleted and created from scratch with winecfg after installing 0.9.57. Native comctl32 was removed with the removal of ~/.wine and not replaced for testing under 0.9.57.
Duplicated on a second platform running openSUSE 10.3 and Wine 0.9.57. Adding native comctl32.dll restored the tool bar to CE.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #41 from RBEmerson n5470@pinefields.com 2008-03-19 21:25:20 --- The following "err:" messages are probably tied to the use of COM5: fixme:menu:TrackPopupMenuEx not fully implemented err:comm:get_baud_rate tcgetattr error 'Input/output error' err:comm:set_baud_rate tcgetattr error 'Input/output error' fixme:menu:TrackPopupMenuEx not fully implemented
I didn't try to shift the GPS' data rate from 4800 baud and data was received in good order, so I'm not sure what the complaint really is, but there it is.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #42 from RBEmerson n5470@pinefields.com 2008-03-19 21:30:32 --- Sigh... strike comment 41. I really, really, really, *really* dislike the auto-advance "feature" when entering comments in bugs. >:-(
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #43 from Dmitry Timoshkov dmitry@codeweavers.com 2008-03-20 02:06:17 --- (In reply to comment #42)
Sigh... strike comment 41. I really, really, really, *really* dislike the auto-advance "feature" when entering comments in bugs. >:-(
How about turning it off in your bugzilla preferences?
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #44 from RBEmerson n5470@pinefields.com 2008-03-20 07:12:17 --- (In reply to comment #43)
(In reply to comment #42)
Sigh... strike comment 41. I really, really, really, *really* dislike the auto-advance "feature" when entering comments in bugs. >:-(
How about turning it off in your bugzilla preferences?
How about not making advancing through bugs, unannounced, the default?
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #45 from Dmitry Timoshkov dmitry@codeweavers.com 2008-03-20 07:18:54 --- (In reply to comment #44)
(In reply to comment #43)
(In reply to comment #42)
Sigh... strike comment 41. I really, really, really, *really* dislike the auto-advance "feature" when entering comments in bugs. >:-(
How about turning it off in your bugzilla preferences?
How about not making advancing through bugs, unannounced, the default?
I believe that's a bugzilla default setting, and Wine bugzilla simply uses the defaults. Feel free to ask bugzilla developers to change that, but changing a setting in your own preferences is much easier than complaining loudly.
http://bugs.winehq.org/show_bug.cgi?id=11548
--- Comment #46 from Austin English austinenglish@gmail.com 2008-12-11 13:06:30 --- Still present in git.
http://bugs.winehq.org/show_bug.cgi?id=11548
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #47 from Austin English austinenglish@gmail.com 2010-06-17 01:01:19 --- Works fine in wine-1.2-rc3-84-g6456e14. There are a lot of toolbar errors in the output, but nothing wrong AFAICT. The properties menu in the bottom right is all white, but I haven't compared to windows. Native comctl32 doesn't change that though.
http://bugs.winehq.org/show_bug.cgi?id=11548
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #48 from Alexandre Julliard julliard@winehq.org 2010-06-18 12:46:14 --- Closing bugs fixed in 1.2-rc4.