Codewright Editor Issues

On Tue, 21 Jan 2020 23:03:20 +0100, Hans-Bernhard Bröker
<HBBroeker@t-online.de> wrote:

>Am 21.01.2020 um 21:15 schrieb Rick C:
>
>> I recall from my early Windows programming days that the association
>> is done by invoking the Codewright app (like a command line) with
>> parameters telling it to open the file.  There is/was a difference
>> between basic "opening" the app/file and editing the file.  The
>> editing command had to have particular details to open the file.
>
>[Note: This all happens in the registry, where "keys" in a hierarchy of 
>locations hold values, one of those being "(Standard)" value: ]
>
>You don't really register a filename extension directly to an app (at 
>least no any more).  You register a file type to an extension:
>
>  location:	\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.c
>  value:		"cfile"
>
>then you register "shell" commands to that file type:
>
>  location:	\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\cfile\shell\open\command
>  value:		C:\WATCOM\binnt\viw.exe %1
>
>That's the command line to handle "open"ing of a file of this type. %1 
>is replaced by the file to be opened.
>
>For the vast majority of Windows users and the programs they use, the 
>only commands that ever get handlers registered and used are "open" and 
>"print", which have existed since all the way back in Windows 3.1.
>
>I've encountered only one tool that actually uses the "edit" command 
>instead: MKS Source Integrity, nowadays owned by PTC --- and what a 
>nuisance it was to hunt down that bit of information!


In this vein, Nirsoft has a free tool for editing file/program and
file/icon associations in the registry.  

https://www.nirsoft.net/utils/file_types_manager.html

The download links are far down the page: easiest to just search for
the word "download".

George

On Thursday, January 23, 2020 at 12:36:11 AM UTC-5, George Neuner wrote:
> On Tue, 21 Jan 2020 14:55:56 -0800 (PST), Rick C
> <gnuarm.deletethisbit@gmail.com> wrote:
> 
> >On Tuesday, January 21, 2020 at 1:07:29 PM UTC-5, George Neuner wrote:
> >> On Mon, 20 Jan 2020 18:34:14 -0800 (PST), Rick C
> >> <gnuarm.deletethisbit@gmail.com> wrote:
> >> 
> >> >It doesn't look like admin privilege is enabled.  Properties,
> >> >Shortcut, Advanced, Run as Admin is not checked.  That toolbar icon
> >> >is how I run the program. 
> >> 
> >> Sorry. If it's not admin privileges then I'm out of ideas.
> >
> >
> >That reminded me of the issue of getting a UAC prompt asking if the
> >app should have permission to modify the computer.  I don't get that
> >if I run it simply, but if I run in compatibility mode or as admin I
> >get the UAC dialog.  I've never figured out a way to get rid of that. 
> >Not a big deal.  Once opened I tend to keep  CW up continuously. 
> 
> Hmm.
> 
> I don't know why you'd get that from a compatibility mode start but
> not from a "normal" start.  CW hooks into Explorer (to monitor files
> for changes) and it writes configuration in the registry unless you
> changed that setting.  So if you have UAC notifications turned on, it
> ought to warn UNLESS you start CW in admin mode.
> 
> Did you perhaps upgrade a Win7 machine?  Can't say I've seen this
> problem particularly, but I've seen a number of odd things with Win7
> upgrades that just don't happen if Win10 is installed fresh.
> 
> George

I don't know what this laptop had installed originally, but I'm pretty sure they wiped it clean when installing Win10.  In fact, Win10 Pro, whatever that is.  This model never supported Win10, so it is lacking some drivers, like for the keyboard back lights.  

-- 

  Rick C.

  -+- Get 1,000 miles of free Supercharging
  -+- Tesla referral code - https://ts.la/richard11209

On Thursday, January 23, 2020 at 12:43:05 AM UTC-5, George Neuner wrote:
> On Tue, 21 Jan 2020 23:03:20 +0100, Hans-Bernhard Bröker
> <HBBroeker@t-online.de> wrote:
> 
> >Am 21.01.2020 um 21:15 schrieb Rick C:
> >
> >> I recall from my early Windows programming days that the association
> >> is done by invoking the Codewright app (like a command line) with
> >> parameters telling it to open the file.  There is/was a difference
> >> between basic "opening" the app/file and editing the file.  The
> >> editing command had to have particular details to open the file.
> >
> >[Note: This all happens in the registry, where "keys" in a hierarchy of 
> >locations hold values, one of those being "(Standard)" value: ]
> >
> >You don't really register a filename extension directly to an app (at 
> >least no any more).  You register a file type to an extension:
> >
> >  location:	\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.c
> >  value:		"cfile"
> >
> >then you register "shell" commands to that file type:
> >
> >  location:	\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\cfile\shell\open\command
> >  value:		C:\WATCOM\binnt\viw.exe %1
> >
> >That's the command line to handle "open"ing of a file of this type. %1 
> >is replaced by the file to be opened.
> >
> >For the vast majority of Windows users and the programs they use, the 
> >only commands that ever get handlers registered and used are "open" and 
> >"print", which have existed since all the way back in Windows 3.1.
> >
> >I've encountered only one tool that actually uses the "edit" command 
> >instead: MKS Source Integrity, nowadays owned by PTC --- and what a 
> >nuisance it was to hunt down that bit of information!
> 
> 
> In this vein, Nirsoft has a free tool for editing file/program and
> file/icon associations in the registry.  
> 
> https://www.nirsoft.net/utils/file_types_manager.html
> 
> The download links are far down the page: easiest to just search for
> the word "download".
> 
> George

Seems to work well, thanks. 

-- 

  Rick C.

  -++ Get 1,000 miles of free Supercharging
  -++ Tesla referral code - https://ts.la/richard11209