New version 1.0

[prb28]

Discussion and feeback about the new version 0.22.
The main objectives of this version are:

• easy management of the binaries (automatic download and update)
• easy download of the example workspace
• display of the errors from vasm / vlink

[prb28]

I'm preparing a little video the extension vsix to test

[prb28]

[prb28]

Extension binaries: https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_1/amiga-assembly-0.22.0.vsix

[Real-MJoe]

Sorry, it´s not work for me:

[prb28]

This extension is needed : https://marketplace.visualstudio.com/items?itemName=mindaro-dev.file-downloader
But it should be downloaded automatically...
I try with a clean install.

[prb28]

It think it's fixed: https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_1/amiga-assembly-0.22.0.vsix

[prb28]

Thanks for testing

[Real-MJoe]

Great, now it works as it should :)

[prb28]

You may find other bugs... it's more like an alpha stage.
If you are used to vscode you can build with ctrl/shift/b and the build traces are in the terminal.

[Real-MJoe]

Is it possible to compile only the current file if you have multiple files in the workspace. Currently all are compiled in ascending order by name.
Is it possible to specify the order of multiple files to be compiled?

[prb28]

You can specify the first one where the main() is (in the vlink options https://github.com/prb28/vscode-amiga-assembly/wiki/Building).
For the other files you'll need to use a makefile.

[phaze101]

Hi, I like the new addition to the extension. Thanks very much for doing this. Please note that on Windows machine the gencop workspace didn't work as per my video. I tried several times after the video too. My code is running from drive D and not Drive C, not sure if this creates any issues.

I recorded a small video of what I would like to see. Please see my comments during the video and what I am changing.
https://youtu.be/hWznvhNSinM

Also in my comments I showed you things that need to change for FS-UAE since the config parameters for a standard A1200 is wrong

If this is an issue what I need not a problem. I will show how to do this manually. I am thinking that maybe when one creates the workspace you are asked for the source filename that you want to give to your code.

For beginners gencop.s is also confusing. I would have preferred MyProgram.s or MyAsm.s or in my case Game.s :)

Please note it is still uploading the video so give it some time is quality is not good. YT takes time to process a video.

Thanks for all the what you have done so far. Much appreciated.

[prb28]

Oh the grey screen is normal, the copper list is setat this point, you must let the program run further (type F5 to continue).
(The video is still in 360p.)

[phaze101]

ok I will test better than. It never showed up so will try again.

YEs it is still processing. It is 12 minutes long and I recorded it in HD 50 frames so I guess youtube is lowering the resolution of it.

[phaze101]

You are right the code works. It just took its time

[prb28]

WinUAE works better on windows.

[phaze101]

Yes it is a better but both worked. I tested the extension properly now.

I noticed that you moved the bin directory under appdata on Windows. Is it possible to specify a different directory for where it gets downloaded or created?

The reason why I am asking is if someone wants to create more configs for FS-UAE or WinUAE is it not intuitive, . In my tutorial series I will need to show how to add an A500 Config that uses Kick1.3 and another for the A1200 that uses a Kick of 3.1. AROS is ok as default but testing code for real Amigas should be done on Kickstart.

[phaze101]

I uploaded another video and this one was available immiadetely. Stupid YT

https://youtu.be/Pg2x3bUZHps

[phaze101]

The game.s is what I want to call it in my tutorial series. It was an example. main.s is good but it would be good to call it what we want and then the script will adjust.

yes the setting.json lets you change the directory but the downloader everytime you start VC repopulates it with its link.

So I did go and edit the settings.jason but it always changed it back in the end.

[prb28]

The downloading problem is a bug, I've already fixed it but I'm finishing the renaming before packaging a fixed version.

[phaze101]

yes sure take your time. No rush. I am glad I am helping out.

Here is some info about as to why I want to use your extension. I am constantly bombarded with people asking me how to setup a dev environment for the Amiga even though I have videos out there that show to set it up. This many times puts people off since it is not easy to set a dev environment for a beginner. With your extension this make things very easy. A person can just install your extension, create a project file (You should call is a project file and not example project) and of they go. They can start coding. My aim is to get more coders in the Amiga scene.

I would like to tweak the EMUs (both FSUAE and WinUAE) to be able to run an A500, A600 and A1200 machine. This means 6 (with and without debug) for each emu hence 12 in total is you have Windows and 6 if you have MAC and Linux. Also there should be a directory called ROMs where one can upload the roms is they want to. I know maybe 12 is too much in your head but trust me in Amiga with all its different kind of machines and kickstarts it is good to have this. Of course this can come later while all this is fixed. It is not urgent. Right now I can live with an A500 in WinUAE and A1200 in FS-UAE.

There are some settings in FSUAE and WinUAE which I do not know yet since I did try to create this file and pass it to you. In WinUAE I do not know how to tell it to select different configs. In FSUAE it is the same but how to tell it where the ROMs are. This is really hard without the launcher of FSUAE.

I hope this helps.

[prb28]

That's the point simple and strait forward to start coding.
This extension is mainly though for people discovering the amiga with the inline documentation and other display options.
And it's missing a Getting started video so I'm happy to help your goal !

12 configurations seems a lot, and without the roms (cannot add it to the binaries, they are licensed), many of them will not work from start. So it can be confusing.

For the options I already did it once, I'll find an example later tonight.

[phaze101]

Well I think we are helping each other here :) There will be definitely a how to but I am happy to show it as I go along with updates. I am not looking for a perfect start of the extension as long as it gives the idea. I have used the extension since it was 0.7 if I remember correctly for quick tests but now it is time to take it for a real drive :) It is good enough.

It is 12 because WinUAE and FS-UAE 3 each and then debug. This will only be so on windows. On the other machines will be 6 but in theory you do not need that much. I am happy with what you have now. It is a start so no rush

[phaze101]

tasks.jason - link config should be as below else it will create an .o file for each .s file that you have in all folders. This will cause the linker to get confused.

before assembling the build directory should be cleared out. If there are link errors they will continue to appear.

		"vlink": {
			"enabled": true,
			"command": "${config:amiga-assembly.binDir}/vlink",
			"includes": "*.{s,S,asm,ASM}",
			"excludes": "",
			"exefilename": "../uae/dh0/game",                                                              Note I renamed the directory to game
			"args": [
				"-bamigahunk",
				"-Bstatic"
			]
		},
		"problemMatcher": [],
		"label": "amigaassembly: build",
		"group": {
			"kind": "build",
			"isDefault": true
		}
	}

[prb28]

Only the files resolved by the vlink task (include / exclude) are linked. So, no need to clean the build dir.
Nonetheless you have a command to clean it, it can be used as a preLaunchTask.

the include : "**/*.s" is useful if you want to organize your project files in folders or add some 3rdparty and do not mix it with your sources.
I think it's more easy to leave it like that to someone starting a project.

[prb28]

An example of the pre-launch clean:

{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "amigaassembly",
			"vasm": {
				"enabled": true,
				"command": "${config:amiga-assembly.binDir}/vasmm68k_mot",
				"args": [
					"-m68000",
					"-Fhunk",
					"-linedebug"
				]
			},
			"vlink": {
				"enabled": true,
				"command": "${config:amiga-assembly.binDir}/vlink",
				"includes": "**/*.{s,S,asm,ASM}",
				"excludes": "",
				"exefilename": "../uae/dh0/gencop",
				"args": [
					"-bamigahunk",
					"-Bstatic"
				]
			},
			"problemMatcher": [],
			"label": "amigaassembly: build",
			"group": {
				"kind": "build",
				"isDefault": true
			},
			"dependsOn": [
				"Clean build directory"
			]
		},
		{
			"label": "Clean build directory",
			"command": "${command:amiga-assembly.clean-vasm-workspace}"
		}
	]
}

[phaze101]

Hi, yes but the issue is not that. That was a suggestion to have.

If you leave this line in launch.jason
"includes": "**/*.{s,S,asm,ASM}"

If I have another directory say with startup.s (amiga hardware programming files tend to have this type of file) it will create a startup.o no matter in which directory I created it. Then the linker will have issues to link to it. Also Amiga.s file normally call other Amiga.s files. Lets say I have game.s, then play.s, collision.s, enemies.s. These will be files included by the main.s hence you need to only assemble the main.s and main.s will call the rest. Linker will really get confused if you do not do this.

[prb28]

That makes sense.

[Real-MJoe]

Q: Where is the variable "amiga-assembly.binDir" defined? If I set it for e.g. in the settings.json the new value is never used in the task.json.

[prb28]

Yes, it's a bug. I'll update the extension soon.

[prb28]

For the default configuration I think, the entry asm file should be set. What do you think ?

[prb28]

That seems to me a bad choice. I prefer having the build fixed on a file and typing ctrl-B anytime without bothering about the current opened file.

[phaze101]

I prefer to have that option than not. I think you are thinking in the terms that an ASM file should be only one file. That is not a good way of organising code. You need to divide the code in multiple files of .s hence why it is a good thing to have even though it will not assemble if you are not in the right tab. One just needs to go to the right tab to do so.

[gaoluobe]

@phaze101 I agree it is fundamental to be able to work with multiple .s file and previous versions of this this project worked fine doing so. I am not sure if I am missing missing... but requiring to be in the right tab to assemble the file would be a nightmare. The expected behaviour is that build action always assemble and link all files at once. Also, so far if you just want to build the selected file just saving it was triggering the assembling for that file.

[prb28]

@phaze101 if you are working in you collision.s file, you just have to type F5 to build and debug you project, no need to change tab, I think it's more efficient. But like python, an example configuration to build and run the current file can be added.

[phaze101]

@gaoluobe I stand to be corrected since I might have tried to used it wrongly but it didn't work (unless you are referring to .i files then it did) with multiple files. If you had more than one .s file it would fail (linker gets confused) and that is still till latest downloadable version (I have the perfect simple project related to this to share if needs be). It is one of the reasons why I didn't use it as much as I wanted however now it does that is the most important thing and it does it very well. It still has the issue if you have more than 1 file in root as .s it will not work but I do not consider it a major thing. (see further down responses)

As for taking the name of current tab it is a choice of preference. I have no issue in using Kick assembler in Sublime (I use the extension of KickAss for it) and to be in the main file to assemble my C64 code. It is not the end of the world. My main point was that I prefer to have the option to have multiple files that are .s then not having them just because I am not on the right tab.

[prb28]

For the Kickstarts

For fs-uae launch configuration add the parameter:

• "--kickstart_file=C:/my_path_to_kickstarts/Kickstart1.3.rom"

For winuae launch configuration add the parameter:

• "-r", "C:/my_path_to_kickstarts/Kickstart1.3.rom"

[phaze101]

wow this is cool thank you. I really need this.

Do you have a links for all config parameters of WinUAE and FSUAE?

[prb28]

Not really, my sources:

• http://eab.abime.net/showpost.php?p=1357595&postcount=253
• https://fs-uae.net/docs/options

[phaze101]

wow thanks

[prb28]

Here is the new release : https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_1/amiga-assembly-0.22.0.vsix

[phaze101]

I do not want to mix system includes with my own includes. That is one reason. @prb28 please create another .s file in root and you will see what I mean. It has nothing to do with dirty this is what beginners will do. I won't but I just wanted to make you aware.

BTW I am very pleased with the extension as I said so please do not take this negatively. It is extremely way miles better than from where it was. I will definitely recommend it for any beginner out there that wants to start coding for the Amiga. It is seriously Amazing what you did and thanks for giving me the option of sharing my opinion and for you taking the time to listening to me and my crazy ideas. Amazing improvement.

[prb28]

Let's say I have 2 .s files in the root directory: "a.s" and "b.s", the entry point is on "a.s" and it calls some symbol in "b.s" (really not a best practice).
Then configuration :

• "includes": "**/*.{s,S,asm,ASM}",
• "excludes": "",
• "entrypoint": "a.s",

The build will do:

• List files with the include/exclude configuration - it will get a.s and b.s
• Build with vasm a.s and b.s to build/a.o and build/b.o
• Link with a.o and b.o with a.o in first position (entrypoint)

Event if it is not a good practice, I think this way of building is possible. And some coders may use it.

[phaze101]

No that is what you are assuming that a calls b or vise versa. Forget best practises. Beginners do not know this. It wont call anything. It will be just some beginner that creates a file test.s. That's why the linker get's confused. It will happen although I will explain it in my video / streams but still and why I suggested the build should be cleaned.

As I said it is not the end of the world and if there is an easy fix for it it would be great else we can all live with it. I won't do that mistake but I am sure beginners will.

[prb28]

Ok, I'm starting to understand....

You have a beginner and he uses the workspace folder like this:

• write is first game.s
• renames game.s as game_v1.s
• modifies game.s and hopes it will work as it. The current build will mess the result exe.

When you ask to build the current tab, you want to run game.s or game_v1.s to view/test differences.

Is that right ?

[phaze101]

Yes exactly. I am sorry but I constantly think of what beginners will do. Every day I get questions related to the setup of the assembler or the environment.

BTW just tested it with latest update of VC V1.62. It is all fine

[phaze101]

Besides F5 are there other keys used by the extension? I tried to look in the documentation page and couldn't find any.

[prb28]

No all the keys, as F5, are the default keys from vscode.

[phaze101]

ok thanks and thank you once again for all this. I am using it right now and I am really enjoying the extension.

[phaze101]

Is it possible to see memory as hex byte data?

[Real-MJoe]

As an external tool I can also recommend EASy68. It counts the cycles least correctly ;)

[phaze101]

@Real-MJoe Yes I know about it too but that doesn't interface with VC. This is the beauty of this.

[phaze101]

@prb28 here is a link of what I did using your extension. It can give you some ideas

https://youtu.be/TGq19zPQIUA

[Real-MJoe]

@phaze101: The EASy68 calc right. Show the calculation of the 68counter extension. Two result for the same command:

[phaze101]

@Real-MJoe yes I can understand that it is not perfect. I am sure in future it will be updated and will do it better. However for learning purposes and helping beginners this extension is a good start but yes I agree with you from this point of view.

Also I have to admit I still prefer the old notation than the new notation. Somehow it still sinks better in my head :(

BTW @Real-MJoe thanks for pointing this out. It is good to know. I didn't know it had this issue but let's give it some credit since the E68K has been there for long and this is new :)

[gaoluobe]

@prb28 @phaze101 @Real-MJoe thank you so much for your time on this and sorry to come after the battle. Please, when it will be the right time to release, it would be awesome if you could sum-up the changes needed (if any) to migrate from 0.21.x to 0.22 projects. Thank you!.

[prb28]

The battle is not over !
I've started a wiki page https://github.com/prb28/vscode-amiga-assembly/wiki/BreakingChanges.
I'll update it at the end.

[prb28]

Still working on feature #128 ...

[phaze101]

@gaoluobe thanks. This new version is a break through in my opinion and @prb28 is the person we should all thank. In few hours after I posted my ideas or enhancements he just went and implemented them. Very cool of him but also thanks to all the others that helped or posted suggestions.

[prb28]

New extension pre-release : https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_2/amiga-assembly-0.22.0.vsix
feature #128 added.

[prb28]

@phaze101 What about an alternate configuration for single file build:

			"vlink": {
				"enabled": true,
				"command": "${config:amiga-assembly.binDir}/vlink",
				"singleFileBuildDestDir": "../uae/dh0",
				"args": [
					"-bamigahunk",
					"-Bstatic"
				]
			},

That will build/link the opened file and generate an executable with the same name without extension in the singleFileBuildDestDir.

[phaze101]

@prb28 I like this. Perfect.

[prb28]

@phaze101 new extension : https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_2/amiga-assembly-0.22.0.vsix
Files filtered in example and new variables in the settings to change the github URL of the example project.

                "amiga-assembly.binariesBranchURL": {
                    "type": "string",
                    "scope": "resource",
                    "default": "https://github.com/prb28/vscode-amiga-assembly-binaries/archive/refs/heads",
                    "description": "URL to retrieve the binaries branches"
                },
                "amiga-assembly.binariesTagsURL": {
                    "type": "string",
                    "scope": "resource",
                    "default": "https://api.github.com/repos/prb28/vscode-amiga-assembly-binaries/tags",
                    "description": "URL to retrieve the binaries tags"
                },
                "amiga-assembly.exampleProjectBranchesURL": {
                    "type": "string",
                    "scope": "resource",
                    "default": "https://github.com/prb28/vscode-amiga-wks-example/archive/refs/heads",
                    "description": "URL to retrieve the example project branches"
                },
                "amiga-assembly.exampleProjectTagsURL": {
                    "type": "string",
                    "scope": "resource",
                    "default": "https://api.github.com/repos/prb28/vscode-amiga-wks-example/tags",
                    "description": "URL to retrieve the example project tags"
                },

You can create your project or fork mine on github and use it.

[phaze101]

@prb28 I tested the new extension. Wow another good improvement. Very cool. Smaller and more clean. You could still leave the License just insert it in its own directory. I feel bad now that I had moved it since I did not mean that it should not be there. I just wanted to be in a folder to look cleaner.

where do I need to go to tell it to use get my github version.

[prb28]

Type Ctrl+, to go to the settings
then:

[phaze101]

@prb28 awesome. This is mega galactic handy. Wow this new version is really a break through.

[phaze101]

@prb28 dum question here.

what are the heads and tags in this case?

[prb28]

The url heads is used the retrieve the master branch with the code.
The url tags to retrieve a selected tag that corresponds to the version of the extension.
The download procedure tries to find a tag with the same number as the extension version. If it exists, it will retrieve it. If not the master branch will be downloaded.

[prb28]

@phaze101 new extension : https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_2/amiga-assembly-0.22.0.vsix
set your tasks configuration removing includes and excludes from vlink:

{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "amigaassembly",
			"vasm": {
				"enabled": true,
				"command": "${config:amiga-assembly.binDir}/vasmm68k_mot",
				"args": [
					"-m68000",
					"-Fhunk",
					"-linedebug"
				]
			},
			"vlink": {
				"enabled": true,
				"command": "${config:amiga-assembly.binDir}/vlink",
				"exefilename": "../uae/dh0/game",
				"args": [
					"-bamigahunk",
					"-Bstatic"
				]
			},
			"problemMatcher": [],
			"label": "amigaassembly: build",
			"group": {
				"kind": "build",
				"isDefault": true
			}
		}
	]
}

The current opened editor will be built.

[phaze101]

@prb28 when are you thinking of releasing the new extension?

[prb28]

I would like to do 2 things before:

• Updating the wiki with the migration how-to and others
• see if I can add a simple way to add to watch a memory dump for the beginners

I think this could be done within 2 weeks depending on the surprises. At the end of November for sure.

[phaze101]

@prb28 ok no problem and thanks. It is just to plan that is all from my side.

[prb28]

@phaze101 @Real-MJoe I need your opinion.
I've added two custom display when you add something to the watch. If you add a source label symbol or an address register (a0-a7), the memory pointed will be dumped.

What do you think?
Should it be added to new type of watches ?
what king of symbols would be interesting to have as a memory dump ?

[prb28]

The custom registers at $dff000 I have some questions in my head. Some of these are write only, others are read only and then lose the value like the collision register for sprites. Will these be effected by the way you are doing it? Apart from that I like it.
No they won't be affected, but I'm not shure that the Winuae integration is totally accurate when accessing to these registers.

BTW tonight I will start my first stream for the game series. Will use the last version that you gave me as an extension and share it with those that follow and ask them to test it out :) If you send me this one I will share this one. Which ever you prefer. Will show how to upgrade to your latest one once you release this.
Here is the new version: https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_2/amiga-assembly-0.22.0.vsix
Need to be polished and documented. I want to add a configuration for this display.
Best wishes for you live session !

[phaze101]

Thanks for the extension. Ok no problem and no hurry. It is a beginners series so I do not expect miracles :) By the time we will be able to do something you would have released it :)

[phaze101]

@prb28 expect others wanting the extension tonight. I will share it but please do not let others pressure you to release the final version. Take your time. It is not a race and you are doing a great job. Personally I prefer that the wiki is updated.

[phaze101]

@prb28 Thank you, Thank you, Thank you. The extension was a huge success. It did exactly as expected. Can't thank you enough

[prb28]

I'm glad that it worked!

[Real-MJoe]

For the development of the game Crazy Columns this extension was also used. :)

[prb28]

Great!

[phaze101]

@prb28 not sure if this is an issue, bug or something that I am doing wrong. Every time I save I am getting the extension to create an object file. The file was not created with the extension template and of course it is a .s

[prb28]

I understand the point. But there is no definition of what is a amiga workspace. What could be done is a global setting to disable it. You'll have to add a workspace/folder setting to reactivate is in an amiga project folder.
Otherwise as you have done you can deactivate the extension and activate is only for your amiga folders.

[gaoluobe]

actually, isn't it already per workspace, I am using 21.3 but I assume it is same than for 22.0 on this.

		"amiga-assembly.vlink": {
			"enabled": true,
			"includes": "*.s"

you can change the "includes" part so I wonder why it bleed in your c64 projects

[gaoluobe]

@prb28 Sorry I didn't see your answer, our comments crossed

[phaze101]

@gaoluobe aha I see why. Unfortunately .s or .asm are interchangeable. Even 8086 assembly uses these so not really something that you can go around and say I will use this for amiga and this for C64 and this for 8086 etc etc. What I do not understand why on save it needs to create an object file each time (apologies for my lamishness here) I was under the impression that when you use F5 it goes and builds but maybe there is history behinds this so I understand. As I said the work around is to disable it since .s or .asm are common file and from time to time we just need to edit them and that is it.

[phaze101]

@prb28 @Real-MJoe 21.3 I think it handled this differently but I stand to be corrected here. It used a workspace.

[phaze101]

@prb28 here is what I am doing so maybe you can do something like this. I have your extension and another extension called Motorola 68000 syntax highlighting. I disabled yours and enabled this one.

What I am thinking is it possible to switch your extension to behave like this one. Just shows syntax highlighting?

[prb28]

Yes, I can add a setting to disable the syntax checking on save with vasm. You'll only have the highlight.

[phaze101]

@prb28 I knew it. You always have a solution. Thanks for thinking of doing this.

[prb28]

https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_2/amiga-assembly-0.22.0.vsix
You'll find the option in the settings : "Check Error On Save".

[phaze101]

Thank you will check it out

[prb28]

New pre-release : https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_0.22_2/amiga-assembly-0.22.0.vsix
Bug fix - the last one may have a broken formatter.

[phaze101]

Thanks for the update

[phaze101]

@prb28 tested and worked well for me

[prb28]

This version deserves a 1.0 !
https://github.com/prb28/vscode-amiga-assembly/releases/download/pre_1.0/amiga-assembly-1.0.0.vsix

[phaze101]

perfect will test

[prb28]

@gaoluobe I've update the migration page : https://github.com/prb28/vscode-amiga-assembly/wiki/BreakingChanges
Al the wiki is updated and cleaned.
Please tell me if you have trouble with the migration.

[phaze101]

@prb28 I do not have much to migrate in my case so can't really say I tested it. Having said that I checked the Wiki docs and although you update the DOCs some of the screen shots still reflect the old extension. Just to give an example the IFF/ILBM Viewer. It is not the end of the world but thought I let you know. I just tested it a few and it looks fine. Just going to bed will test better tomorrow but so far so good.

Anyway well done. It really came a long way from where it was. Loving it and I had very very positive comments about it, Check my youtube.

[phaze101]

@prb28 I tested it quite a bit yesterday and it looks good to me. I didn't have one single issue. I tested it will multiple files and it behaved as expected. Very pleased.

When are you thinking of releasing it?

[prb28]

Yes, this week-end, if everything goes right.
I'll look for the old screenshots in the wiki to replace some that wouldn't be accurate.
I hope that the migration of the workspaces won't be painful for some users....

[gaoluobe]

@prb28 thank you and sorry for the delay. I'll try to check it this week. I am trying to see the breaking change page but I am getting a 404. Also unrelated, but I was looking at the VBCC integration and was wondering if it could be more seamlessly integrated later on. Right now there's a makefile to be synced-up... maybe something to consider for a later update ? Thanks again for your work, I will for sure test it and provide feedback as soon as I can.

[prb28]

@gaoluobe the url is: https://github.com/prb28/vscode-amiga-assembly/wiki/Breaking-Changes

The use of a makefile is a good option if you have a big project.

[mithrendal]

exciting ! 😍

[prb28]

It's released have fun !

[prb28]

@phaze101 ok, If you agree, I'll add the description in text and a link to your video in the wiki in the FAQ.

[phaze101]

@prb28 Yes sure. I will send you the link after I stream it and uploaded it to Youtube.

[phaze101]

@prb28 for the above link is this https://tinyurl.com/p101-lmag - Episode 4 to be precise

Also something that I thought it would be great to have, is to have some sort of todo list then when you say completed it will be like a devlog trace.

[prb28]

Also something that I thought it would be great to have, is to have some sort of todo list then when you say completed it will be like a devlog trace.

There must be some other extension that already does it. Or I misunderstand the feature.

Actually I started working on the memory watch point. It will be done on for winuae only (the code is already implemented in the emulator). I think it's an important feature to help debugging.

[phaze101]

@prb28 yes there is and not so important. I mentioned it because it came to my head and thought it might be better.

Anyway looking forward to the new feature.

[prb28]

Version released, this discussion is locked. Please use the dedicated discussion for the next version.