Hi
I've been evaluating GCB by comparing it with my current Basic Compiler (Oshonsoft). I decided the best way to do this was to start with one of my existing working programs, then find the different syntax/commands as I worked through. Before I get to my 2 niggles, I must say I really like the way the Syn Editor fonts and background colours etc can be configured. I don't like staring at small fonts on a glaring white background.
A very simple 12f683 program was converted without any major problems but I did notice 2 things.
Whenever I open GCB I get the same 4(?) files opened, a mix of text files and a sample program. Altough this was OK the first time, but I don't really want to see them every time. I tried a few changes to settings but could get the desired result. I then deleted the text files to see if it would just ignore the missing files, but now I get an error when starting up GCB so clearly this is "hard wired" into the GCB code. Or I missed something.
So Question 1, is there a way of making the editor either open with nothing or the last edited program?
After changing obvious differences to the code like #chip etc I ran the compiler to make hex so
I could see where the commands/syntax varied by way of syntax error or messages.
This was where niggle No 2 was found. The output window correctly identified any issues but I was not able to make any changes while the window was open. Since my memory isn't up to remembering several error messages, this meant I had to make a correction then run the compiler again for the next error.
OK what I'm doing will obviously create quite a few errors, but even when I know what I'm doing, I often make several mistakes when creating code.
So Question 2. Is it possible to make the editor output window stay open until errors have been fixed?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A. The IDE leverages the SynWrite Editor. Not much we can do about the file open/close.
B. Nothing is hard wired. I am not sure what is happening - can you post some screen shots?
C. I am unaware of any method to open to an empty editort. Others may know but this is something I have never thought about.
D. The output window does stay open. So, I am puzzled what is happening. Screen shots may help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK thanks, I'll double check the output window usage.
I'll have to reinstall because deleting the text files screwed things up a bit (technical terminology).
When I say "hard wired" I meant "a" program seems to be opening the 4 files rather than a setting, which is what I think you are saying.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So Question 1, is there a way of making the editor either open with nothing or the last edited program?
Yes ... Options> Customize> Sessions/Projects. This can be setup to open only an empty untitled file. But cannot be setup to open nothing.
So Question 2. Is it possible to make the editor output window stay open until errors have been fixed?
Probably not. When the G+Tools window is open, it takes exclusive control. Nothing can be changed in the Synwrite editor while this window is open. However you can select the text in the output window with a mouse and then use CTRL+C to copy the text to the clipboard and then to paste to Notepad. Then close the output window to allow editing the Synwrite editor.
Frank would know more about this and if it might be posible to prevent the G+Stools window from taking exclusive control.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for that info. An empty untittled file would be Ok, that's what I meant by blank.
I tried the the output window again and that is exactly what happens, if I move the mouse cursor in to the editor and click the whole desktop freezes for a few seconds.
Personally I find this a serious limitation. All of the programming tools I've used before allow errors to be fixed while leaving the output window on view. I can't see any logocal reason for the output window to have "executive control".
Is it possible to request a change?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After a compilation, when using the IDE you will get a listing of all the errors. This is called the 'output' window. This window contains all the errors - you can select and click the error with the IDE moving your cursor to the appropiate error.
As shown here at the bottom of the image.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Really weird, I just reinstalled, when I open GCB I get the a new document, not the 4 files mentioned before. I opened a small program and inserted a line with the wrong syntax.
When I compile (make hex) I get the output window + a little "busy" circle on th emouse cursor + an extra message. n.b. this time I did not install Picket 2 etc because I already have them installed. When I compile (make hex) I get the output window + a little "busy" circle as the mouse cursor (this doesn't show on the attached PrtScn) + an extra message (not seen before). The only way I can clear the mouse cursor circle now is by closing the new message.
n.b. this time I did not install Picket 2 etc because I already have them installed. I've attached a PrtScn image.
I've just installed GCB on a different computer. With the exception of the extra message, I get exactly the same result. This time I installed Picket2+3 and AVRDude(es) but none of the other programmer types.
Ok I'm not sure what happened but:it's all fixed now
Q1 There is an IDE.bas in the G+Stools. looking at that, the 4 files mentioned before should only be shown on 1st run which is what happened on the 2nd PC. Also I now get the last saved program on re-opening GCB. I've done nothing to the settings.
Q2 The inital output window is a bit confusing, it is for info only. When it was closed I noticed an "output" tab bottom left. When I opened this it gave me the errors and has a hyperlink to the error in the editor. This tab has now undocked itself and now appears everytime I close the initial window. Not sure how it happened, I don't think I undocked it, but maybe I did.
I think I'll do a seek and destroy on the 1st PC then reinstall. I'm using a week old download of GCB97 installer.
Thanks for you help
Just reinstalled, did not get the 4 files mentioned at inital startup (I had deleted all GCB folders etc). I now get a blank i.e. new doc at restart. I must have undocked the Console because it wouldn't work until I did.. Now as soon as the inital Output Window has printed, it closes and the Console/Output window displays the result. So what was missing before was a destination for the output window i.e. Console/Output
So all good but all the variations are a bit confusing.
Last edit: David Thompson 2017-04-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am a recent convert to GCB and probably stating something you already knew. But when I open GCB it brings up the last file I worked on. To start a new blank GCB file, just click on the FILE TAB, then NEW, then NEW FILE, and you have a completely blank page to start a new program.
Sorry if I not understanding the ops question, but thats what I do.
Last edit: Paul Haug 2017-04-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's what I would have expected. I was getting the "first startup" with 3 text files and a .bas example everytime I started GCB, even if I closed them all and edited something else. Not sure what caused it, but all works as expected now after a software re install.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I've been evaluating GCB by comparing it with my current Basic Compiler (Oshonsoft). I decided the best way to do this was to start with one of my existing working programs, then find the different syntax/commands as I worked through. Before I get to my 2 niggles, I must say I really like the way the Syn Editor fonts and background colours etc can be configured. I don't like staring at small fonts on a glaring white background.
A very simple 12f683 program was converted without any major problems but I did notice 2 things.
Whenever I open GCB I get the same 4(?) files opened, a mix of text files and a sample program. Altough this was OK the first time, but I don't really want to see them every time. I tried a few changes to settings but could get the desired result. I then deleted the text files to see if it would just ignore the missing files, but now I get an error when starting up GCB so clearly this is "hard wired" into the GCB code. Or I missed something.
So Question 1, is there a way of making the editor either open with nothing or the last edited program?
After changing obvious differences to the code like #chip etc I ran the compiler to make hex so
I could see where the commands/syntax varied by way of syntax error or messages.
This was where niggle No 2 was found. The output window correctly identified any issues but I was not able to make any changes while the window was open. Since my memory isn't up to remembering several error messages, this meant I had to make a correction then run the compiler again for the next error.
OK what I'm doing will obviously create quite a few errors, but even when I know what I'm doing, I often make several mistakes when creating code.
So Question 2. Is it possible to make the editor output window stay open until errors have been fixed?
Thank you for a good post.
A. The IDE leverages the SynWrite Editor. Not much we can do about the file open/close.
B. Nothing is hard wired. I am not sure what is happening - can you post some screen shots?
C. I am unaware of any method to open to an empty editort. Others may know but this is something I have never thought about.
D. The output window does stay open. So, I am puzzled what is happening. Screen shots may help.
OK thanks, I'll double check the output window usage.
I'll have to reinstall because deleting the text files screwed things up a bit (technical terminology).
When I say "hard wired" I meant "a" program seems to be opening the 4 files rather than a setting, which is what I think you are saying.
Yes ... Options> Customize> Sessions/Projects. This can be setup to open only an empty untitled file. But cannot be setup to open nothing.
Probably not. When the G+Tools window is open, it takes exclusive control. Nothing can be changed in the Synwrite editor while this window is open. However you can select the text in the output window with a mouse and then use CTRL+C to copy the text to the clipboard and then to paste to Notepad. Then close the output window to allow editing the Synwrite editor.
Frank would know more about this and if it might be posible to prevent the G+Stools window from taking exclusive control.
Thanks for that info. An empty untittled file would be Ok, that's what I meant by blank.
I tried the the output window again and that is exactly what happens, if I move the mouse cursor in to the editor and click the whole desktop freezes for a few seconds.
Personally I find this a serious limitation. All of the programming tools I've used before allow errors to be fixed while leaving the output window on view. I can't see any logocal reason for the output window to have "executive control".
Is it possible to request a change?
Puzzled here.
After a compilation, when using the IDE you will get a listing of all the errors. This is called the 'output' window. This window contains all the errors - you can select and click the error with the IDE moving your cursor to the appropiate error.
As shown here at the bottom of the image.
Really weird, I just reinstalled, when I open GCB I get the a new document, not the 4 files mentioned before. I opened a small program and inserted a line with the wrong syntax.
When I compile (make hex) I get the output window + a little "busy" circle on th emouse cursor + an extra message. n.b. this time I did not install Picket 2 etc because I already have them installed. When I compile (make hex) I get the output window + a little "busy" circle as the mouse cursor (this doesn't show on the attached PrtScn) + an extra message (not seen before). The only way I can clear the mouse cursor circle now is by closing the new message.
n.b. this time I did not install Picket 2 etc because I already have them installed. I've attached a PrtScn image.
I've just installed GCB on a different computer. With the exception of the extra message, I get exactly the same result. This time I installed Picket2+3 and AVRDude(es) but none of the other programmer types.
Last edit: David Thompson 2017-04-17
Would recommend removing. Delete the installation folder. Then, install everything especially pk2 as this has the latest data files.
From this reinstall we should know where you are.
What OS?
Ok I'm not sure what happened but:it's all fixed now
Q1 There is an IDE.bas in the G+Stools. looking at that, the 4 files mentioned before should only be shown on 1st run which is what happened on the 2nd PC. Also I now get the last saved program on re-opening GCB. I've done nothing to the settings.
Q2 The inital output window is a bit confusing, it is for info only. When it was closed I noticed an "output" tab bottom left. When I opened this it gave me the errors and has a hyperlink to the error in the editor. This tab has now undocked itself and now appears everytime I close the initial window. Not sure how it happened, I don't think I undocked it, but maybe I did.
I think I'll do a seek and destroy on the 1st PC then reinstall. I'm using a week old download of GCB97 installer.
Thanks for you help
Just reinstalled, did not get the 4 files mentioned at inital startup (I had deleted all GCB folders etc). I now get a blank i.e. new doc at restart. I must have undocked the Console because it wouldn't work until I did.. Now as soon as the inital Output Window has printed, it closes and the Console/Output window displays the result. So what was missing before was a destination for the output window i.e. Console/Output
So all good but all the variations are a bit confusing.
Last edit: David Thompson 2017-04-17
I am a recent convert to GCB and probably stating something you already knew. But when I open GCB it brings up the last file I worked on. To start a new blank GCB file, just click on the FILE TAB, then NEW, then NEW FILE, and you have a completely blank page to start a new program.
Sorry if I not understanding the ops question, but thats what I do.
Last edit: Paul Haug 2017-04-17
That's what I would have expected. I was getting the "first startup" with 3 text files and a .bas example everytime I started GCB, even if I closed them all and edited something else. Not sure what caused it, but all works as expected now after a software re install.