Author Topic: Assembly code editor  (Read 5422 times)

0 Members and 1 Guest are viewing this topic.

Offline Leeroy

  • Newbie
  • Posts: 4
    • View Profile
Assembly code editor
« on: August 07, 2018, 07:04:54 am »
G'day All

A few weeks ago i was posting in the general discussion section, looking for some help with a GUI library for this project.
Original post here..  https://www.qb64.org/forum/index.php?topic=318.0
Anyway i didn't end up finding much in the way of a suitable GUI Library, so just wrote as much as i needed for this project. 
It all came about from needing a simple way of creating Assembly code for my home brew bread board computer..
Here's a short video of it computing the time tables up to 12.
http://www.youtube.com/watch?v=9FdBGrspunw
I've attached the .bas file as well as the times tables assembly program file as a sample..
It seems to work well on my laptop and PC but i'd be interested to hear if anyone experiences any bugs or glitches..
This is just a hobby project so feel free to use any of the code if you like..

Cheers
Lee



* assembler.bas (Filesize: 149.62 KB, Downloads: 227)
* times_tables.asm (Filesize: 212 KB, Downloads: 223)
« Last Edit: August 07, 2018, 07:53:17 am by Leeroy »

FellippeHeitor

  • Guest
Re: Assembly code editor
« Reply #1 on: August 07, 2018, 07:56:43 am »
Looking good!

Offline bplus

  • Global Moderator
  • Forum Resident
  • Posts: 8053
  • b = b + ...
    • View Profile
Re: Assembly code editor
« Reply #2 on: August 07, 2018, 09:05:23 am »
Hi Leeroy,

Very interesting project! I don't know assembler but this has me hankering again but I don't think I want to get THAT Basic.

Anyway, your file management tools are interesting. I navigated my system and liked how they worked though a problem with long Path names.

Do you come from a land where they spell cancel, cancell?

Really nice app!

FellippeHeitor

  • Guest
Re: Assembly code editor
« Reply #3 on: August 07, 2018, 09:25:02 am »
I didn't get to browse files as an Out of Memory error occurred when I clicked on Open.

Offline Leeroy

  • Newbie
  • Posts: 4
    • View Profile
Re: Assembly code editor
« Reply #4 on: August 07, 2018, 05:41:57 pm »
Hi Leeroy,

Very interesting project! I don't know assembler but this has me hankering again but I don't think I want to get THAT Basic.

Anyway, your file management tools are interesting. I navigated my system and liked how they worked though a problem with long Path names.

Do you come from a land where they spell cancel, cancell?

Really nice app!

Hi Bplus

Thanks for the feedback.. I did know about the long fie names issues. It also seems to have trouble with files with spaces in them ie "test file.asm".
For some reason when i use the code

Code: QB64: [Select]
  1.     pathfile$ = _CWD$ + "\" + currentfile + ".asm"
  2.     shell$ = "DIR " + pathfile$ + " /b > MYTEST.TXT"
  3.     OPEN "MYTEST.TXT" FOR APPEND AS #20
  4.     l = LOF(20)
  5.     CLOSE #20
  6.     IF l = 0 THEN ' file does not exist
  7.    
  8.  

If the string variable "currentfile" has spaces in it, the MYTEST.TXT file returned by DOS is always empty, even if the file actually exists. 
I don't know why this happens..

The spelling of "cancel" is of course a typo i didn't notice which just got copied and pasted through the program..  :-)
My logical brain has always had trouble with spelling of the English language!
Perhaps QB64 needs a spellchecker? lol.. 

I didn't get to browse files as an Out of Memory error occurred when I clicked on Open.

Fellippe

I get the out of memory error too if i run the exe from my network storage drive.  I have not had a chance to investigate why this happens. 
No errors occur if it's run from a local disk though.
I'll look into it when i get some time..

Cheers
Lee




Offline bplus

  • Global Moderator
  • Forum Resident
  • Posts: 8053
  • b = b + ...
    • View Profile
Re: Assembly code editor
« Reply #5 on: August 07, 2018, 09:12:58 pm »
Seems to me I remember an old trick of enclosing Pathname$ in quotes if it has a space in it.

eg  ... + chr$(34) + pathname$ + chr$(34) + ...

maybe that was for something else?