austin987 wrote: > > Right, but if the bug is fixed in Wine later on, then the app may > behave unexpectedly. What if some windows machines have similar bugs > (many often do). They won't receive that fix either. > The proper thing to do would be detect the broken behavior and work > around it, not detect Wine. But if you have a workaround, that should > be the default behavior, so your app works the same in Windows and > Wine. > -- > -Austin No doubt, your point of view is the correct one and it is the official standpoint. BUT! There are people that have only 1 interest and that is that a Windows app they are using can be run under Linux. Also it happens that the programm developer has not much interest in this but is willing to look into the matter and (if easy dooble) is willing to enhance his app to make a divergence based on "Wine yes/No". If a simple solution like this can be realised than the developer is happy, the user is happy and no one has any else needs to have any problems with it. More important, the solution would be today and immediate and not dependent of the will of somebody to either correct Wine behaviour or correct a module coming from again another party that has no interest in repairing at all. It is the will of the user that should count and certainly Wine should not block this. (And keep in mind that the chance is likely that this problem situation arises in only 1 particular combination that only a handfull of users are experiencing)
