Hello Paul
I noticed that the language file has been updated.
Based on this, I have adapted the German language file for the upcoming release version 1.3.0.
Hi Joerg, you must be looking at the Development branch :-)
Be careful using that branch right now because I am in the process of adding a debugger (GDB Debugger). A lot of code there that will be constantly changing over the next couple of weeks. Test code, temporary popup dialogs, etc.
Thanks for the translation! I will ask you again for an updated version before 1.30 is actually released.
The best debugging tool that I have used is DebugView.
Using GDB allows me to have FB compile programs with -g thereby creating the necessary debug info for GDB. Allows me to handle breakpoints, stepping through code, and displaying local/global variable values, watch variables, etc. I already have the breakpoints partially working. I don't think that DebugView can display application variable values, etc. I thought that it just captures output debug messages that the user embeds into their programs(?)
It displays the information which you tell it to show, without the noise of a ton of useless information. An skilled programmer knows which parts of his code need to be watched. I never have used a debugger, but if you find it useful...
Hello Paul
I regularly check the developer version of the tiko editor on GitHub.
The customized version of the German language file is based on your developer version.
Just as I regularly visit Jose's GitHub page and integrate the latest versions of his AFXNova into my environment. :)
I look forward to hearing from you.
I will then create the new language file in good time before the new version is released.
Thank you for developing the new editor.
My reasons for wanting the GDB debugger integrated into Tiko is a little selfish on my part. I have been trying to do more work on the FBC compiler source code and tracing my way through it at runtime is very difficult. There are countless files and you jump all over the place. You get lost very quickly. It will also be nice to be able to see the state of variables as I step through the code. I have tried using Sarg's FBDebugger but I find it a little not to my tastes and it only works with GAS64 compiles.
The current test state of the debugger in Tiko is such that I can set breakpoints and then run the code and it will break in the correct spots. I can then step over code and into and out of functions. The editor also displays red circle icons for the breakpoints, and a yellow pointing arrow on the active line as the debugger moves through the code. It's all still a work in progress but so far I am happy with it.
Hi Paul,
I came across Tiko Editor and liked it.
I am however having a problem passing an options file (@voptions) to the compiler.
I have tried a number of ways but "-s console -gen gas64 @voptions" in the build configuration seemed to be the most logical. It errors out with:-
Failed Compile (Errors 2 Warnings 0 [2025-11-05 07:24:22])
Command Line:
D:\tiko-main\Toolchains\FreeBASIC-1.10.1-winlibs-gcc-9.3.0\fbc64.exe -m "C:\users\roger\_dev1\source\languageONE\@editorTOO\test.bas" -v -s console -gen gas64 @voptions @options -x "C:\users\roger\_dev1\source\languageONE\@editorTOO\test.exe"
error 26: File access error, options
It seems like you automatically insert an options file into the command line. How does that mechanism work ?
Hoping you'll able to point me in the right direction ?
Cheers
Roger
Quote from: roger@languageONE.com.au on November 04, 2025, 04:56:24 PMHi Paul,
I came across Tiko Editor and liked it.
I am however having a problem passing an options file (@voptions) to the compiler.
I have tried a number of ways but "-s console -gen gas64 @voptions" in the build configuration seemed to be the most logical. It errors out with:-
Failed Compile (Errors 2 Warnings 0 [2025-11-05 07:24:22])
Command Line:
D:\tiko-main\Toolchains\FreeBASIC-1.10.1-winlibs-gcc-9.3.0\fbc64.exe -m "C:\users\roger\_dev1\source\languageONE\@editorTOO\test.bas" -v -s console -gen gas64 @voptions @options -x "C:\users\roger\_dev1\source\languageONE\@editorTOO\test.exe"
error 26: File access error, options
It seems like you automatically insert an options file into the command line. How does that mechanism work ?
Hoping you'll able to point me in the right direction ?
Cheers
Roger
Hi Roger,
Interesting. I've never used this option for an external command line options file.
I did notice in your post that the "Command Line:" includes 2 different options files? One called @voptions and a second called @options, whereas just prior to that you stated that you modified the Build Configuration to be "-s console -gen gas64 @voptions" (notice, without that second @options).
If that is not the problem, then I wonder if the issue that the @voptions file can not be found. I wonder if you can either try using a full path name to the file, or try placing that file in different places until the compiler finds it. Try the folder where your source is located, and maybe even the folder where your FBC compile exe is located? Not sure what the answer is... yet. :-)
It seems that tiko is assuming an options file in the source directory. I renamed mine from voptions to options and it worked fine. Simple fix if you know it I guess.
Also..
I read you were working on a adding a debugger and would look forward to that. I like that tiko is fairly simple and would probably keep it that way. I prefer running batch files for all my compiling etc so it's nice to be able to hook into that easily.
Just a couple of things I've noticed initially..
1) In darkmode the compiler messages text is still black and pretty hard to read
2) Ctrl-F (Search) pops up the window but doesn't give it focus. I think Ctrl-F for searching is so ingrained now that (certainly I) don't look up. I just Ctrl-F and key the search string in.
Anyway, keep up the good work
Cheers
Roger
Interesting that I don't have either of those two problems that you mentioned. Compiler results and/or Compiler Log file text always displays with a white on dark gray color. The Ctrl+F Find always places the text cursor and sets focus to the Find textbox. I'm not sure what the problem could be but if others also experience this same problem then maybe it is something that I am missing.
For the color issue, make sure that you've installed tiko correctly so that it can load the dark theme file. It expects it to be in the settings\themes subfolder. I assume that you have not modified that default_dark.theme file.
The debugger is a work in progress. Currently you can compile your source code and step through it but that's about it. I haven't been spending a lot of time on that code yet because I have been doing other things but I think given time it will progress along quite nicely.
Thx Paul,
I wouldn't worry too much about it.
I am running under WINE so a few funny things may go on. Mostly though it seems to run ok.
I'll boot into Windows later and give it a shot
Cheers
Roger
EDIT:- Just did a quick check and I can confirm that Yes, it is WINE that is the problem. Both things I mentioned are fine on a bare metal Windows 11.
Also in relation to my original post:-
CompilerSwitches=@options ----> this is a line from settings.ini. I would hazard a guess that this is where things are getting mixed up with a users own Options file.
Ah, yes, Wine would be a problem. I haven't had much success running it under Wine. I tried WinBoat (under Fedora) on another Win32 application but it didn't run. I think though that once WinBoat matures it may be a better option than Wine.
Yeah I had tried WINE - gee more than a decade ago - and it really wouldn't run anything, but I gave it another shot a few months ago and it seems to be far more capable.
Never heard of winboat, I'll take a look at it.
Anywho,good luck with tiko, I'll check back every so often and look for any newer versions.
Cheers
Roger