Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #29112 > unrolled thread

Codewright Editor Issues

Back to article view | Back to comp.arch.embedded

Contents

  Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-20 13:09 -0800
    Re: Codewright Editor Issues Brett <ggtgp@yahoo.com> - 2020-01-20 22:16 +0000
      Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-20 14:57 -0800
        Re: Codewright Editor Issues Chris <chris.hoffmann@gmail.com> - 2020-01-20 16:30 -0800
        Re: Codewright Editor Issues George Neuner <gneuner2@comcast.net> - 2020-01-20 20:36 -0500
          Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-20 18:34 -0800
            Re: Codewright Editor Issues George Neuner <gneuner2@comcast.net> - 2020-01-21 13:07 -0500
              Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-21 14:55 -0800
                Re: Codewright Editor Issues George Neuner <gneuner2@comcast.net> - 2020-01-23 00:36 -0500
                  Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-22 21:46 -0800
        Re: Codewright Editor Issues Herbert Kleebauer <klee@unibwm.de> - 2020-01-21 10:43 +0100
          Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-21 12:15 -0800
            Re: Codewright Editor Issues Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2020-01-21 23:03 +0100
              Re: Codewright Editor Issues George Neuner <gneuner2@comcast.net> - 2020-01-23 00:43 -0500
                Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-22 21:56 -0800
    Re: Codewright Editor Issues David Brown <david.brown@hesbynett.no> - 2020-01-21 08:48 +0100
      Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-21 00:08 -0800
        Re: Codewright Editor Issues David Brown <david.brown@hesbynett.no> - 2020-01-21 10:35 +0100
    Re: Codewright Editor Issues Anssi Saari <as@sci.fi> - 2020-01-21 11:44 +0200
      Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-21 14:39 -0800
    Re: Codewright Editor Issues Michael Kellett <mk@mkesc.co.uk> - 2020-01-21 14:53 +0000
      Re: Codewright Editor Issues Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-21 14:48 -0800
    Re: Codewright Editor Issues John Speth <johnspeth@yahoo.com> - 2020-01-22 09:11 -0800

Page 1 of 2  [1] 2  Next page →

#29112 — Codewright Editor Issues

Maybe I'm stuck in my ways like a dinosaur, but I've always liked my Codewright editor.  My latest PC would not take my previous installation of it though and I had to start fresh.  But that means a lot of stuff that worked before doesn't work now.  This is ver 7.5, that latest.  

I don't know exactly how Windows makes the connection when you click on a file type to open it in the editor.  Back in the day there were specific options to enter on the command line which was shown in a dialog for setting the action on a file extension.  That dialog vanished a few generations of Windows ago.  I have Codewright linked to the file extension, but when I double click nothing seems to happen.  If I drag the file to the Codewright window it shows the arrow with the plus sign which seems to indicate it will open, but again nothing happens.  The only way to open a file seems to be through the Open File menu option. 

Anyone know how to set this so Codewright will work with Windows Explorer and open files like other apps? 

Once I get this working I need to work no language settings... one step at a time. 

-- 

  Rick C.

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

[toc] | [next] | [standalone]

#29113

Rick C <gnuarm.deletethisbit@gmail.com> wrote:
> Maybe I'm stuck in my ways like a dinosaur, but I've always liked my
> Codewright editor.  My latest PC would not take my previous installation
> of it though and I had to start fresh.  But that means a lot of stuff
> that worked before doesn't work now.  This is ver 7.5, that latest.  
> 
> I don't know exactly how Windows makes the connection when you click on a
> file type to open it in the editor.  Back in the day there were specific
> options to enter on the command line which was shown in a dialog for
> setting the action on a file extension.  That dialog vanished a few
> generations of Windows ago.  I have Codewright linked to the file
> extension, but when I double click nothing seems to happen.  If I drag
> the file to the Codewright window it shows the arrow with the plus sign
> which seems to indicate it will open, but again nothing happens.  The
> only way to open a file seems to be through the Open File menu option. 
> 
> Anyone know how to set this so Codewright will work with Windows Explorer
> and open files like other apps? 

Right click on file and select Open With, set checkbox to always use with
the app you select.

> Once I get this working I need to work no language settings... one step at a time. 
> 

[toc] | [prev] | [next] | [standalone]

#29114

On Monday, January 20, 2020 at 5:16:08 PM UTC-5, Brett wrote:
> Rick C <gnuarm.deletethisbit@gmail.com> wrote:
> > Maybe I'm stuck in my ways like a dinosaur, but I've always liked my
> > Codewright editor.  My latest PC would not take my previous installation
> > of it though and I had to start fresh.  But that means a lot of stuff
> > that worked before doesn't work now.  This is ver 7.5, that latest.  
> > 
> > I don't know exactly how Windows makes the connection when you click on a
> > file type to open it in the editor.  Back in the day there were specific
> > options to enter on the command line which was shown in a dialog for
> > setting the action on a file extension.  That dialog vanished a few
> > generations of Windows ago.  I have Codewright linked to the file
> > extension, but when I double click nothing seems to happen.  If I drag
> > the file to the Codewright window it shows the arrow with the plus sign
> > which seems to indicate it will open, but again nothing happens.  The
> > only way to open a file seems to be through the Open File menu option. 
> > 
> > Anyone know how to set this so Codewright will work with Windows Explorer
> > and open files like other apps? 
> 
> Right click on file and select Open With, set checkbox to always use with
> the app you select.

Thanks, but that has already been done.  The Codewright icon shows up on the files.  Double click the file and Codewright comes to the foreground (sort of) but the file doesn't open.  Likewise drag and drop shows an indicator this should work, but the file never opens. 

-- 

  Rick C.

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

[toc] | [prev] | [next] | [standalone]

#29115

On Tuesday, 21 January 2020 09:57:29 UTC+11, Rick C  wrote:
> On Monday, January 20, 2020 at 5:16:08 PM UTC-5, Brett wrote:
> > Rick C <gnuarm.deletethisbit@gmail.com> wrote:
> > > Maybe I'm stuck in my ways like a dinosaur, but I've always liked my
> > > Codewright editor.  My latest PC would not take my previous installation
> > > of it though and I had to start fresh.  But that means a lot of stuff
> > > that worked before doesn't work now.  This is ver 7.5, that latest.  
> > > 
> > > I don't know exactly how Windows makes the connection when you click on a
> > > file type to open it in the editor.  Back in the day there were specific
> > > options to enter on the command line which was shown in a dialog for
> > > setting the action on a file extension.  That dialog vanished a few
> > > generations of Windows ago.  I have Codewright linked to the file
> > > extension, but when I double click nothing seems to happen.  If I drag
> > > the file to the Codewright window it shows the arrow with the plus sign
> > > which seems to indicate it will open, but again nothing happens.  The
> > > only way to open a file seems to be through the Open File menu option. 
> > > 
> > > Anyone know how to set this so Codewright will work with Windows Explorer
> > > and open files like other apps? 
> > 
> > Right click on file and select Open With, set checkbox to always use with
> > the app you select.
> 
> Thanks, but that has already been done.  The Codewright icon shows up on the files.  Double click the file and Codewright comes to the foreground (sort of) but the file doesn't open.  Likewise drag and drop shows an indicator this should work, but the file never opens. 
> 
> -- 
> 
>   Rick C.
> 
>   + Get 1,000 miles of free Supercharging
>   + Tesla referral code - https://ts.la/richard11209

File associations are contained in the registry.

You don't say which windows you are using but there are many options still available even up to win10:

'assoc' command
Control Panel->Default Programs->Associate a file type(...)
Settings->Apps->Default Apps->Choose default applications by file type

The last is Win 10 specific but the others also work in Win 10.

HTH
--
Cheers,
Chris.

[toc] | [prev] | [next] | [standalone]

#29116

On Mon, 20 Jan 2020 14:57:25 -0800 (PST), Rick C
<gnuarm.deletethisbit@gmail.com> wrote:

>On Monday, January 20, 2020 at 5:16:08 PM UTC-5, Brett wrote:
>> Rick C <gnuarm.deletethisbit@gmail.com> wrote:
>>
>> > Anyone know how to set this so Codewright will work with Windows Explorer
>> > and open files like other apps? 
>> 
>> Right click on file and select Open With, set checkbox to always use with
>> the app you select.
>
>Thanks, but that has already been done.  The Codewright icon shows up
>on the files.  Double click the file and Codewright comes to the 
>foreground (sort of) but the file doesn't open.  Likewise drag and 
>drop shows an indicator this should work, but the file never opens. 

Did you perhaps set Codewright to run with Administrator privileges? 

Windows 8 and 10 won't allow drag and drop into an application that
has Admin privilege unless you disable user account controls.  Note
that simply turning off UAC notifications in Settings is NOT
sufficient - you need to edit the registry to disable UAC entirely.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
EnableLUA:DWORD = 0

But realize that if you do this, all users the machine (not just your
account) will lose UAC warnings about programs that are trying to
change system settings.


George

[toc] | [prev] | [next] | [standalone]

#29117

On Monday, January 20, 2020 at 8:37:01 PM UTC-5, George Neuner wrote:
> On Mon, 20 Jan 2020 14:57:25 -0800 (PST), Rick C
> <gnuarm.deletethisbit@gmail.com> wrote:
> 
> >On Monday, January 20, 2020 at 5:16:08 PM UTC-5, Brett wrote:
> >> Rick C <gnuarm.deletethisbit@gmail.com> wrote:
> >>
> >> > Anyone know how to set this so Codewright will work with Windows Explorer
> >> > and open files like other apps? 
> >> 
> >> Right click on file and select Open With, set checkbox to always use with
> >> the app you select.
> >
> >Thanks, but that has already been done.  The Codewright icon shows up
> >on the files.  Double click the file and Codewright comes to the 
> >foreground (sort of) but the file doesn't open.  Likewise drag and 
> >drop shows an indicator this should work, but the file never opens. 
> 
> Did you perhaps set Codewright to run with Administrator privileges? 

Thanks for the info.  I hadn't even thought about looking at that. 

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. 


> Windows 8 and 10 won't allow drag and drop into an application that
> has Admin privilege unless you disable user account controls.  Note
> that simply turning off UAC notifications in Settings is NOT
> sufficient - you need to edit the registry to disable UAC entirely.
> 
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
> EnableLUA:DWORD = 0
> 
> But realize that if you do this, all users the machine (not just your
> account) will lose UAC warnings about programs that are trying to
> change system settings.

I turned off UAC under Win7 and it healed many issues.  Win 8 and 10 seem to play much better with various programs.  I'm running Win10.  

-- 

  Rick C.

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

[toc] | [prev] | [next] | [standalone]

#29124

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.

George

[toc] | [prev] | [next] | [standalone]

#29129

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.
> 
> George

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. 

-- 

  Rick C.

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

[toc] | [prev] | [next] | [standalone]

#29131

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

[toc] | [prev] | [next] | [standalone]

#29133

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

[toc] | [prev] | [next] | [standalone]

#29121

On 20.01.2020 23:57, Rick C wrote:

> Double click the file and Codewright comes to the foreground (sort of) but the file doesn't open.

Try it with a file like

c:\test.txt

Maybe there is a problem with long file names or spaces in path/file name.

[toc] | [prev] | [next] | [standalone]

#29125

On Tuesday, January 21, 2020 at 4:43:34 AM UTC-5, Herbert Kleebauer wrote:
> On 20.01.2020 23:57, Rick C wrote:
> 
> > Double click the file and Codewright comes to the foreground (sort of) but the file doesn't open.
> 
> Try it with a file like
> 
> c:\test.txt
> 
> Maybe there is a problem with long file names or spaces in path/file name.

Thanks for the suggestion.  I try to keep spaced out of both directory names and filenames.  But I tried your suggestion and same result.  Codewright pops to the foreground, but the file is not opened.  It would seem the association is made, but Codewright is not getting what it needs to open the file.  

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.  It's all very fuzzy as I don't think I've had to do this since W2K.  

Thanks for the suggestion though. 

-- 

  Rick C.

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

[toc] | [prev] | [next] | [standalone]

#29126

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!

[toc] | [prev] | [next] | [standalone]

#29132

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

[toc] | [prev] | [next] | [standalone]

#29134

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

[toc] | [prev] | [next] | [standalone]

#29118

On 20/01/2020 22:09, Rick C wrote:
> Maybe I'm stuck in my ways like a dinosaur, but I've always liked my
> Codewright editor.  My latest PC would not take my previous
> installation of it though and I had to start fresh.  But that means a
> lot of stuff that worked before doesn't work now.  This is ver 7.5,
> that latest.
> 
> I don't know exactly how Windows makes the connection when you click
> on a file type to open it in the editor.  Back in the day there were
> specific options to enter on the command line which was shown in a
> dialog for setting the action on a file extension.  That dialog
> vanished a few generations of Windows ago.  I have Codewright linked
> to the file extension, but when I double click nothing seems to
> happen.  If I drag the file to the Codewright window it shows the
> arrow with the plus sign which seems to indicate it will open, but
> again nothing happens.  The only way to open a file seems to be
> through the Open File menu option.
> 
> Anyone know how to set this so Codewright will work with Windows
> Explorer and open files like other apps?
> 
> Once I get this working I need to work no language settings... one
> step at a time.
> 

I don't to sound rude, and this group is not exactly overwhelmed by
activity - but surely you'd get an answer from 30 seconds of googling?

[toc] | [prev] | [next] | [standalone]

#29119

On Tuesday, January 21, 2020 at 2:48:43 AM UTC-5, David Brown wrote:
> On 20/01/2020 22:09, Rick C wrote:
> > Maybe I'm stuck in my ways like a dinosaur, but I've always liked my
> > Codewright editor.  My latest PC would not take my previous
> > installation of it though and I had to start fresh.  But that means a
> > lot of stuff that worked before doesn't work now.  This is ver 7.5,
> > that latest.
> > 
> > I don't know exactly how Windows makes the connection when you click
> > on a file type to open it in the editor.  Back in the day there were
> > specific options to enter on the command line which was shown in a
> > dialog for setting the action on a file extension.  That dialog
> > vanished a few generations of Windows ago.  I have Codewright linked
> > to the file extension, but when I double click nothing seems to
> > happen.  If I drag the file to the Codewright window it shows the
> > arrow with the plus sign which seems to indicate it will open, but
> > again nothing happens.  The only way to open a file seems to be
> > through the Open File menu option.
> > 
> > Anyone know how to set this so Codewright will work with Windows
> > Explorer and open files like other apps?
> > 
> > Once I get this working I need to work no language settings... one
> > step at a time.
> > 
> 
> I don't to sound rude, and this group is not exactly overwhelmed by
> activity - but surely you'd get an answer from 30 seconds of googling?

If you didn't want to sound rude, why did you?  Actually it isn't so much rude as just not well informed.  The info I'm looking for isn't the cut and dried matter that Bret and Chris offered.  

If you think you can find the solution using Google, please show me.  I tried and found 80 million hits about anything remotely related, none of the first few pages of hits were even close.  

I remember a teacher saying you can look up a word in the dictionary to get the correct spelling.  I asked how do you use the dictionary if you don't know how to spell the word.  Google can have the same problem where you need to know how to get focused answers to find what you need and this is one of those times when I can't figure out how to get Google to focus. 

If this is all you have to offer, why did you even reply??? 

-- 

  Rick C.

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

[toc] | [prev] | [next] | [standalone]

#29120

On 21/01/2020 09:08, Rick C wrote:
> On Tuesday, January 21, 2020 at 2:48:43 AM UTC-5, David Brown wrote:
>> On 20/01/2020 22:09, Rick C wrote:
>>> Maybe I'm stuck in my ways like a dinosaur, but I've always liked
>>> my Codewright editor.  My latest PC would not take my previous 
>>> installation of it though and I had to start fresh.  But that
>>> means a lot of stuff that worked before doesn't work now.  This
>>> is ver 7.5, that latest.
>>> 
>>> I don't know exactly how Windows makes the connection when you
>>> click on a file type to open it in the editor.  Back in the day
>>> there were specific options to enter on the command line which
>>> was shown in a dialog for setting the action on a file extension.
>>> That dialog vanished a few generations of Windows ago.  I have
>>> Codewright linked to the file extension, but when I double click
>>> nothing seems to happen.  If I drag the file to the Codewright
>>> window it shows the arrow with the plus sign which seems to
>>> indicate it will open, but again nothing happens.  The only way
>>> to open a file seems to be through the Open File menu option.
>>> 
>>> Anyone know how to set this so Codewright will work with Windows 
>>> Explorer and open files like other apps?
>>> 
>>> Once I get this working I need to work no language settings...
>>> one step at a time.
>>> 
>> 
>> I don't to sound rude, and this group is not exactly overwhelmed
>> by activity - but surely you'd get an answer from 30 seconds of
>> googling?
> 
> If you didn't want to sound rude, why did you?  Actually it isn't so
> much rude as just not well informed.  The info I'm looking for isn't
> the cut and dried matter that Bret and Chris offered.

I don't believe I did sound rude - but I feared you might interpret it
that way.  Rude would have been posting a "let me google that for you"
link with the search "how to change file association in windows 10".

Yes, I know it is not entirely a simple matter.  Yes, I know MS in their
unending quest to irritate people change these things from version to
version, taking perfectly good working methods and screwing with them
until no one knows what's going on.

That is /precisely/ why googling is a better idea than asking in a
newsgroup (especially one that specialises in a very different niche -
though it does have the advantage of having smart and helpful denizens).
 A web search will get you to tutorials, web pages, etc., a let you get
right to the requirements at hand - no need for several posts back and
forth to figure out what version of Windows you are using or any other
details.  It would get you the answers you want faster.  It would get
you more details if you want them - or just a simple picture to follow
if a quick answer is all you want.  Surely that is a good thing?

> 
> If you think you can find the solution using Google, please show me.
> I tried and found 80 million hits about anything remotely related,
> none of the first few pages of hits were even close.

You have been around Usenet for longer than most people have used
computers.  Don't tell me you have never read a "how to ask smart
questions" FAQ.  You know that if you have already tried things -
including web searches - you write a summary with your question.  For
example, you should have started with saying that you got CodeWright to
start from clicking the file, but it wasn't opening the file itself.
And you could have given information about what /does/ work - can you
open files properly from within the application?

> 
> I remember a teacher saying you can look up a word in the dictionary
> to get the correct spelling.  I asked how do you use the dictionary
> if you don't know how to spell the word.  Google can have the same
> problem where you need to know how to get focused answers to find
> what you need and this is one of those times when I can't figure out
> how to get Google to focus.
> 

Well, what did you try?

> If this is all you have to offer, why did you even reply???
> 

I had this vague idea that I could help you get better help, but it
seems I was mistaken.  From a number of threads with you, I get the
impression that you sometimes prefer to rant than to solve problems -
especially if the solution involves accepting the reality that the world
has moved on in the last 20 years.  (I am not asking you to /like/ the
fact that things that were perfectly simple decades ago are now overly
complicated, when the old solutions would still do the job - I am asking
you to accept it.)

If you had been looking for an answer rather than a rant or a fight,
you'd have replied to my post with "I already googled for ..., but the
hits did not help - have you any suggestions?".


So, please take a moment and figure out what you want to do.

Do you want to vent your frustrations about modern Windows not letting
you use your old program as you like?  Or that MS won't let you use old
Windows that you were quite happy with?  If so, I think you'll find very
strong agreement from most people (including me).  Start a rant thread,
and people can share their war stories and feel a little better.

Do you want to figure out how to use your old editor on your new system?
 Then google a lot, and tell people what you have tried, what works, and
what doesn't.  And be prepared to accept that maybe it won't ever work -
that maybe you'll have to open files from within the editor instead of
drag-and-drop.  Be prepared that it might take a lot of work, trial and
error, "compatibility modes", reading manuals, etc.

Do you want to edit files to write code and do your work?  Maybe it's
time to spend an hour getting familiar with NotePad++ (or whatever) and
dropping CodeWright.  I'm sure you'll find some pros along with all the
cons.

[toc] | [prev] | [next] | [standalone]

#29122

Rick C <gnuarm.deletethisbit@gmail.com> writes:

> Maybe I'm stuck in my ways like a dinosaur, but I've always liked my
> Codewright editor.  My latest PC would not take my previous
> installation of it though and I had to start fresh.  But that means a
> lot of stuff that worked before doesn't work now.  This is ver 7.5,
> that latest.

Does that mean CodeWright has an installer and you ran it successfully?

> I don't know exactly how Windows makes the connection when you click
> on a file type to open it in the editor.  Back in the day there were
> specific options to enter on the command line which was shown in a
> dialog for setting the action on a file extension.  That dialog
> vanished a few generations of Windows ago.

I don't remember but OK. It seems to me there are maybe two or three
systems for the association stuff in Windows 10. For example, I use
Emacs and it has some associations that work but the command line tool
assoc isn't aware of some of those at all and for some files things work
differently from what assoc and ftype report. But maybe using these
older tools (assoc and ftype) could work for CodeWright?

Then there's the tool called FileTypesMan which I've used with some
success. It seems to give a more complete view of the situation.

[toc] | [prev] | [next] | [standalone]

#29127

On Tuesday, January 21, 2020 at 4:44:58 AM UTC-5, Anssi Saari wrote:
> Rick C <gnuarm.deletethisbit@gmail.com> writes:
> 
> > Maybe I'm stuck in my ways like a dinosaur, but I've always liked my
> > Codewright editor.  My latest PC would not take my previous
> > installation of it though and I had to start fresh.  But that means a
> > lot of stuff that worked before doesn't work now.  This is ver 7.5,
> > that latest.
> 
> Does that mean CodeWright has an installer and you ran it successfully?

Yes.


> > I don't know exactly how Windows makes the connection when you click
> > on a file type to open it in the editor.  Back in the day there were
> > specific options to enter on the command line which was shown in a
> > dialog for setting the action on a file extension.  That dialog
> > vanished a few generations of Windows ago.
> 
> I don't remember but OK. It seems to me there are maybe two or three
> systems for the association stuff in Windows 10. For example, I use
> Emacs and it has some associations that work but the command line tool
> assoc isn't aware of some of those at all and for some files things work
> differently from what assoc and ftype report. But maybe using these
> older tools (assoc and ftype) could work for CodeWright?
> 
> Then there's the tool called FileTypesMan which I've used with some
> success. It seems to give a more complete view of the situation.

Thanks.  Digging around with assoc and ftype helped me figure out what was going on.  So I think I found the issue.  

While the association was pointing to the Codewright installed under C:\Program Files (x86) that was not the location of the Codewright I was running and pinned to my taskbar.  On changing that the associations seem to work now and not only bring Codewright to the foreground, opens the file.  

Now I need to set up the various visual issues.  Seems the font selection doesn't actually result in that font being used, but something else is being substituted as if there are only a small number of real fonts and it selects something "close".  Many of them result in very wide characters... or more like wide space between characters.  Is it possible there is something preventing Codewright from accessing the many fonts it shows in the fonts list and translates everything to a small number of fonts (possibly 1)? 

http://arius.com/pictures/LucidaConsole_12pt.png

http://arius.com/pictures/LucidaConsole_14pt.png

Here's another thing I'll just mention to anyone wishing to continue the discussion.  Out of the box it has some goofiness with not displaying files in the File Open dialog box.  Running in compatibility mode fixes that, but now every time I run it I have to click the dialog box giving permissions for it to access files.  Why not before but only after setting compatibility mode? 

-- 

  Rick C.

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

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.arch.embedded

csiph-web