Search results

  1. pleiser

    Is PICAXE support for Mac officially dead?

    For anyone else that's interested, I've released another update to my PicaxePreprocess script, adding many more of the features that PE6 has that the command line compilers don't natively support (Thanks again to J G for the pull request for many of the new features!) It now supports #IF...
  2. pleiser

    Python preprocessor script for #includes and compiler selection

    I finally got around to merging in your changes, (sorry I didn't get around to it sooner), thanks again for your contributions! I also did some more testing with this version, and realized (and fixed) an issue with accounting for the fact that the PICAXE 40x2 uses the same compiler as the 28x2...
  3. pleiser

    Python preprocessor script for #includes and compiler selection

    Sorry for the late reply, college finals have been keeping me busy! Yeah, same for me, I later found a C preprocessor (also linked in my readme) that would have probably done enough, but where's the fun in that? Sure! Feel free to free to add any additional options or features you want, I...
  4. pleiser

    Python preprocessor script for #includes and compiler selection

    Welcome to the PICAXE forum, and thanks for sharing your project! A couple years ago, I actually made a very similar project, coincidentally also using python. It's at https://github.com/Patronics/PicaxePreprocess, and, like yours, also has some sample files and examples included. It seems our...
  5. pleiser

    Is PICAXE support for Mac officially dead?

    I actually already tried this, and although the compilers seem to be a newer version than published on the website (modified in 2017, vs 2014), they didn't work, giving the error "bad cpu type in executable". Regarding the FTDI drivers discussion, I don't yet have an M1 Mac either, but I have...
  6. pleiser

    Is PICAXE support for Mac officially dead?

    Thanks for the response @Technical. I know I'm in the minority, but I suspect your online system will be insufficient for me and my peers. Is there an API available to directly access the online compiler? If not, that would be very, very helpful, if it could be implemented. If not, the features...
  7. pleiser

    Is PICAXE support for Mac officially dead?

    It's been a few years since MacOS Catalina came out, dropping support for apps that hadn't been updated in the last decade and change to support 64 bit Intel processors. When this happened, we were assured here by @Technical that, although AxePad is discontinued, it's replacement, Blockly, would...
  8. pleiser

    MacAxePad bug: pressing delete adds invisible (ASCII 08, BackSpace) characters, and doesn't delete the preceding characters from the line??

    Thanks for the reply, Hippy. I've been testing it more, the problem went away for a while, then came back, and now it's behaving normally again (hopefully it doesn't come back again). I forgot to mention that the problem wasn't exclusive to the backspace key, but also others, such as the...
  9. pleiser

    MacAxePad bug: pressing delete adds invisible (ASCII 08, BackSpace) characters, and doesn't delete the preceding characters from the line??

    All of a sudden I've been getting a weird bug in MacAxePad, where pressing the delete key adds delete characters instead of actually deleting anything, as well as moving the cursor around 2 spaces forward. This obviously makes axepad unusable for programming, and trying to run a syntax check...
  10. pleiser

    New (Beta) crossplatform (axepad-friendly) #include and #define preprocessor!

    By the way, I've more thoroughly documented and published the code for the preprocessor on github, for anyone interested. I've been successfully using the preprocessor with my robotics team for the last several months, and hope others have found it useful as well. If you have, I'd love to hear...
  11. pleiser

    MacAxePad needs to be updated for 64 bit for future compatibility

    I recently realized that the command line compilers for MacOS are also 32 bit, so they will also be unusable on MacOS after the next major update (likely in July). Are those going to be updated with a 64 bit version (and ideally perhaps including native #include and #macro directives)?
  12. pleiser

    MacAxePad needs to be updated for 64 bit for future compatibility

    It's not directly integrated into AxePad (though I'd be happy to work with Rev-Ed to integrate it into their tools if they're interested), but I have set up a makefile which runs the preprocessor, and works with the command line compilers to do the preprocessing and upload with the command...
  13. pleiser

    MacAxePad needs to be updated for 64 bit for future compatibility

    The preprocessor functionality should be useable in macOS and Linux with the preprocessor I developed for use with axepad. I welcome any improvements to it, or feedback about it.
  14. pleiser

    How to install PICAXE Visual Studio Code extension on MacOS?

    Given that apparently AxePad is obsolete, and Blockly only supports one open file at a time, I'm trying to install the VSCode extension, but all the mac installation instructions are "to be completed" How can I install these extensions?
  15. pleiser

    MacAxePad needs to be updated for 64 bit for future compatibility

    Is Blockly for PICAXE the official successor for AxePad? I have not looked into it in detail yet, as I am not interested in the block-based programming that (I assumed, anyway) are its primary focus. How does its feature set compare with AxePad and PE6? Does it support all the preprocessor...
  16. pleiser

    MacAxePad needs to be updated for 64 bit for future compatibility

    For the last couple versions, MacOS has started to warn users when opening apps that haven't been updated with 64 bit support, among them MacAxePad. AxePad is generally in desperate need of updates to match at least the essential features of PE6 (although the preprocessor I made helps supplement...
  17. pleiser

    New (Beta) crossplatform (axepad-friendly) #include and #define preprocessor!

    here's the latest form of the preprocessor's source code: #!/usr/bin/python #PICAXE #include, #define, and #macro preprocessor #todo: make defines behave like single line macros, allowing(parameters) #todo: more thoroughly test macro behaviors, especially with parentheses #Created by Patrick...
  18. pleiser

    New (Beta) crossplatform (axepad-friendly) #include and #define preprocessor!

    I just tested it again with both behaviors of #define, and after a small modification to fix a minor bug, it works great. here's an example input and output from the preprocessor of both types of define: Input: #define testing #define message sertxd("New Define") main: #ifdef testing...
  19. pleiser

    New (Beta) crossplatform (axepad-friendly) #include and #define preprocessor!

    @Technical, yes, I know that #define works with #ifdef and #ifndef etc, in axepad, however axepad’s implementation doesn’t work with the new behavior in PE6 of letting you define code substitutions, like the example in the manual of #DEFINE SetBackLedOn b0 = 255 : Gosub SendBackLED Also my...
  20. pleiser

    New (Beta) crossplatform (axepad-friendly) #include and #define preprocessor!

    I've continued working on it, and now it works with both relative and absolute paths (assuming the absolute paths start with a "/" as they typically do on UNIX anyway). I also added full support for the #DEFINE preprocessor directive! I'm planning to work on support for #MACRO next. I wonder...
Top