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.
Codewright Editor Issues
Started by ●January 20, 2020
Reply by ●January 21, 20202020-01-21
Reply by ●January 21, 20202020-01-21
On 20/01/2020 21: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 was going to attempt installing Codewright on my Windows 10 machine - but alas - it must have been thrown out in the last major clear up (making room for pallet full of HP power supplies). Mostly I use the editors in the Keil IDE (for C) and Aldec HDL (for VHDL). Any other time I use Notepad (the dead simple MS thing) or Notepad++ (the free and open source thing). I was a bit miffed when Codewright went unsupported but it was a very long time ago - it might be time to bite the bullet and move on :-( MK
Reply by ●January 21, 20202020-01-21
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
Reply by ●January 21, 20202020-01-21
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
Reply by ●January 21, 20202020-01-21
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!
Reply by ●January 21, 20202020-01-21
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
Reply by ●January 21, 20202020-01-21
On Tuesday, January 21, 2020 at 9:53:18 AM UTC-5, Michael Kellett wrote:> On 20/01/2020 21: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 was going to attempt installing Codewright on my Windows 10 machine - > but alas - it must have been thrown out in the last major clear up > (making room for pallet full of HP power supplies). > > Mostly I use the editors in the Keil IDE (for C) and Aldec HDL (for > VHDL). Any other time I use Notepad (the dead simple MS thing) or > Notepad++ (the free and open source thing). > > I was a bit miffed when Codewright went unsupported but it was a very > long time ago - it might be time to bite the bullet and move on :-( > > MKI'm really sorry you tossed it out. Anytime you toss out software it would be nice to offer to give it to someone. I gave away my really old Xilinx software for the old 4000 series parts a few years back. Someone was working with them and wanted the software. I don't know if I ever found the key for it though. lol I've looked at using other stuff, but at this point Codewright is in my DNA and it's just painful to give it up. I'm always missing the features. There's also a thing or two I don't care for. The way it doesn't treat end of lines as continuing to the next line for cursor movement. Use the right arrow and it just keeps moving right, no wrapping at the end of the line. There's a few more that the authors think are features, but mostly I think of them when they get in the way. BTW, a friend of mine who thinks old computers are something to be relished like an old wine had to toss his Win95/98 machine and insisted I find someone who "could use it". Rather than argue with him about it I took it and it's sitting in my basement. Anyone want it or should I toss it? It's got some software with it, but I can't tell you exactly what at the moment. Are Win95 machines getting rare yet? -- Rick C. --- Get 1,000 miles of free Supercharging --- Tesla referral code - https://ts.la/richard11209
Reply by ●January 21, 20202020-01-21
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. > > GeorgeThat 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
Reply by ●January 22, 20202020-01-22
If it's any consolation, I use CW 4.0E from 1996 on Win 10 Home 64 bit. It works just fine. I've carried it forward on numerous computers all these years. My method has always been to manually copy the entire CW directory tree verbatim (never use the installer). It's always been "C:\CW32". Doing it that way relieves me of the burden of editing the ini files to resolve the new paths. My help files are broken for good. Former copies running under WinXP and beyond used to screw up key auto-repeat timing frequently. The problem still happens on my Win 10 but its now rare, almost as if CW is getting better as Windows ages! I used to experience CW failing to start on Win7. That never happens on Win10. JJS
Reply by ●January 23, 20202020-01-23
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
