Assembled file isn't loaded ...

[BacchusFLT]

One want that pressing F7, the project should assemble, launch VICE and load the recently assembled file. However introducing segments, this doesn't work.

When I assemble the below WITH the ".segment" row, address 1000 has the labels
in the monitor, but not the actual code. The binary was clearly never loaded. Commenting out the .segment it's loaded as normal.

	.segment MyCode[]

	*=$1000
start:	inc $d020
	jmp start

[Swoffa]

Thanks for reporting, will look into it.

[Swoffa]

@BacchusFLT
My suggested solution is to put annotations in the file being built, something like this:

// @kickass-build: {"file-to-run": "file.prg", "disk-to-run": "disk.d64"} 
	.segment MyCode[]

	*=$1000
start:	inc $d020
	jmp start

The file-to-run-annotation sets which prg-file to run in vice (or C64Debugger) and the disk-to-run-annotation sets which d64 to load into Vice. If disk-to-run is set, file-to-run is loaded from that disk, otherwise from the file system.

Would this solution give you what you need?

[BacchusFLT]

I wasn't aware of this option. Thx! /Pontus Berg Bergatrollet AB CEO & Owner Tel/SMS: +46 735 082860 Skype: BacchusBerg Hangout: pontus.bergatrollet@gmail.com www.bergatrollet.se Den mån 10 dec. 2018 kl 09:03 skrev Simon Oskarsson < notifications@github.com>:

…

@BacchusFLT <https://github.com/BacchusFLT> My suggested solution is to put annotations in the file being built, something like thins: // @kickass-build: {"file-to-run": "file.prg", "disk-to-run": "disk.d64"} .segment MyCode[] *=$1000 start: inc $d020 jmp start The file-to-run-annotation sets which prg-file to run in vice (or C64Debugger) and the disk-to-run-annotation sets which d64 to load into Vice. If disk-to-run is set, file-to-run is loaded from that disk, otherwise from the file system. Would this solution give you what you need? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AbNsyqIAgC-n6LIOU-OJM5_RSGDQuHvXks5u3hVYgaJpZM4X_K64> .

[Swoffa]

I wasn't aware of this option. Thx! /Pontus Berg

@BacchusFLT
No, no, it is not implemented yet! It is my suggestion, but I wanted to ensure it actually helps you before I implement it. From your answer I guess its "thumbs up". :)

[BacchusFLT]

Yes I guess it would. /Pontus Berg Bergatrollet AB CEO & Owner Tel/SMS: +46 735 082860 Skype: BacchusBerg Hangout: pontus.bergatrollet@gmail.com www.bergatrollet.se Den mån 10 dec. 2018 kl 11:29 skrev Simon Oskarsson < notifications@github.com>:

…

I wasn't aware of this option. Thx! /Pontus Berg @BacchusFLT <https://github.com/BacchusFLT> No, no, it is not implemented yet! It is my suggestion, but I wanted to ensure it actually helps you before I implement it. From your answer I guess its "thumbs up". :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AbNsypDf_xllMWAqPiM7NHhi4Nkn5p7Lks5u3jeDgaJpZM4X_K64> .

[Swoffa]

Fixed in PR #50. Will be in release 1.3.1.

[Swoffa]

Version 1.3.1 available thru Package control now