I'm wondering what the user driver functions GetScreenSaveActive and SetScreenSaveActive are supposed to do. I have an implementation against CodeWeaver's changes to Wine and I just want to make sure that I'm making the functions properly.
First is GetScreenStateActive. Does it check for if the screen saver is disabled for the whole system or just the app.
And SetScreenStateActive. Is it supposed to set the activity for the whole system (I.E. if two apps call SetScreenStateActive to yes, then one to no, does the screen saver run) or is it per-app?
On Jan 19, 2013, at 1:09 PM, C.W. Betts wrote:
I'm wondering what the user driver functions GetScreenSaveActive and SetScreenSaveActive are supposed to do. I have an implementation against CodeWeaver's changes to Wine and I just want to make sure that I'm making the functions properly.
How should we know? (Well, those of us who don't work at CW anyway.) USER drivers don't even have those in (unmodified) Wine.
I'm sorry if I come across as rude, but this mailing list is for plain Wine. If you have a question about CrossOver Wine, you should ask CodeWeavers. I'm sure that somewhere on their website, they have an email or a mailing list you can contact them with.
Chip
I'm sorry if my intention was not clear: I want to implement this on vanilla Wine, I just did the initial work on CodeWeaver's code. But if the functions aren't on Vanilla, I guess there's no use pushing the patch here. On Jan 19, 2013, at 1:23 PM, Charles Davis cdavis5x@gmail.com wrote:
On Jan 19, 2013, at 1:09 PM, C.W. Betts wrote:
I'm wondering what the user driver functions GetScreenSaveActive and SetScreenSaveActive are supposed to do. I have an implementation against CodeWeaver's changes to Wine and I just want to make sure that I'm making the functions properly.
How should we know? (Well, those of us who don't work at CW anyway.) USER drivers don't even have those in (unmodified) Wine.
I'm sorry if I come across as rude, but this mailing list is for plain Wine. If you have a question about CrossOver Wine, you should ask CodeWeavers. I'm sure that somewhere on their website, they have an email or a mailing list you can contact them with.
Chip
Although, looking through the X11 Driver, there is a function that does check for the screen saver activity, it's just not two functions: SystemParametersInfo. I'll see if I can't get a patch put out.
Also, what would be a good way to do this? Should I split the code into a new file or put it in macdrv_main.c? It does include a new header, as well as declare a static variable (Tell me if that's a no-no and I'll see if I can work around it). Also, the Mac driver would have to link to IOKit. On Jan 19, 2013, at 1:27 PM, "C.W. Betts" computers57@hotmail.com wrote:
I'm sorry if my intention was not clear: I want to implement this on vanilla Wine, I just did the initial work on CodeWeaver's code. But if the functions aren't on Vanilla, I guess there's no use pushing the patch here. On Jan 19, 2013, at 1:23 PM, Charles Davis cdavis5x@gmail.com wrote:
On Jan 19, 2013, at 1:09 PM, C.W. Betts wrote:
I'm wondering what the user driver functions GetScreenSaveActive and SetScreenSaveActive are supposed to do. I have an implementation against CodeWeaver's changes to Wine and I just want to make sure that I'm making the functions properly.
How should we know? (Well, those of us who don't work at CW anyway.) USER drivers don't even have those in (unmodified) Wine.
I'm sorry if I come across as rude, but this mailing list is for plain Wine. If you have a question about CrossOver Wine, you should ask CodeWeavers. I'm sure that somewhere on their website, they have an email or a mailing list you can contact them with.
Chip
-
C.W. Betts -
Charles Davis