On Thu, Feb 5, 2009 at 11:54 AM, antoniong <wineforum-user@xxxxxxxxxx> wrote: > > austin987 wrote: >> >> Like I said, it's doable, plenty of apps do this, but should Wine be >> fixed, it will break your app. Detecting the broken behavior is a >> better solution, and fixing Wine is the best. >> >> -- >> -Austin > > > Apparently you don't want to understand the quintessens of the problem. Your solution maybe fine for wine but for an enduser is is no solution whatsoever. The user does not care a bit about Wine for him it is a fix for a singualr problem. That's all. Actually, it's the end developer that you're worried about, not the end user. The end user won't be adding this workaround in their code. I do understand, but preparing you for the reality of your 'solution'. > Do you have any experience as an enduser or do you feel like the allmighty God developer? Open up your eyes! Yes. I started as a user, and have learned a lot from working with Wine. I've used similar workarounds for testing Wine in an automated fashion, since our tab behavior is apparently broken. You can check for the "SHELL" environmental variable (or really any that *nix has that windows doesn't), or check for Wine specific registry entries. Again, it's a very dangerous practice. If you test for the the broken behavior (which can occur on Windows as well), you won't risk breaking Wine in the future, and also fix the app for broken Windows machines. -- -Austin
