LightWave seems to be nearly working in Wine without _too_ many issues, but there are a few things that seem to leave it lacking. I will attach the error_out logs that I get upon using the application a little bit. (Both Modeler.exe and LightWav.exe logs) Visually and User Interface wise, some issues I see right off the top are things such as: Deactivated text is red with a slight drop shadow (should be grayed out with that same drop shadow). Some text is dislocated on menu buttons. The numeric pad doesn't seem to function quite right (specifically, I tried to press the `+' key on the keypad to add an object to a scene in LightWav.exe) Menus do not deactivate when the user clicks outside of the menu. This happens in both Modeler and LightWave (layout). To get a menu to disappear one must click a nonactive or deactivated text portion of the menu, so this becomes very burdensome while manipulating the application. I have also had wine crash while using LightWav.exe, so there are some issues that need resolved beyond what I've outlined above, but I think the other issues will come out as the application is used once a "usable" point is reached and we start doing more thorough debugging. The Hub application is also a bit problematic as it resides in the tray. It does sit in my KDE 3.1 tray, which is neat, but when I right click it and tell it to exit, it does not quit so I end up having to kill all wine processes manually. But the hub is the least of my concerns :) and I realize that tray apps don't work quite right yet. I would be very happy to provide input, test and debug fixes if someone is able to provide patches and help for these issues. I am using a cvs version of wine from about 1.5 weeks ago. I have also tried winex cvs and it exhibits many, if not all of the same issues. Winex may be slightly faster in terms of its directdraw functionality as LightWave uses directdraw. Please advise if someone is willing to work through these issues with me and I will be happy to go out an acquire any information needed to get started. Thanks much! It sure is exciting to be _so close_ to leaving Windows entirely behind!!! -George Plymale
Visually and User Interface wise, some issues I see right off the top are things such as:
Doesn't LightWave use its own widget library? I seem to recall it's not a "native windows app" in that respect.
The Hub application is also a bit problematic as it resides in the tray. It does sit in my KDE 3.1 tray, which is neat,
It does? Looks like KDE kept backwards compatability with the old protocol then. Interesting.
but when I right click it and tell it to exit, it does not quit so I end up having to kill all wine processes manually. But the hub is the least of my concerns :) and I realize that tray apps don't work quite right yet.
They should work fine, at least in KDE. That sounds more like a problem with quitting than the tray.
I would be very happy to provide input, test and debug fixes if someone is able to provide patches and help for these issues. I am using a cvs version of wine from about 1.5 weeks ago. I have also tried winex cvs and it exhibits many, if not all of the same issues. Winex may be slightly faster in terms of its directdraw functionality as LightWave uses directdraw.
Please advise if someone is willing to work through these issues with me and I will be happy to go out an acquire any information needed to get started.
To be honest, debugging is something best done by somebody familiar with the app, and who actually has a copy. I don't know how much experience with coding you have, but I'd suggest you read the the wine users guide and developers guide, those give an intro to debugging and sit down and work through the problems. For crashes, try using winedbg to get a backtrace, if you can get a good backtrace that can help with crashes. They look like: ==> 1) function call ..... ebp=.... 2) another function call ..... 3) etc etc Otherwise try filing bugs in bugzilla related to the individual issues. Unless there is a demo version somewhere, it's unlikely any of us have a copy of LightWave, so you're the best person to debug it :) thanks -mike
There is a demo version available from what I've seen. If you have it installed without the dongle and license.key it will run in "discovery" mode which will not save in LightWave (layout). I'm not sure if you can download it though... I'll have to figure that out and get back to you. -George On Monday, March 10, 2003, at 04:31 AM, Mike Hearn wrote:
Visually and User Interface wise, some issues I see right off the top are things such as:
Doesn't LightWave use its own widget library? I seem to recall it's not a "native windows app" in that respect.
The Hub application is also a bit problematic as it resides in the tray. It does sit in my KDE 3.1 tray, which is neat,
It does? Looks like KDE kept backwards compatability with the old protocol then. Interesting.
but when I right click it and tell it to exit, it does not quit so I end up having to kill all wine processes manually. But the hub is the least of my concerns :) and I realize that tray apps don't work quite right yet.
They should work fine, at least in KDE. That sounds more like a problem with quitting than the tray.
I would be very happy to provide input, test and debug fixes if someone is able to provide patches and help for these issues. I am using a cvs version of wine from about 1.5 weeks ago. I have also tried winex cvs and it exhibits many, if not all of the same issues. Winex may be slightly faster in terms of its directdraw functionality as LightWave uses directdraw.
Please advise if someone is willing to work through these issues with me and I will be happy to go out an acquire any information needed to get started.
To be honest, debugging is something best done by somebody familiar with the app, and who actually has a copy. I don't know how much experience with coding you have, but I'd suggest you read the the wine users guide and developers guide, those give an intro to debugging and sit down and work through the problems. For crashes, try using winedbg to get a backtrace, if you can get a good backtrace that can help with crashes. They look like:
==> 1) function call ..... ebp=.... 2) another function call ..... 3) etc etc
Otherwise try filing bugs in bugzilla related to the individual issues. Unless there is a demo version somewhere, it's unlikely any of us have a copy of LightWave, so you're the best person to debug it :)
thanks -mike
Could a limit of attachment size be set, like the wine-users list has ? ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight Spam ! EuroCauce: http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Mike, I just spoke with Newtek this morning and they said that they are actually going to post a trial version of LightWave this week, around Wednesday or Thursday! So that's a real plus for this. Also, you are right it appears that they do use their own widget library, however Window's widgets do appear to be used for some dialogs. Hopefully with this trial becoming available we can work through this. -George On Monday, March 10, 2003, at 04:31 AM, Mike Hearn wrote:
Visually and User Interface wise, some issues I see right off the top are things such as:
Doesn't LightWave use its own widget library? I seem to recall it's not a "native windows app" in that respect.
The Hub application is also a bit problematic as it resides in the tray. It does sit in my KDE 3.1 tray, which is neat,
It does? Looks like KDE kept backwards compatability with the old protocol then. Interesting.
but when I right click it and tell it to exit, it does not quit so I end up having to kill all wine processes manually. But the hub is the least of my concerns :) and I realize that tray apps don't work quite right yet.
They should work fine, at least in KDE. That sounds more like a problem with quitting than the tray.
I would be very happy to provide input, test and debug fixes if someone is able to provide patches and help for these issues. I am using a cvs version of wine from about 1.5 weeks ago. I have also tried winex cvs and it exhibits many, if not all of the same issues. Winex may be slightly faster in terms of its directdraw functionality as LightWave uses directdraw.
Please advise if someone is willing to work through these issues with me and I will be happy to go out an acquire any information needed to get started.
To be honest, debugging is something best done by somebody familiar with the app, and who actually has a copy. I don't know how much experience with coding you have, but I'd suggest you read the the wine users guide and developers guide, those give an intro to debugging and sit down and work through the problems. For crashes, try using winedbg to get a backtrace, if you can get a good backtrace that can help with crashes. They look like:
==> 1) function call ..... ebp=.... 2) another function call ..... 3) etc etc
Otherwise try filing bugs in bugzilla related to the individual issues. Unless there is a demo version somewhere, it's unlikely any of us have a copy of LightWave, so you're the best person to debug it :)
thanks -mike
On Mon, 2003-03-10 at 16:52, George D.Plymale wrote:
Mike,
I just spoke with Newtek this morning and they said that they are actually going to post a trial version of LightWave this week, around Wednesday or Thursday! So that's a real plus for this. Also, you are right it appears that they do use their own widget library, however Window's widgets do appear to be used for some dialogs.
Hopefully with this trial becoming available we can work through this.
-George
As I have said before, you'll probably have to do this yourself. Unless you can find a developer to debug it for you, it's safe to assume we're all busy with other things. This happens every so often, sometimes somebody gets interested and pops up with some patches or notes, but it's by no means guaranteed. -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center
participants (4)
-
George D.Plymale -
Mike Hearn -
Sylvain Petreolle -
Vincent Béron