+JAC! Posted February 27, 2023 Author Share Posted February 27, 2023 The daily build has been updated with the changes for these two issues: https://github.com/peterdell/wudsn-ide/issues/10 - Key binding conflict with Ctrl+Shift+0 on Windows Bindings have been changed to Ctrl-Shift-8/9 instead. Also the wording has been adapted to "Language" and "Build" instead of the specific "Assembler/Assemble/Compiler/Compile" to have a uniform wording for all languages. Maybe I'll later also move the entries to the other standard menus (File/Project/Run/Help) instead.https://github.com/peterdell/wudsn-ide/issues/6 - Support dark theme All icons have been converted from GIF with transparency to PNG with alpha-channel. The preferences keys for the syntax highlighting colors have been separated. This way the chosen colors are kept separately for light and dark theme. The title of the group box indicates, if dark theme is active. Default colors have been added also for the dark theme. Additionally, the tooltip of the color now shows the hexadecimal color value, so you can see the exact color code. Click the links to see the detailed explanations. I've not updated the stable version, because these a huge change and I'd like to first get some feedback. 3 Quote Link to comment Share on other sites More sharing options...
Jetboot Jack Posted February 28, 2023 Share Posted February 28, 2023 (edited) Hi, Quick question - I have installed/setup Eclipse and WUDSN and am using them with MADS on an M1 MacBook Pro with Atari800Mac X - and all is good. However I also want to edit/compile for 2600 and cannot figure out how to setup for support two platforms in Eclipse... sTeVE Edited February 28, 2023 by Jetboot Jack Quote Link to comment Share on other sites More sharing options...
+Stephen Posted February 28, 2023 Share Posted February 28, 2023 26 minutes ago, Jetboot Jack said: Hi, Quick question - I have installed/setup Eclipse and WUDSN and am using them with MADS on an M1 MacBook Pro with Atari800Mac X - and all is good. However I also want to edit/compile for 2600 and cannot figure out how to setup for support two platforms in Eclipse... sTeVE Possibly one of these 2 videos will help: Quote Link to comment Share on other sites More sharing options...
+JAC! Posted March 1, 2023 Author Share Posted March 1, 2023 Thanks Steven. The above works if you use the standard assembler for the target platform. E.g. MADS for Atari 8-bit, DASM for Atari 2600. https://www.wudsn.com/index.php/ide/features#Editor If you want to use a "foreign" assmbler (e.g. I always use MADS for all platforms), then you have to specify the platform explicitly in the main source file via an annotation. https://www.wudsn.com/index.php/ide/faq#FAQHardwareAnnotation 1 Quote Link to comment Share on other sites More sharing options...
Jetboot Jack Posted March 1, 2023 Share Posted March 1, 2023 Fantastic - thank you both for the information! sTeVE Quote Link to comment Share on other sites More sharing options...
Justin Payne Posted March 3, 2023 Share Posted March 3, 2023 @JAC! I'm modifying EdVentures example code. It runs just fine but I'd like to do some debugging but when I put the breakpoint it, it either doesn't hit it OR it crashes Altirra. Funny thing is, if I hit pause and then F9, the program runs. No breakpoint, the program runs. Suggestions? Altirra x64 v4.10 Eclipse Version: 2022-12 (4.26.0) Build id: 20221201-1913 Assembler: Mads Mad-Assembler-2.1.3 Wudns plugin: Latest. Just downloaded it. Quote Link to comment Share on other sites More sharing options...
+JAC! Posted March 4, 2023 Author Share Posted March 4, 2023 10 hours ago, Justin Payne said: @JAC! I'm modifying EdVentures example code. It runs just fine but I'd like to do some debugging but when I put the breakpoint it, it either doesn't hit it OR it crashes Altirra. Funny thing is, if I hit pause and then F9, the program runs. No breakpoint, the program runs. Suggestions? Altirra x64 v4.10 Eclipse Version: 2022-12 (4.26.0) Build id: 20221201-1913 Assembler: Mads Mad-Assembler-2.1.3 Wudns plugin: Latest. Just downloaded it. Thanks for the hint. Altirra by default assume a "casual" user who would not know what to do in a debugger, not a programmer and therefore displays this dialog. You have to change the "Tools/Options/Error Handling" to "Break into Debugger". I'll see how I can make that the default in future https://github.com/peterdell/wudsn-ide/issues/13. 3 Quote Link to comment Share on other sites More sharing options...
Justin Payne Posted March 4, 2023 Share Posted March 4, 2023 @JAC! Oh, jeeze. I saw that before but thought Option was for a 2016 version of Altirra. I looked again and found it. Thanks! Quote Link to comment Share on other sites More sharing options...
ilmenit Posted March 12, 2023 Share Posted March 12, 2023 (edited) @JAC!- With new WUDSN I receive following warning when assembling Atari project for Altirra with MADS. "Breakpoints will be ignored because the application 'Operating System Default Application' does not support passing source level breakpoints." I installed the new Altirra 4.20 beta, do I need to switch something in the configuration? With built-in Altirra 4.10 it did work, however for some reason this version had some issues for me and 4.20 has them fixed. Should I set something somewhere to allow breakpoints? How WUDSN is checking if the app is supporting source level breakpoints? Edited March 12, 2023 by ilmenit Quote Link to comment Share on other sites More sharing options...
+JAC! Posted March 12, 2023 Author Share Posted March 12, 2023 7 hours ago, ilmenit said: @JAC!- With new WUDSN I receive following warning when assembling Atari project for Altirra with MADS. "Breakpoints will be ignored because the application 'Operating System Default Application' does not support passing source level breakpoints." I installed the new Altirra 4.20 beta, do I need to switch something in the configuration? With built-in Altirra 4.10 it did work, however for some reason this version had some issues for me and 4.20 has them fixed. Should I set something somewhere to allow breakpoints? How WUDSN is checking if the app is supporting source level breakpoints? You have to select Altirra explicitly as the default application (incl. the path to the .exe) in the preferences to use instead of "Operating System Default". Only then the IDE can be sure you are using Altirra, since some other emulator could be registered for ".xex". 2 Quote Link to comment Share on other sites More sharing options...
Wilheim Posted April 3, 2023 Share Posted April 3, 2023 Hi! I'm trying to compile a cartridge image with WUDSN and MADS. I used to use the following parameter to compile with the proper file extension: ; @com.wudsn.ide.asm.outputfileextension=.rom But witth the new version of WUDSN it doesn't compile with the ".rom" extension anymore. What can I do? Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted April 3, 2023 Share Posted April 3, 2023 I think this is fixed in the 'daily' update. 1 Quote Link to comment Share on other sites More sharing options...
Wilheim Posted April 4, 2023 Share Posted April 4, 2023 21 hours ago, flashjazzcat said: I think this is fixed in the 'daily' update. It worked! Thanks. Also, now I'm using the "@com.wudsn.ide.lng.outputfileextension" instead of asm, as suggested on Eclipse. 2 Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted April 28, 2023 Share Posted April 28, 2023 @JAC! I've been rebuilding my PC and tried to download the zero installation files from here https://www.wudsn.com/productions/java/ide/downloads/eclipse-platform-4.19-win32-x86_64.zip. and from your web site here https://www.wudsn.com/productions/java/ide/downloads/wudsn-ide-win64.zip on both I get:- Has the download link changed ? or is there a server error? thanks Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. Quote Link to comment Share on other sites More sharing options...
+JAC! Posted April 30, 2023 Author Share Posted April 30, 2023 On 4/28/2023 at 5:28 PM, TGB1718 said: @JAC! I've been rebuilding my PC and tried to download the zero installation files from here https://www.wudsn.com/productions/java/ide/downloads/eclipse-platform-4.19-win32-x86_64.zip. and from your web site here https://www.wudsn.com/productions/java/ide/downloads/wudsn-ide-win64.zip on both I get:- Has the download link changed ? or is there a server error? Yes, the folders were restructured and there is a new installer. See http://www.wudsn.com/index.php/ide/releases 1 Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted April 30, 2023 Share Posted April 30, 2023 9 hours ago, JAC! said: Yes, the folders were restructured and there is a new installer. See http://www.wudsn.com/index.php/ide/releases Thank you, that downloaded fine Quote Link to comment Share on other sites More sharing options...
patjomki Posted August 21, 2023 Share Posted August 21, 2023 (edited) How do I find out which version of wudsn is installed? Edited August 21, 2023 by patjomki Quote Link to comment Share on other sites More sharing options...
E474 Posted August 21, 2023 Share Posted August 21, 2023 Startup Eclipse, then: Help -> About Eclipse IDE -> "Installation Details" 1 Quote Link to comment Share on other sites More sharing options...
patjomki Posted August 21, 2023 Share Posted August 21, 2023 1 hour ago, E474 said: Startup Eclipse, then: Help -> About Eclipse IDE -> "Installation Details" Ah, thanks a lot. There it is hidden. 😀 1 Quote Link to comment Share on other sites More sharing options...
dukdukgoos Posted December 25, 2023 Share Posted December 25, 2023 (edited) I noticed something today when doing some reconfiguring of my emulators: WUDSN doesn't seem to be able to find any emulators unless the full path is configured in the settings dialog, even if the emulator is part of the system PATH. So for example, I changed the Stella config in preferences from: C:\Programs\Emulators\Stella\Stella.exe to stella I have my Stella folder added to the system PATH so I can access Stella directly in the command line with just "stella" but WUDSN won't see it unless it has the full path to the executable. It's weird because the compilers work fine if they're in the system PATH (EDIT: compilers don't work either), but the emulators don't. Any ideas? EDIT: compilers don't work with only the executable name either, so it appears WUDSN or Eclipse isn't using the system path when executing a command. Edited December 25, 2023 by dukdukgoos corrected information Quote Link to comment Share on other sites More sharing options...
+JAC! Posted December 25, 2023 Author Share Posted December 25, 2023 (edited) 15 hours ago, dukdukgoos said: I noticed something today when doing some reconfiguring of my emulators: WUDSN doesn't seem to be able to find any emulators unless the full path is configured in the settings dialog, even if the emulator is part of the system PATH. So for example, I changed the Stella config in preferences from: C:\Programs\Emulators\Stella\Stella.exe to stella I have my Stella folder added to the system PATH so I can access Stella directly in the command line with just "stella" but WUDSN won't see it unless it has the full path to the executable. It's weird because the compilers work fine if they're in the system PATH (EDIT: compilers don't work either), but the emulators don't. Any ideas? EDIT: compilers don't work with only the executable name either, so it appears WUDSN or Eclipse isn't using the system path when executing a command. Correct, WUDSN uses the absolutes paths configured in the preferences because the system path is a shell property and cannot be used directly without opening a shell window. But in the latest versions of WUDSN, the installer also includes the standard assemblers/compilers in a default folder structure for the IDE. If no explicit paths are configured, they are found and used automatically. For the emulators, you can also choose to use "Operating System Default Application" then, it'll use the default for the file extension as defined in the registry. That also means less configuration but limits the parameters passing to the emulator to the executable file path. Edited December 25, 2023 by JAC! 1 Quote Link to comment Share on other sites More sharing options...
dukdukgoos Posted February 6 Share Posted February 6 @JAC! Getting the following error when compiling anything. Fresh manual install with Eclipse 2023-12, Temurin Java 21.0.1+12, WUDSN 1.7.2.202401300233 from "daily" repo java.lang.Error: Unresolved compilation problem: Invalid escape sequence (valid ones are \b \t \n \f \r \" \' \\ ) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommand.splitAtSpaces(LanguageEditorCompileCommand.java:199) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommand.executeInternal(LanguageEditorCompileCommand.java:303) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommand.execute(LanguageEditorCompileCommand.java:165) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommandHandler.execute(LanguageEditorCompileCommandHandler.java:55) at com.wudsn.ide.lng.editor.LanguageEditorFilesCommandHandler.execute(LanguageEditorFilesCommandHandler.java:64) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:99) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:298) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:232) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:174) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:488) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:485) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4273) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4071) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3659) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:342) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:648) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:342) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:651) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:588) at org.eclipse.equinox.launcher.Main.run(Main.java:1459) Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted February 6 Share Posted February 6 They all seem to be Java errors, do you have the latest version of Java installed ? Quote Link to comment Share on other sites More sharing options...
sanny Posted February 6 Share Posted February 6 And what do you have configured as "CompileCommand"? I don't know WUDSN, but it appears it could be an user settable configuration. Still a bug if you could enter things there that cause it to crash... Quote Link to comment Share on other sites More sharing options...
dukdukgoos Posted February 6 Share Posted February 6 I took a look at Github and it seems like maybe this has been fixed a few days ago, but maybe not released yet: https://github.com/wudsn/wudsn-ide/commit/6520f1e27af721dbcfb246cd9901268867b6f8ad 1 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.