| Groups | Blog | Home |
dotnet compact framework : Power control question
by setting registry values then using the OpenNETCF CreateEvent and SetEvent for "SDKBackLightChangeEvent" to make it take effect. Now I need to control the power-off timeouts too. I have 2 questions: 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't work. It seems to be the case that this only works if "GWES is enabled", which I think means you ONLY have the standard registry entries set in HKLM/System/CurrentControlSet/Control/Power. If you ALSO have the .../Control/Power/Timeouts keys set, as my device does, those take precedence and cause the reset API call to do nothing. And making changes manually in Settings/Power control panel only affects the Control/Power/Timeouts keys, not the Control/Power keys. Is this common on many PocketPC devices? Control/Power: ExtPowerOff BattPowerOff WakeupPowerOff vs. Control/Power/Timeouts: BattSuspendTimeout ACSuspendTimeout 2. I can set the right registry keys, but what's the equivalent event message I can send for power-timeout changes to make it take effect, as I do for brightness changes? -- Tim Johnson High Point Software, Inc. www.high-point.com (503) 312-8625
broadcast a WM_SETTINGCHANGE message
-Chris [quoted text, click to view] "Tim Johnson" <tjohnson@high-point.com> wrote in message news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... > I'm setting the backlight brightness values and screen-dimming timeouts > ok, by setting registry values then using the OpenNETCF CreateEvent and > SetEvent for "SDKBackLightChangeEvent" to make it take effect. Now I need > to control the power-off timeouts too. I have 2 questions: > > 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't work. > It seems to be the case that this only works if "GWES is enabled", which I > think means you ONLY have the standard registry entries set in > HKLM/System/CurrentControlSet/Control/Power. If you ALSO have the > ../Control/Power/Timeouts keys set, as my device does, those take > precedence and cause the reset API call to do nothing. And making changes > manually in Settings/Power control panel only affects the > Control/Power/Timeouts keys, not the Control/Power keys. Is this common > on many PocketPC devices? > > Control/Power: > ExtPowerOff > BattPowerOff > WakeupPowerOff > > vs. > > Control/Power/Timeouts: > BattSuspendTimeout > ACSuspendTimeout > > 2. I can set the right registry keys, but what's the equivalent event > message I can send for power-timeout changes to make it take effect, as I > do for brightness changes? > > -- > > Tim Johnson > High Point Software, Inc. > www.high-point.com > (503) 312-8625 > > >
Thanks, I'll try that. Seems a little odd though, doesn't that just send a
message to all top-level windows running? So it notifies running apps, but all I really want to do is notify the operating system about the new power control timeout settings. Doesn't seem like any other app would really care about that, only the OS. -- Tim Johnson High Point Software, Inc. www.high-point.com (503) 312-8625 [quoted text, click to view] "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... > broadcast a WM_SETTINGCHANGE message > > -Chris > > "Tim Johnson" <tjohnson@high-point.com> wrote in message > news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >> I'm setting the backlight brightness values and screen-dimming timeouts >> ok, by setting registry values then using the OpenNETCF CreateEvent and >> SetEvent for "SDKBackLightChangeEvent" to make it take effect. Now I >> need to control the power-off timeouts too. I have 2 questions: >> >> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't >> work. It seems to be the case that this only works if "GWES is enabled", >> which I think means you ONLY have the standard registry entries set in >> HKLM/System/CurrentControlSet/Control/Power. If you ALSO have the >> ../Control/Power/Timeouts keys set, as my device does, those take >> precedence and cause the reset API call to do nothing. And making >> changes manually in Settings/Power control panel only affects the >> Control/Power/Timeouts keys, not the Control/Power keys. Is this common >> on many PocketPC devices? >> >> Control/Power: >> ExtPowerOff >> BattPowerOff >> WakeupPowerOff >> >> vs. >> >> Control/Power/Timeouts: >> BattSuspendTimeout >> ACSuspendTimeout >> >> 2. I can set the right registry keys, but what's the equivalent event >> message I can send for power-timeout changes to make it take effect, as I >> do for brightness changes? >> >> -- >> >> Tim Johnson >> High Point Software, Inc. >> www.high-point.com >> (503) 312-8625 >> >> >> > >
I tried that but it doesn't seem to actually take effect. I can see in the
registry that I've correctly changed the values, and when I bring up the control panel in Settings/Power I see the settings I configured thru my program. So for example everything shows it will power-down on either battery or AC after 1 minute - but it never does. Maybe it's the lParam I'm using in the following calls? I can't get a straight story on what to use here, as in this example: OpenNETCF.Win32.RegistryKey key; //Set timeouts in /Power/Timeouts registry area key = OpenNETCF.Win32.Registry.LocalMachine.OpenSubKey (@"\System\CurrentControlSet\Control\Power\Timeouts", true); key.SetValue("BattPowerOff", 60); key.Close(); rc = PostMessage ( (System.IntPtr)HWND_BROADCAST, WM_SETTINGCHANGE, 0, "Timeouts"); I do this for both the keys in /Power and the other keys in Power/Timeouts. I have the correct dllimport and constants defined from other newsgroup samples, and I can see a "true" value come back from the PostMessage call in the debugger. I've used "Timeouts" and "Power" and "Environment" as lParam, but still no actual behavior change on the PDA. Any suggestions? -- Tim Johnson High Point Software, Inc. www.high-point.com (503) 312-8625 [quoted text, click to view] "Tim Johnson" <tjohnson@high-point.com> wrote in message news:egj3EKcTFHA.228@TK2MSFTNGP12.phx.gbl... > Thanks, I'll try that. Seems a little odd though, doesn't that just send > a message to all top-level windows running? So it notifies running apps, > but all I really want to do is notify the operating system about the new > power control timeout settings. Doesn't seem like any other app would > really care about that, only the OS. > > -- > > Tim Johnson > High Point Software, Inc. > www.high-point.com > (503) 312-8625 > > > "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message > news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... >> broadcast a WM_SETTINGCHANGE message >> >> -Chris >> >> "Tim Johnson" <tjohnson@high-point.com> wrote in message >> news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >>> I'm setting the backlight brightness values and screen-dimming timeouts >>> ok, by setting registry values then using the OpenNETCF CreateEvent and >>> SetEvent for "SDKBackLightChangeEvent" to make it take effect. Now I >>> need to control the power-off timeouts too. I have 2 questions: >>> >>> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't >>> work. It seems to be the case that this only works if "GWES is enabled", >>> which I think means you ONLY have the standard registry entries set in >>> HKLM/System/CurrentControlSet/Control/Power. If you ALSO have the >>> ../Control/Power/Timeouts keys set, as my device does, those take >>> precedence and cause the reset API call to do nothing. And making >>> changes manually in Settings/Power control panel only affects the >>> Control/Power/Timeouts keys, not the Control/Power keys. Is this common >>> on many PocketPC devices? >>> >>> Control/Power: >>> ExtPowerOff >>> BattPowerOff >>> WakeupPowerOff >>> >>> vs. >>> >>> Control/Power/Timeouts: >>> BattSuspendTimeout >>> ACSuspendTimeout >>> >>> 2. I can set the right registry keys, but what's the equivalent event >>> message I can send for power-timeout changes to make it take effect, as >>> I do for brightness changes? >>> >>> -- >>> >>> Tim Johnson >>> High Point Software, Inc. >>> www.high-point.com >>> (503) 312-8625 >>> >>> >>> >> >> > >
I'd think LParam and WParam could both be zero. At this point the place I'd
go is to the source for the control panel applet itself that adjusts these (part of Platform Builder). Typically they broadcast the event and the shell itself catches it and knows to re-read registry values. Evidently it doesn't work that way in this case. -Chris [quoted text, click to view] "Tim Johnson" <tjohnson@high-point.com> wrote in message news:%23OWN8BdTFHA.1896@TK2MSFTNGP14.phx.gbl... >I tried that but it doesn't seem to actually take effect. I can see in the >registry that I've correctly changed the values, and when I bring up the >control panel in Settings/Power I see the settings I configured thru my >program. So for example everything shows it will power-down on either >battery or AC after 1 minute - but it never does. > > Maybe it's the lParam I'm using in the following calls? I can't get a > straight story on what to use here, as in this example: > > OpenNETCF.Win32.RegistryKey key; > > //Set timeouts in /Power/Timeouts registry area > > key = OpenNETCF.Win32.Registry.LocalMachine.OpenSubKey > > (@"\System\CurrentControlSet\Control\Power\Timeouts", true); > > key.SetValue("BattPowerOff", 60); > > key.Close(); > > rc = PostMessage ( (System.IntPtr)HWND_BROADCAST, WM_SETTINGCHANGE, 0, > "Timeouts"); > > I do this for both the keys in /Power and the other keys in > Power/Timeouts. I have the correct dllimport and constants defined from > other newsgroup samples, and I can see a "true" value come back from the > PostMessage call in the debugger. I've used "Timeouts" and "Power" and > "Environment" as lParam, but still no actual behavior change on the PDA. > Any suggestions? > -- > > Tim Johnson > High Point Software, Inc. > www.high-point.com > (503) 312-8625 > > > "Tim Johnson" <tjohnson@high-point.com> wrote in message > news:egj3EKcTFHA.228@TK2MSFTNGP12.phx.gbl... >> Thanks, I'll try that. Seems a little odd though, doesn't that just send >> a message to all top-level windows running? So it notifies running apps, >> but all I really want to do is notify the operating system about the new >> power control timeout settings. Doesn't seem like any other app would >> really care about that, only the OS. >> >> -- >> >> Tim Johnson >> High Point Software, Inc. >> www.high-point.com >> (503) 312-8625 >> >> >> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >> news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... >>> broadcast a WM_SETTINGCHANGE message >>> >>> -Chris >>> >>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>> news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >>>> I'm setting the backlight brightness values and screen-dimming timeouts >>>> ok, by setting registry values then using the OpenNETCF CreateEvent and >>>> SetEvent for "SDKBackLightChangeEvent" to make it take effect. Now I >>>> need to control the power-off timeouts too. I have 2 questions: >>>> >>>> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't >>>> work. It seems to be the case that this only works if "GWES is >>>> enabled", which I think means you ONLY have the standard registry >>>> entries set in HKLM/System/CurrentControlSet/Control/Power. If you >>>> ALSO have the ../Control/Power/Timeouts keys set, as my device does, >>>> those take precedence and cause the reset API call to do nothing. And >>>> making changes manually in Settings/Power control panel only affects >>>> the Control/Power/Timeouts keys, not the Control/Power keys. Is this >>>> common on many PocketPC devices? >>>> >>>> Control/Power: >>>> ExtPowerOff >>>> BattPowerOff >>>> WakeupPowerOff >>>> >>>> vs. >>>> >>>> Control/Power/Timeouts: >>>> BattSuspendTimeout >>>> ACSuspendTimeout >>>> >>>> 2. I can set the right registry keys, but what's the equivalent event >>>> message I can send for power-timeout changes to make it take effect, as >>>> I do for brightness changes? >>>> >>>> -- >>>> >>>> Tim Johnson >>>> High Point Software, Inc. >>>> www.high-point.com >>>> (503) 312-8625 >>>> >>>> >>>> >>> >>> >> >> > >
I'll try both zeroes. Do you know where could I find PB source?
-- Tim Johnson High Point Software, Inc. www.high-point.com (503) 312-8625 [quoted text, click to view] "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message news:eSfLsRfTFHA.2520@TK2MSFTNGP09.phx.gbl... > I'd think LParam and WParam could both be zero. At this point the place > I'd go is to the source for the control panel applet itself that adjusts > these (part of Platform Builder). Typically they broadcast the event and > the shell itself catches it and knows to re-read registry values. > Evidently it doesn't work that way in this case. > > -Chris > > > "Tim Johnson" <tjohnson@high-point.com> wrote in message > news:%23OWN8BdTFHA.1896@TK2MSFTNGP14.phx.gbl... >>I tried that but it doesn't seem to actually take effect. I can see in >>the registry that I've correctly changed the values, and when I bring up >>the control panel in Settings/Power I see the settings I configured thru >>my program. So for example everything shows it will power-down on either >>battery or AC after 1 minute - but it never does. >> >> Maybe it's the lParam I'm using in the following calls? I can't get a >> straight story on what to use here, as in this example: >> >> OpenNETCF.Win32.RegistryKey key; >> >> //Set timeouts in /Power/Timeouts registry area >> >> key = OpenNETCF.Win32.Registry.LocalMachine.OpenSubKey >> >> (@"\System\CurrentControlSet\Control\Power\Timeouts", true); >> >> key.SetValue("BattPowerOff", 60); >> >> key.Close(); >> >> rc = PostMessage ( (System.IntPtr)HWND_BROADCAST, WM_SETTINGCHANGE, 0, >> "Timeouts"); >> >> I do this for both the keys in /Power and the other keys in >> Power/Timeouts. I have the correct dllimport and constants defined from >> other newsgroup samples, and I can see a "true" value come back from the >> PostMessage call in the debugger. I've used "Timeouts" and "Power" and >> "Environment" as lParam, but still no actual behavior change on the PDA. >> Any suggestions? >> -- >> >> Tim Johnson >> High Point Software, Inc. >> www.high-point.com >> (503) 312-8625 >> >> >> "Tim Johnson" <tjohnson@high-point.com> wrote in message >> news:egj3EKcTFHA.228@TK2MSFTNGP12.phx.gbl... >>> Thanks, I'll try that. Seems a little odd though, doesn't that just >>> send a message to all top-level windows running? So it notifies running >>> apps, but all I really want to do is notify the operating system about >>> the new power control timeout settings. Doesn't seem like any other app >>> would really care about that, only the OS. >>> >>> -- >>> >>> Tim Johnson >>> High Point Software, Inc. >>> www.high-point.com >>> (503) 312-8625 >>> >>> >>> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >>> news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... >>>> broadcast a WM_SETTINGCHANGE message >>>> >>>> -Chris >>>> >>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>> news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >>>>> I'm setting the backlight brightness values and screen-dimming >>>>> timeouts ok, by setting registry values then using the OpenNETCF >>>>> CreateEvent and SetEvent for "SDKBackLightChangeEvent" to make it take >>>>> effect. Now I need to control the power-off timeouts too. I have 2 >>>>> questions: >>>>> >>>>> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't >>>>> work. It seems to be the case that this only works if "GWES is >>>>> enabled", which I think means you ONLY have the standard registry >>>>> entries set in HKLM/System/CurrentControlSet/Control/Power. If you >>>>> ALSO have the ../Control/Power/Timeouts keys set, as my device does, >>>>> those take precedence and cause the reset API call to do nothing. And >>>>> making changes manually in Settings/Power control panel only affects >>>>> the Control/Power/Timeouts keys, not the Control/Power keys. Is this >>>>> common on many PocketPC devices? >>>>> >>>>> Control/Power: >>>>> ExtPowerOff >>>>> BattPowerOff >>>>> WakeupPowerOff >>>>> >>>>> vs. >>>>> >>>>> Control/Power/Timeouts: >>>>> BattSuspendTimeout >>>>> ACSuspendTimeout >>>>> >>>>> 2. I can set the right registry keys, but what's the equivalent event >>>>> message I can send for power-timeout changes to make it take effect, >>>>> as I do for brightness changes? >>>>> >>>>> -- >>>>> >>>>> Tim Johnson >>>>> High Point Software, Inc. >>>>> www.high-point.com >>>>> (503) 312-8625 >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
Excellent, thanks. And the 0's did seem to work, except no matter I do I
can't make the AudioVox PocketPC Phone Edition pda do a power-off while on AC power. I think it's a model issue. Changing the Battery power timeout works fine now though. For the app we're building I really needed control of two things - before the user logs in but has started the app I want to power-down after 1 minute; but after he logs in I never want to power down because we're busy collecting GPS readings. Now I have almost all that, and if it can't power-down while on AC power I guess that's not a big deal. Thanks again. -- Tim Johnson High Point Software, Inc. www.high-point.com (503) 312-8625 [quoted text, click to view] "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message news:%23khzf6nTFHA.4056@TK2MSFTNGP15.phx.gbl... > You do enough work that I'd recommend ordering the eval CDs from > Microsoft. It's something like $10 and is a 120 day eval, but you're using > it for a source reference, so that won't affect you. > > -Chris > > > "Tim Johnson" <tjohnson@high-point.com> wrote in message > news:%23Ko7nunTFHA.1148@tk2msftngp13.phx.gbl... >> I'll try both zeroes. Do you know where could I find PB source? >> >> -- >> >> Tim Johnson >> High Point Software, Inc. >> www.high-point.com >> (503) 312-8625 >> >> >> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >> news:eSfLsRfTFHA.2520@TK2MSFTNGP09.phx.gbl... >>> I'd think LParam and WParam could both be zero. At this point the place >>> I'd go is to the source for the control panel applet itself that adjusts >>> these (part of Platform Builder). Typically they broadcast the event >>> and the shell itself catches it and knows to re-read registry values. >>> Evidently it doesn't work that way in this case. >>> >>> -Chris >>> >>> >>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>> news:%23OWN8BdTFHA.1896@TK2MSFTNGP14.phx.gbl... >>>>I tried that but it doesn't seem to actually take effect. I can see in >>>>the registry that I've correctly changed the values, and when I bring up >>>>the control panel in Settings/Power I see the settings I configured thru >>>>my program. So for example everything shows it will power-down on >>>>either battery or AC after 1 minute - but it never does. >>>> >>>> Maybe it's the lParam I'm using in the following calls? I can't get a >>>> straight story on what to use here, as in this example: >>>> >>>> OpenNETCF.Win32.RegistryKey key; >>>> >>>> //Set timeouts in /Power/Timeouts registry area >>>> >>>> key = OpenNETCF.Win32.Registry.LocalMachine.OpenSubKey >>>> >>>> (@"\System\CurrentControlSet\Control\Power\Timeouts", true); >>>> >>>> key.SetValue("BattPowerOff", 60); >>>> >>>> key.Close(); >>>> >>>> rc = PostMessage ( (System.IntPtr)HWND_BROADCAST, WM_SETTINGCHANGE, 0, >>>> "Timeouts"); >>>> >>>> I do this for both the keys in /Power and the other keys in >>>> Power/Timeouts. I have the correct dllimport and constants defined from >>>> other newsgroup samples, and I can see a "true" value come back from >>>> the PostMessage call in the debugger. I've used "Timeouts" and "Power" >>>> and "Environment" as lParam, but still no actual behavior change on the >>>> PDA. Any suggestions? >>>> -- >>>> >>>> Tim Johnson >>>> High Point Software, Inc. >>>> www.high-point.com >>>> (503) 312-8625 >>>> >>>> >>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>> news:egj3EKcTFHA.228@TK2MSFTNGP12.phx.gbl... >>>>> Thanks, I'll try that. Seems a little odd though, doesn't that just >>>>> send a message to all top-level windows running? So it notifies >>>>> running apps, but all I really want to do is notify the operating >>>>> system about the new power control timeout settings. Doesn't seem >>>>> like any other app would really care about that, only the OS. >>>>> >>>>> -- >>>>> >>>>> Tim Johnson >>>>> High Point Software, Inc. >>>>> www.high-point.com >>>>> (503) 312-8625 >>>>> >>>>> >>>>> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >>>>> news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... >>>>>> broadcast a WM_SETTINGCHANGE message >>>>>> >>>>>> -Chris >>>>>> >>>>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>>>> news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >>>>>>> I'm setting the backlight brightness values and screen-dimming >>>>>>> timeouts ok, by setting registry values then using the OpenNETCF >>>>>>> CreateEvent and SetEvent for "SDKBackLightChangeEvent" to make it >>>>>>> take effect. Now I need to control the power-off timeouts too. I >>>>>>> have 2 questions: >>>>>>> >>>>>>> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't >>>>>>> work. It seems to be the case that this only works if "GWES is >>>>>>> enabled", which I think means you ONLY have the standard registry >>>>>>> entries set in HKLM/System/CurrentControlSet/Control/Power. If you >>>>>>> ALSO have the ../Control/Power/Timeouts keys set, as my device does, >>>>>>> those take precedence and cause the reset API call to do nothing. >>>>>>> And making changes manually in Settings/Power control panel only >>>>>>> affects the Control/Power/Timeouts keys, not the Control/Power keys. >>>>>>> Is this common on many PocketPC devices? >>>>>>> >>>>>>> Control/Power: >>>>>>> ExtPowerOff >>>>>>> BattPowerOff >>>>>>> WakeupPowerOff >>>>>>> >>>>>>> vs. >>>>>>> >>>>>>> Control/Power/Timeouts: >>>>>>> BattSuspendTimeout >>>>>>> ACSuspendTimeout >>>>>>> >>>>>>> 2. I can set the right registry keys, but what's the equivalent >>>>>>> event message I can send for power-timeout changes to make it take >>>>>>> effect, as I do for brightness changes? >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Tim Johnson >>>>>>> High Point Software, Inc. >>>>>>> www.high-point.com >>>>>>> (503) 312-8625 >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
You do enough work that I'd recommend ordering the eval CDs from Microsoft.
It's something like $10 and is a 120 day eval, but you're using it for a source reference, so that won't affect you. -Chris [quoted text, click to view] "Tim Johnson" <tjohnson@high-point.com> wrote in message news:%23Ko7nunTFHA.1148@tk2msftngp13.phx.gbl... > I'll try both zeroes. Do you know where could I find PB source? > > -- > > Tim Johnson > High Point Software, Inc. > www.high-point.com > (503) 312-8625 > > > "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message > news:eSfLsRfTFHA.2520@TK2MSFTNGP09.phx.gbl... >> I'd think LParam and WParam could both be zero. At this point the place >> I'd go is to the source for the control panel applet itself that adjusts >> these (part of Platform Builder). Typically they broadcast the event and >> the shell itself catches it and knows to re-read registry values. >> Evidently it doesn't work that way in this case. >> >> -Chris >> >> >> "Tim Johnson" <tjohnson@high-point.com> wrote in message >> news:%23OWN8BdTFHA.1896@TK2MSFTNGP14.phx.gbl... >>>I tried that but it doesn't seem to actually take effect. I can see in >>>the registry that I've correctly changed the values, and when I bring up >>>the control panel in Settings/Power I see the settings I configured thru >>>my program. So for example everything shows it will power-down on either >>>battery or AC after 1 minute - but it never does. >>> >>> Maybe it's the lParam I'm using in the following calls? I can't get a >>> straight story on what to use here, as in this example: >>> >>> OpenNETCF.Win32.RegistryKey key; >>> >>> //Set timeouts in /Power/Timeouts registry area >>> >>> key = OpenNETCF.Win32.Registry.LocalMachine.OpenSubKey >>> >>> (@"\System\CurrentControlSet\Control\Power\Timeouts", true); >>> >>> key.SetValue("BattPowerOff", 60); >>> >>> key.Close(); >>> >>> rc = PostMessage ( (System.IntPtr)HWND_BROADCAST, WM_SETTINGCHANGE, 0, >>> "Timeouts"); >>> >>> I do this for both the keys in /Power and the other keys in >>> Power/Timeouts. I have the correct dllimport and constants defined from >>> other newsgroup samples, and I can see a "true" value come back from the >>> PostMessage call in the debugger. I've used "Timeouts" and "Power" and >>> "Environment" as lParam, but still no actual behavior change on the PDA. >>> Any suggestions? >>> -- >>> >>> Tim Johnson >>> High Point Software, Inc. >>> www.high-point.com >>> (503) 312-8625 >>> >>> >>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>> news:egj3EKcTFHA.228@TK2MSFTNGP12.phx.gbl... >>>> Thanks, I'll try that. Seems a little odd though, doesn't that just >>>> send a message to all top-level windows running? So it notifies >>>> running apps, but all I really want to do is notify the operating >>>> system about the new power control timeout settings. Doesn't seem like >>>> any other app would really care about that, only the OS. >>>> >>>> -- >>>> >>>> Tim Johnson >>>> High Point Software, Inc. >>>> www.high-point.com >>>> (503) 312-8625 >>>> >>>> >>>> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >>>> news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... >>>>> broadcast a WM_SETTINGCHANGE message >>>>> >>>>> -Chris >>>>> >>>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>>> news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >>>>>> I'm setting the backlight brightness values and screen-dimming >>>>>> timeouts ok, by setting registry values then using the OpenNETCF >>>>>> CreateEvent and SetEvent for "SDKBackLightChangeEvent" to make it >>>>>> take effect. Now I need to control the power-off timeouts too. I >>>>>> have 2 questions: >>>>>> >>>>>> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset doesn't >>>>>> work. It seems to be the case that this only works if "GWES is >>>>>> enabled", which I think means you ONLY have the standard registry >>>>>> entries set in HKLM/System/CurrentControlSet/Control/Power. If you >>>>>> ALSO have the ../Control/Power/Timeouts keys set, as my device does, >>>>>> those take precedence and cause the reset API call to do nothing. >>>>>> And making changes manually in Settings/Power control panel only >>>>>> affects the Control/Power/Timeouts keys, not the Control/Power keys. >>>>>> Is this common on many PocketPC devices? >>>>>> >>>>>> Control/Power: >>>>>> ExtPowerOff >>>>>> BattPowerOff >>>>>> WakeupPowerOff >>>>>> >>>>>> vs. >>>>>> >>>>>> Control/Power/Timeouts: >>>>>> BattSuspendTimeout >>>>>> ACSuspendTimeout >>>>>> >>>>>> 2. I can set the right registry keys, but what's the equivalent event >>>>>> message I can send for power-timeout changes to make it take effect, >>>>>> as I do for brightness changes? >>>>>> >>>>>> -- >>>>>> >>>>>> Tim Johnson >>>>>> High Point Software, Inc. >>>>>> www.high-point.com >>>>>> (503) 312-8625 >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
Actually there is still a problem. The settings changes I make only take
effect AFTER I tap the screen. This applies to brightness, where the effect is obvious, but also to power timeouts. So if I change the brightness from bright to dim and change power timeout from never to 1 minute, but don't tap the screen, then a) screen stays bright, and b) device never hibernates. If I do the same change and tap the screen, the screen goes dim as requested and then it hibernates after 1 minute. Any thoughts on this one? -- Tim Johnson High Point Software, Inc. www.high-point.com (503) 312-8625 [quoted text, click to view] "Tim Johnson" <tjohnson@high-point.com> wrote in message news:%238iqEwoTFHA.612@TK2MSFTNGP12.phx.gbl... > Excellent, thanks. And the 0's did seem to work, except no matter I do I > can't make the AudioVox PocketPC Phone Edition pda do a power-off while on > AC power. I think it's a model issue. Changing the Battery power timeout > works fine now though. For the app we're building I really needed control > of two things - before the user logs in but has started the app I want to > power-down after 1 minute; but after he logs in I never want to power down > because we're busy collecting GPS readings. Now I have almost all that, > and if it can't power-down while on AC power I guess that's not a big > deal. > > Thanks again. > > -- > > Tim Johnson > High Point Software, Inc. > www.high-point.com > (503) 312-8625 > > > "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message > news:%23khzf6nTFHA.4056@TK2MSFTNGP15.phx.gbl... >> You do enough work that I'd recommend ordering the eval CDs from >> Microsoft. It's something like $10 and is a 120 day eval, but you're >> using it for a source reference, so that won't affect you. >> >> -Chris >> >> >> "Tim Johnson" <tjohnson@high-point.com> wrote in message >> news:%23Ko7nunTFHA.1148@tk2msftngp13.phx.gbl... >>> I'll try both zeroes. Do you know where could I find PB source? >>> >>> -- >>> >>> Tim Johnson >>> High Point Software, Inc. >>> www.high-point.com >>> (503) 312-8625 >>> >>> >>> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >>> news:eSfLsRfTFHA.2520@TK2MSFTNGP09.phx.gbl... >>>> I'd think LParam and WParam could both be zero. At this point the >>>> place I'd go is to the source for the control panel applet itself that >>>> adjusts these (part of Platform Builder). Typically they broadcast the >>>> event and the shell itself catches it and knows to re-read registry >>>> values. Evidently it doesn't work that way in this case. >>>> >>>> -Chris >>>> >>>> >>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>> news:%23OWN8BdTFHA.1896@TK2MSFTNGP14.phx.gbl... >>>>>I tried that but it doesn't seem to actually take effect. I can see in >>>>>the registry that I've correctly changed the values, and when I bring >>>>>up the control panel in Settings/Power I see the settings I configured >>>>>thru my program. So for example everything shows it will power-down on >>>>>either battery or AC after 1 minute - but it never does. >>>>> >>>>> Maybe it's the lParam I'm using in the following calls? I can't get a >>>>> straight story on what to use here, as in this example: >>>>> >>>>> OpenNETCF.Win32.RegistryKey key; >>>>> >>>>> //Set timeouts in /Power/Timeouts registry area >>>>> >>>>> key = OpenNETCF.Win32.Registry.LocalMachine.OpenSubKey >>>>> >>>>> (@"\System\CurrentControlSet\Control\Power\Timeouts", true); >>>>> >>>>> key.SetValue("BattPowerOff", 60); >>>>> >>>>> key.Close(); >>>>> >>>>> rc = PostMessage ( (System.IntPtr)HWND_BROADCAST, WM_SETTINGCHANGE, 0, >>>>> "Timeouts"); >>>>> >>>>> I do this for both the keys in /Power and the other keys in >>>>> Power/Timeouts. I have the correct dllimport and constants defined >>>>> from other newsgroup samples, and I can see a "true" value come back >>>>> from the PostMessage call in the debugger. I've used "Timeouts" and >>>>> "Power" and "Environment" as lParam, but still no actual behavior >>>>> change on the PDA. Any suggestions? >>>>> -- >>>>> >>>>> Tim Johnson >>>>> High Point Software, Inc. >>>>> www.high-point.com >>>>> (503) 312-8625 >>>>> >>>>> >>>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>>> news:egj3EKcTFHA.228@TK2MSFTNGP12.phx.gbl... >>>>>> Thanks, I'll try that. Seems a little odd though, doesn't that just >>>>>> send a message to all top-level windows running? So it notifies >>>>>> running apps, but all I really want to do is notify the operating >>>>>> system about the new power control timeout settings. Doesn't seem >>>>>> like any other app would really care about that, only the OS. >>>>>> >>>>>> -- >>>>>> >>>>>> Tim Johnson >>>>>> High Point Software, Inc. >>>>>> www.high-point.com >>>>>> (503) 312-8625 >>>>>> >>>>>> >>>>>> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >>>>>> news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... >>>>>>> broadcast a WM_SETTINGCHANGE message >>>>>>> >>>>>>> -Chris >>>>>>> >>>>>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>>>>> news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >>>>>>>> I'm setting the backlight brightness values and screen-dimming >>>>>>>> timeouts ok, by setting registry values then using the OpenNETCF >>>>>>>> CreateEvent and SetEvent for "SDKBackLightChangeEvent" to make it >>>>>>>> take effect. Now I need to control the power-off timeouts too. I >>>>>>>> have 2 questions: >>>>>>>> >>>>>>>> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset >>>>>>>> doesn't work. It seems to be the case that this only works if "GWES >>>>>>>> is enabled", which I think means you ONLY have the standard >>>>>>>> registry entries set in >>>>>>>> HKLM/System/CurrentControlSet/Control/Power. If you ALSO have the >>>>>>>> ../Control/Power/Timeouts keys set, as my device does, those take >>>>>>>> precedence and cause the reset API call to do nothing. And making >>>>>>>> changes manually in Settings/Power control panel only affects the >>>>>>>> Control/Power/Timeouts keys, not the Control/Power keys. Is this >>>>>>>> common on many PocketPC devices? >>>>>>>> >>>>>>>> Control/Power: >>>>>>>> ExtPowerOff >>>>>>>> BattPowerOff >>>>>>>> WakeupPowerOff >>>>>>>> >>>>>>>> vs. >>>>>>>> >>>>>>>> Control/Power/Timeouts: >>>>>>>> BattSuspendTimeout >>>>>>>> ACSuspendTimeout >>>>>>>> >>>>>>>> 2. I can set the right registry keys, but what's the equivalent >>>>>>>> event message I can send for power-timeout changes to make it take >>>>>>>> effect, as I do for brightness changes? >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Tim Johnson >>>>>>>> High Point Software, Inc. >>>>>>>> www.high-point.com >>>>>>>> (503) 312-8625 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
You could P/Invoke mouse_event to simulate a screen tap e.g.:-
http://www.peterfoot.net/EmulateScreenTaps.aspx Peter -- Peter Foot Windows Embedded MVP http://www.inthehand.com | http://www.peterfoot.net | http://www.opennetcf.org [quoted text, click to view] "Tim Johnson" <tjohnson@high-point.com> wrote in message
news:%23MpEmnsTFHA.2680@tk2msftngp13.phx.gbl... > Actually there is still a problem. The settings changes I make only take > effect AFTER I tap the screen. This applies to brightness, where the > effect is obvious, but also to power timeouts. So if I change the > brightness from bright to dim and change power timeout from never to 1 > minute, but don't tap the screen, then a) screen stays bright, and b) > device never hibernates. If I do the same change and tap the screen, the > screen goes dim as requested and then it hibernates after 1 minute. Any > thoughts on this one? > > -- > > Tim Johnson > High Point Software, Inc. > www.high-point.com > (503) 312-8625 > > > "Tim Johnson" <tjohnson@high-point.com> wrote in message > news:%238iqEwoTFHA.612@TK2MSFTNGP12.phx.gbl... >> Excellent, thanks. And the 0's did seem to work, except no matter I do I >> can't make the AudioVox PocketPC Phone Edition pda do a power-off while >> on AC power. I think it's a model issue. Changing the Battery power >> timeout works fine now though. For the app we're building I really >> needed control of two things - before the user logs in but has started >> the app I want to power-down after 1 minute; but after he logs in I never >> want to power down because we're busy collecting GPS readings. Now I >> have almost all that, and if it can't power-down while on AC power I >> guess that's not a big deal. >> >> Thanks again. >> >> -- >> >> Tim Johnson >> High Point Software, Inc. >> www.high-point.com >> (503) 312-8625 >> >> >> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >> news:%23khzf6nTFHA.4056@TK2MSFTNGP15.phx.gbl... >>> You do enough work that I'd recommend ordering the eval CDs from >>> Microsoft. It's something like $10 and is a 120 day eval, but you're >>> using it for a source reference, so that won't affect you. >>> >>> -Chris >>> >>> >>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>> news:%23Ko7nunTFHA.1148@tk2msftngp13.phx.gbl... >>>> I'll try both zeroes. Do you know where could I find PB source? >>>> >>>> -- >>>> >>>> Tim Johnson >>>> High Point Software, Inc. >>>> www.high-point.com >>>> (503) 312-8625 >>>> >>>> >>>> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >>>> news:eSfLsRfTFHA.2520@TK2MSFTNGP09.phx.gbl... >>>>> I'd think LParam and WParam could both be zero. At this point the >>>>> place I'd go is to the source for the control panel applet itself that >>>>> adjusts these (part of Platform Builder). Typically they broadcast >>>>> the event and the shell itself catches it and knows to re-read >>>>> registry values. Evidently it doesn't work that way in this case. >>>>> >>>>> -Chris >>>>> >>>>> >>>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>>> news:%23OWN8BdTFHA.1896@TK2MSFTNGP14.phx.gbl... >>>>>>I tried that but it doesn't seem to actually take effect. I can see >>>>>>in the registry that I've correctly changed the values, and when I >>>>>>bring up the control panel in Settings/Power I see the settings I >>>>>>configured thru my program. So for example everything shows it will >>>>>>power-down on either battery or AC after 1 minute - but it never does. >>>>>> >>>>>> Maybe it's the lParam I'm using in the following calls? I can't get >>>>>> a straight story on what to use here, as in this example: >>>>>> >>>>>> OpenNETCF.Win32.RegistryKey key; >>>>>> >>>>>> //Set timeouts in /Power/Timeouts registry area >>>>>> >>>>>> key = OpenNETCF.Win32.Registry.LocalMachine.OpenSubKey >>>>>> >>>>>> (@"\System\CurrentControlSet\Control\Power\Timeouts", true); >>>>>> >>>>>> key.SetValue("BattPowerOff", 60); >>>>>> >>>>>> key.Close(); >>>>>> >>>>>> rc = PostMessage ( (System.IntPtr)HWND_BROADCAST, WM_SETTINGCHANGE, >>>>>> 0, "Timeouts"); >>>>>> >>>>>> I do this for both the keys in /Power and the other keys in >>>>>> Power/Timeouts. I have the correct dllimport and constants defined >>>>>> from other newsgroup samples, and I can see a "true" value come back >>>>>> from the PostMessage call in the debugger. I've used "Timeouts" and >>>>>> "Power" and "Environment" as lParam, but still no actual behavior >>>>>> change on the PDA. Any suggestions? >>>>>> -- >>>>>> >>>>>> Tim Johnson >>>>>> High Point Software, Inc. >>>>>> www.high-point.com >>>>>> (503) 312-8625 >>>>>> >>>>>> >>>>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>>>> news:egj3EKcTFHA.228@TK2MSFTNGP12.phx.gbl... >>>>>>> Thanks, I'll try that. Seems a little odd though, doesn't that just >>>>>>> send a message to all top-level windows running? So it notifies >>>>>>> running apps, but all I really want to do is notify the operating >>>>>>> system about the new power control timeout settings. Doesn't seem >>>>>>> like any other app would really care about that, only the OS. >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Tim Johnson >>>>>>> High Point Software, Inc. >>>>>>> www.high-point.com >>>>>>> (503) 312-8625 >>>>>>> >>>>>>> >>>>>>> "<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message >>>>>>> news:ORF6s5YTFHA.3544@TK2MSFTNGP12.phx.gbl... >>>>>>>> broadcast a WM_SETTINGCHANGE message >>>>>>>> >>>>>>>> -Chris >>>>>>>> >>>>>>>> "Tim Johnson" <tjohnson@high-point.com> wrote in message >>>>>>>> news:Ox4PgiVTFHA.2556@TK2MSFTNGP12.phx.gbl... >>>>>>>>> I'm setting the backlight brightness values and screen-dimming >>>>>>>>> timeouts ok, by setting registry values then using the OpenNETCF >>>>>>>>> CreateEvent and SetEvent for "SDKBackLightChangeEvent" to make it >>>>>>>>> take effect. Now I need to control the power-off timeouts too. I >>>>>>>>> have 2 questions: >>>>>>>>> >>>>>>>>> 1. I notice on my AudioVox PocketPC the SystemIdleTimerReset >>>>>>>>> doesn't work. It seems to be the case that this only works if >>>>>>>>> "GWES is enabled", which I think means you ONLY have the standard >>>>>>>>> registry entries set in >>>>>>>>> HKLM/System/CurrentControlSet/Control/Power. If you ALSO have the >>>>>>>>> ../Control/Power/Timeouts keys set, as my device does, those take >>>>>>>>> precedence and cause the reset API call to do nothing. And making >>>>>>>>> changes manually in Settings/Power control panel only affects the >>>>>>>>> Control/Power/Timeouts keys, not the Control/Power keys. Is this >>>>>>>>> common on many PocketPC devices? >>>>>>>>> >>>>>>>>> Control/Power: >>>>>>>>> ExtPowerOff >>>>>>>>> BattPowerOff >>>>>>>>> WakeupPowerOff >>>>>>>>> >>>>>>>>> vs. >>>>>>>>> >>>>>>>>> Control/Power/Timeouts: >>>>>>>>> BattSuspendTimeout
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |