Jump to content

dukdukgoos

Members
  • Posts

    58
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Tokyo, Japan

Recent Profile Visitors

1,736 profile views

dukdukgoos's Achievements

Star Raider

Star Raider (3/9)

13

Reputation

  1. 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
  2. @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)
  3. Just a friendly bump to see if there's anything new planned for this app. It's quite useful and a shame it hasn't seen much activity lately...
  4. 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.
  5. As it sounds like this is useful information to retain, for now I'm just going to manually remove the lines from the DAT I use in RomVault. Maybe the RomVault developer will update his parser at some point. We also might consider changing the DAT format to the XML-based one. Not sure if this would fix the issue with RomVault, but it's probably better in any case to use XML if you're tracking rich data in the file (more extensible, flexible data structures, easier for other tools to parse/use the data, etc.)
  6. Yeah, I agree it should ignore unexpected tags, but as the ClrMamePro DAT format is non-standard it has to have a custom parser written, and I guess he just followed the spec verbatim. Most DAT files I see these days are in XML format, which is super easy to parse with standard tools. RomVault is a GREAT rom manager though, nothing else comes close imo... except for this issue What are the custom tags used for in this case? Something on the a8p site?
  7. Confirmed with the ROMVault dev that custom tags are not supported. I found the file format definition for ClrMamePro-style DATs here: http://www.logiqx.com/DatFAQs/CMPro.php
  8. This new DAT crashes ROMVault when updated. Is it because of the "a8p" datapoints that have been added to every game?
  9. I was affected by this (I imagine everyone on Windows with an extra keyboard installed would be) I remapped to Ctrl-Shift-8 and -9 (just moved everything down one key to avoid 0) What I did worked fine if you want to keep it pretty close to how it was before. I'd be fine with the F11/Ctrl-F11 as it's Eclipse standard too
  10. New installer didn't work for me on Windows. Here's the relevant error lines: Unpacking wudsn-ide-tools-main.zip to C:\Programs\WUDSN\Install. wudsn-ide-tools-main/ASM/DASM/test/cmdline_defs/declare_var_mac.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\cmdline_defs\\declare_var_mac.asm' wudsn-ide-tools-main/ASM/DASM/test/delete_empty_binary.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\delete_empty_binary.asm' wudsn-ide-tools-main/ASM/DASM/test/m_switch_2.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\m_switch_2.asm' wudsn-ide-tools-main/ASM/DASM/test/m_switch_3.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\m_switch_3.asm' tar: Error exit delayed from previous errors. Copying files to C:\Programs\WUDSN\Tools. 1918 File(s) copied Removing folder wudsn-ide-tools-main. Installing Eclipse. Downloading eclipse-platform-4.19-win32-x86_64.zip from https://www.wudsn.com/productions/java/ide/downloads/eclipse-platform-4.19-win32-x86_64.zip. Unpacking eclipse-platform-4.19-win32-x86_64.zip to C:\Programs\WUDSN\Tools\IDE\Eclipse. tar: Error opening archive: Unrecognized archive format Looks like there's some corruption at the beginning of the paths and it's trying to use tar for zip files
  11. Great, thanks! It looks like you already had the zipped DAT on your server (35382958_Atari8bitPreservedSoftware2022-09-10.zip) so you don't need mine if you want to delete it
  12. Yes, that's exactly the process I had in mind, as it ensures all renames and deletes are handled by the DAT and don't need to be included in the update pack. I went ahead and made an update pack for the current release. Comes in at a much slimmer 102mb. Could be helpful for those who haven't already got the full pack. Optimally the update packs would be posted and archived on the archive sites (https://atari-cellar.net/ and https://atari8bit.net/) along with the full releases. 1210149540_Atari8bitPreservedSoftware2022-09-10UPDATE.zip Atari 8bit Preserved Software 2022-09-10.zip
  13. Do you think we could get an "update pack" when a new release is made? That is, a zip with only the new and changed files plus the DAT for the new release (which is already available now). This would allow us to update to the latest version using ClrMamePro or other ROM managers to process the previous release plus the update pack to make the new release while saving bandwidth by avoiding redownloading the whole thing again. Files that were only renamed or deleted between releases would be handled by the ROM manager with the DAT file without needed additional space in the update pack. Atari files are small so it's not a huge deal to download the whole thing every time, but doing things efficiently is always good, and if we start adding more cassette WAVs or raw Kyroflux images the releases could get much bigger in a hurry.
  14. Maybe this has been asked and answered already, but is there a DAT available for this collection?
  15. That's exactly the stuff I'm interested in though... the conversion of a 2600 kernel to 8-bit. I assume the 8-bit version is still a kernel, "racing the beam" style? Alternately if you know of any examples of other 2600 kernel to 8-bit conversions that helped you learn how to do it I'd be interested in seeing those.
×
×
  • Create New...