- Are there any key combinations to navigate between tabs? The default behaviour, if the text component has the focus, is that ctrl+tab and ctrl+shift+tab move on to the next component. Thus, pressing ctrl+shift+tab would move the focus to the tabs. However, once the tab has the focus you can use arrow-keys and ctrl+tab and ctrl+shift+tab to switch between tabs. To move focus to the text editor, you need to press "tab"...
- Is it common to have a mixed assembler project? I think a global assembler for all tabs is enough. Probably not, but I personally use it quite a lot. It's not only selecting different compilers, but also the parameter-textfield gives you the option to use parameters "on the fly" that override the global settings. Might be useful... ?
What are other common and often used cross assemblers? Currently, there'S specific support for KickAssembler and ACME. Relaunch64 may work with other cross assembler as well, but there are probably highlighting issue etc. So I would like to implement support for further cross assemblers... Any suggestions which could be added?
- I can't enter tabs into the source, instead the focus is changed.
- The line numbers are cut off at the right side more and more as the number gets longer, while there's still plenty of space on the left. Also more visible on bigger font sizes.
- The tab size is independent of font size (in pixels). Normally it's n*(width of monospace font), where n is configurable. The current behaviour is probably ok for variable width fonts.
- I use "java -Dawt.useSystemAAFontSettings=on" to get nice antialiased text. Is it possible to add System.setProperty("awt.useSystemAAFontSettings","on"); somewhere at startup to have this automatic?
- Thanks for supporting 64tass! The -T option is not recommended, that's only for die-hard c64 tass/tasm users who agree that 2+2*3 is 12 ;) The -W option has been removed sometime ago, the start address is always a word unless otherwise requested.
- "cld", "clv" is missing from instructions highlighting. What is "cls"?
- Alternate instruction sets highlighting would be nice for illegal opcodes, 65c02, 65816, etc.
- Compiler log could be erased automatically after each compilation. Only the last one is interesting usually.
- Opening a file using the dialog and compiling it works, but if I open from the command line and want to compile it then I get: Caused by: java.lang.NullPointerException at de.relaunch64.popelganda.Relaunch64View.compileFile(Relaunch64View.java:1301) at de.relaunch64.popelganda.Relaunch64View.runFile(Relaunch64View.java:1175)
- I think you forgot to add "help_userscripts.html" to the resources. The help button does not work because of this.
- VICE does not start, instead I get Couldn't get a file descriptor referring to the console. Not even from user script. If I use it in place of a compiler, then it works, probably because then it can log to somewhere.
Error message format for Kick assembler (guess): Error: <text> <linefeed> at line <line>, column <column> in <filename> ACME: fprintf(msg_stream, "%s - File %s, line %d (%s %s): %sn", type, Input_now->original_filename, Input_now->line_number, Section_now->type, Section_now->title, message); Where type is "Error", "Warning", "Serious error". Error message format for 64tass is documented here: http://tass64.sourceforge.net/#messages
Quoting soci- The line numbers are cut off at the right side more and more as the number gets longer, while there's still plenty of space on the left. Also more visible on bigger font sizes. Hm, this behavior is different on my machines where it works as intended. I'll keep that in mind and try to figure out what this could be.
Quoting soci- VICE does not start, instead I get Couldn't get a file descriptor referring to the console. Not even from user script. If I use it in place of a compiler, then it works, probably because then it can log to somewhere. Strange. Did you specify a file path to Vice?
