Frank or Alexey, When Frank's compilation window pops up and then disappears after a successful build, it leaves a gray area in the output window only blocking the first few lines. If I click on a line then the text appears and the gray disappears for that line. Can this be fixed or is it a windows thing?
Made a new G@Stool, maybe it helps (replace the one in G@Stools folder): Download
Happy new year to all
Steini
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tried the new G@Stool and same results.
I did discover something strange though.
If I compile a small GCB program such as the sample BlinkLED.gcb the issue occurs.
If I compile a larger program such as morse code.gcb then the issue doesn't happen.
It only appears to show up when the compile time is very short. morse code.gcb takes visibly longer to compile and assemble than BlinkLED so it appears to me to be some kind of timing issue of the window staying open longer than the compile despite being automatically closed by a successful compile.
Isn't there a way to keep the pop up window open and force a manual close?
I know I read it in the notes somewhere but now I cannot find it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did some testing; found that
- It only happens with WinXP, not Vista, not Win7
- it only happens, if "Capture output " is enabled in SynWrites "External tools" config.
As a workaround i put the compilation window on top of the screen, so SynWrites output area schould not be affected.
Use the download link from my post above.
Isn't there a way to keep the pop up window open and force a manual close? I know I read it in the notes somewhere but now I cannot find it.
Add stayopen as last parameter in SynWrite Option - External tools …. / Parameters
See FLASH previous made hexfile for an example.
Steini
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
new version 2013-01-14:
SynWrite updated to 4.6.600
new position for G@Stools messagewindow, to prevent overwriting SynWrites output window (seems to be an issue for WinXP only)
chip resource usage (from GCBs reportfile) displayed in SynWrites output window
minor changes to batchfiles
This was great Frank.
The reporting of the memory size is perfect.
I have modified your GCB@SYN to create my own custom PIC only simplified interface.
With each update I have to go back and modify so I'm going to lock in to a level here soon so I can post it for others to use if they want.
I really like the new position of the message window. I also use the stayopen which works great.
One thing I have noticed though is when I open up a new session, the output window is all the way at the bottom and very thin. I drag it up to make it bigger and then I can see the output results.
When I shut down, I automatically save the session.
I also have it set to restore last session on open.
But each time GCB@SYN opens, the output window shrinks down a few lines. If I close and reopen several times, the output window shrinks down to very thin again.
This forces me to re-adjust the window almost every time I open GCB@SYN.
Shouldn't saving the session save the position of the output window?
Again, I'm using XP. It may be an XP thing. I'm going to try this on Win 7 when I get a chance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One thing I have noticed though is when I open up a new session, the output window is all the way at the bottom and very thin. I drag it up to make it bigger and then I can see the output results. When I shut down, I automatically save the session. I also have it set to restore last session on open. But each time GCB@SYN opens, the output window shrinks down a few lines. If I close and reopen several times, the output window shrinks down to very thin again. This forces me to re-adjust the window almost every time I open GCB@SYN. Shouldn't saving the session save the position of the output window? Again, I'm using XP. It may be an XP thing. I'm going to try this on Win 7 when I get a chance.
That's a SynWrite issue. It happens for me regardless of the Windows Version (but never noticed before).
Maybe you should mention it in the SynWrite forum.
Steini
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems to fix it but now as I resized the output window, the Tree Structure window appears and dissapears as I move the output window.
If I then move the mouse over the Tree Structure X then the Title Tree Structure appears again.
This only happens on certain positions of the output window.
(Posted this on SynWrite Forum also)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Frank,
Next time you build the GCB@SYN, is there anyway to use the GCGB Cow icon in the build so rather than having a square box icon for GCB@SYN we have the Cow icon?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-24
how can i edit "Make ASM" to show asm code after run? to not need to find the file and open after.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Recommendation- use "OfficeXP" theme by default. "Default" theme is SLUGGISH, shows redraw issues on panels resizing. OfficeXp is faster. And less issues yet
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Implemented some suggestions from the forum posters in
new version 2013-01-26:
- SynWrite: Updated to 4.7.670
Toolbar theme changed to OfficeXP due to recommendation of Alexej
- Added the beautiful cow-icon to IDE.exe
- Added "Open ASM" to the "Run" menu
Frank,
One bug showed up for me.
No matter what I put in SynHide, Run menu won't show options 0-3.
It only shows 4- 7 even though SynHide doesn't have options 0-3 hidden.
Are you seeing this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also,
If I make changes to the order and selections in the Run menu, where is that stored so I don't have to redo that every time a new version is released?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No matter what I put in SynHide, Run menu won't show options 0-3. It only shows 4- 7 even though SynHide doesn't have options 0-3 hidden. Are you seeing this?
Some items are shown only, if a GCB sourcefile (*.bas, *.gcb, *.pbs, *h) is active in the editor window, because it makes no sense trying to compile/flash another kind of file. Check out Options - External tools … / Tool properties: / Lexers:
If I make changes to the order and selections in the Run menu, where is that stored so I don't have to redo that every time a new version is released?
I recommend to backup all *.ini files in the SynWrite folder and replace the default ones with these after an update.
I used your editor, and I'm honestly very satisfied, great job.
You point out only that, the. Asm generated is hard to read, because it has no indentation, such as that generated by GCGB.
I hope you can fix it in a future release.
You already have some idea of what to add in the future?
Thanks, MC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You point out only that, the. Asm generated is hard to read, because it has no indentation, such as that generated by GCGB. I hope you can fix it in a future release.
It has indentation, but it's set to 2 chars only in SynWrite. You can easily change that: Options - Customize… - Editor2 -> Set the value in the "Tab stops" field to what you need (i.e. 8).
You already have some idea of what to add in the future?
I rather would play around with some hardware projects :-)
Frank,
Thank you for adding the Cow symbol and all the other improvements I've requested.
I'm working on a series of Great Cow Basic books for the CHIPINO module and having this IDE was the missing piece I needed.
The work you, Hugh, Alexy and others have put in to make such a great open source product for the embedded BASIC programmer is fantastic.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply, I confirm that it is a great interface for GCB.
MC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-03-19
Hello to all.
I see that you can use winpic to load the Hex file in Pic.
E 'can use "MikroProg suite" (for USB) Mikroelettronica to program the pic directly from SynWrite?
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
… worked on GCB@Syn again!
New version 2013-03-19:
- GCBasic compiler updated to "Version 0.9 10/3/2013"
- SynWrite updated to 4.10.900
- Br@y's Terminal updated to 20130116ß
- Added backup function for config files (SynWrite-inis and G@Ctool-batchfiles)
See section "Backup-Function" in readme file.
- Added new GCB commands to lexer
- Small GCB lexer improvements (i.e. labels now in Tree Structure window)
- Added simple asm-lexer (asm source now coloured)
- New helpfile handling (auto-maximize, one instance)
tonkawa53
… use "MikroProg suite" (for USB) Mikroelettronica to program the pic directly from SynWrite?
Should be possible. MikroProgSuite - manual says, that it understands commandline parameters to use it from other software. Edit flashPIC.bat (located in …\GCB@Syn\G@Stools) this way. Replace C:\_YourPath_ with your real path.
REM --- Your code here: ---------------------------------------
REM Call mikroProg Suite for PIC - programming software:
"C:\_YourPath_\mikroProg Suite for PIC.exe" -q -w -pPIC%2 -v -f%1
REM --- End of your code. -------------------------------------
Made a new G@Stool, maybe it helps (replace the one in G@Stools folder):
Download
Happy new year to all
Steini
Tried the new G@Stool and same results.
I did discover something strange though.
If I compile a small GCB program such as the sample BlinkLED.gcb the issue occurs.
If I compile a larger program such as morse code.gcb then the issue doesn't happen.
It only appears to show up when the compile time is very short. morse code.gcb takes visibly longer to compile and assemble than BlinkLED so it appears to me to be some kind of timing issue of the window staying open longer than the compile despite being automatically closed by a successful compile.
Isn't there a way to keep the pop up window open and force a manual close?
I know I read it in the notes somewhere but now I cannot find it.
Did some testing; found that
- It only happens with WinXP, not Vista, not Win7
- it only happens, if "Capture output " is enabled in SynWrites "External tools" config.
As a workaround i put the compilation window on top of the screen, so SynWrites output area schould not be affected.
Use the download link from my post above.
Add stayopen as last parameter in SynWrite Option - External tools …. / Parameters
See FLASH previous made hexfile for an example.
Steini
The stayopen worked great.
Is there a way to display the memory used by the GCB program in the output window so the user knows how much space is left?
Hello GCB friends,
new version 2013-01-14:
Download
Regards
_________________________
Steini
This was great Frank.
The reporting of the memory size is perfect.
I have modified your GCB@SYN to create my own custom PIC only simplified interface.
With each update I have to go back and modify so I'm going to lock in to a level here soon so I can post it for others to use if they want.
I really like the new position of the message window. I also use the stayopen which works great.
One thing I have noticed though is when I open up a new session, the output window is all the way at the bottom and very thin. I drag it up to make it bigger and then I can see the output results.
When I shut down, I automatically save the session.
I also have it set to restore last session on open.
But each time GCB@SYN opens, the output window shrinks down a few lines. If I close and reopen several times, the output window shrinks down to very thin again.
This forces me to re-adjust the window almost every time I open GCB@SYN.
Shouldn't saving the session save the position of the output window?
Again, I'm using XP. It may be an XP thing. I'm going to try this on Win 7 when I get a chance.
That's a SynWrite issue. It happens for me regardless of the Windows Version (but never noticed before).
Maybe you should mention it in the SynWrite forum.
Steini
Seems fixed "Shrinked output pane". Beta of SW. Test it
It seems to fix it but now as I resized the output window, the Tree Structure window appears and dissapears as I move the output window.
If I then move the mouse over the Tree Structure X then the Title Tree Structure appears again.
This only happens on certain positions of the output window.
(Posted this on SynWrite Forum also)
Clipboard History also appears and dissapears as I move the output window.
Frank,
Next time you build the GCB@SYN, is there anyway to use the GCGB Cow icon in the build so rather than having a square box icon for GCB@SYN we have the Cow icon?
how can i edit "Make ASM" to show asm code after run? to not need to find the file and open after.
Recommendation- use "OfficeXP" theme by default. "Default" theme is SLUGGISH, shows redraw issues on panels resizing. OfficeXp is faster. And less issues yet
Hi,
Implemented some suggestions from the forum posters in
new version 2013-01-26:
Download
Hope you like it!
_________________________
Steini
Frank,
One bug showed up for me.
No matter what I put in SynHide, Run menu won't show options 0-3.
It only shows 4- 7 even though SynHide doesn't have options 0-3 hidden.
Are you seeing this?
Also,
If I make changes to the order and selections in the Run menu, where is that stored so I don't have to redo that every time a new version is released?
Hi
Some items are shown only, if a GCB sourcefile (*.bas, *.gcb, *.pbs, *h) is active in the editor window, because it makes no sense trying to compile/flash another kind of file. Check out Options - External tools … / Tool properties: / Lexers:
I recommend to backup all *.ini files in the SynWrite folder and replace the default ones with these after an update.
_________________________
Steini
Hello Steini
I used your editor, and I'm honestly very satisfied, great job.
You point out only that, the. Asm generated is hard to read, because it has no indentation, such as that generated by GCGB.
I hope you can fix it in a future release.
You already have some idea of what to add in the future?
Thanks, MC
Gentleman,
I an very impressed. I will stick with GCB now.
I will publish my code in the spirit that you have shown.
Well done!
Hi MC!
It has indentation, but it's set to 2 chars only in SynWrite. You can easily change that:
Options - Customize… - Editor2
-> Set the value in the "Tab stops" field to what you need (i.e. 8).
I rather would play around with some hardware projects :-)
_________________________
Steini
Frank,
Thank you for adding the Cow symbol and all the other improvements I've requested.
I'm working on a series of Great Cow Basic books for the CHIPINO module and having this IDE was the missing piece I needed.
The work you, Hugh, Alexy and others have put in to make such a great open source product for the embedded BASIC programmer is fantastic.
Hi Steini
Thanks for the reply, I confirm that it is a great interface for GCB.
MC
Hello to all.
I see that you can use winpic to load the Hex file in Pic.
E 'can use "MikroProg suite" (for USB) Mikroelettronica to program the pic directly from SynWrite?
Thank you.
Hi,
… worked on GCB@Syn again!
New version 2013-03-19:
Download
Regards
_________________________
Steini
Hi tonkawa53!
Should be possible. MikroProgSuite - manual says, that it understands commandline parameters to use it from other software. Edit flashPIC.bat (located in …\GCB@Syn\G@Stools) this way. Replace C:\_YourPath_ with your real path.
Tell us, if its works!
Good luck!
_________________________
Steini