Menu ▾ ▴

#239 broadcast registry env changes

closed-fixed
Jeffrey Hobbs
32. registry Package (5)
5
2002-10-19
2002-10-18
Jeffrey Hobbs
No

It was noted that just setting the environment vars in the
registry won't propagate them to the current system (a
relogon is required). You must broadcase a
WM_SETTINGCHANGE message, as noted in this
howto and url:

http://support.microsoft.com/default.aspx?scid=KB;EN-
US;q104011

http://www.toflidium.com/citydesk/articles/docs/fog00000
00016.html

Attached is the 'registry broadcast' command
implementation to do this, with docs and tests.

Discussion

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2002-10-18

    Logged In: YES
    user_id=72656

    updated patch to remove unnecessary Tcl_WinUtfToTchar
    conversion.

     

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2002-10-18
     
    regbroadcast.patch.3

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2002-10-18

    Logged In: YES
    user_id=72656

    one more update with more/better tests. tested on Win2K
    and Win98.

     

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2002-10-19
    • status: open --> closed-fixed
     

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2002-10-19

    Logged In: YES
    user_id=72656

    Added for 8.4.1, up'ed reg to v1.1.

     

  • Donal K. Fellows

    Donal K. Fellows - 2002-10-21

    Logged In: YES
    user_id=79902

    Should such a change (new script-level API) go into a patch
    release? Should such a change to something distributed as
    part of the core go in without a TIP? After all, the
    registry package is listed as part of TIP#16 (unlike the
    thread extension.)

     

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2002-10-21

    Logged In: YES
    user_id=72656

    The sub-packages have a history of being rev'ed between
    releases. This goes into the debate of the value of tieing the
    core to packages, which I won't do here.