News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

RadASM 3.0 bugtest

Started by KetilO, May 31, 2010, 12:28:11 PM

Previous topic - Next topic

remus2k

#255
Hi

I missing a fuction in radasm3

I have in the Resource browser 3 dialog ,now need i by right click on a dialog
in resource browser "remove from project"

Radasm 2 have it !!
by Radasm3 must i switch to the Menübar > Resource> Remove select





Thanks

Shooter

I don't know if this is a bug, or if I'm doing something wrong. I created a new MASM project with no files, and then manually added the .asm and .rc files accordingly, and finally, removed the existing paths of the .inc and .lib listed in the .asm file. It compiles, but without the .rc file.

Also, when I attempt to edit the path of an included header file listed in the .rc, RadASM's title bar flashes inactive for a brief moment, then active again, but nothing else happens (see screenshot below with red box). I checked the Make Options to ensure the RC strings are correct, and they seem to be just fine, but it's just not compiling with the resource file.



Here is the project I'm trying to 'import'.

Am I doing something wrong?

-Shooter
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

donkey

To force the RC file to compile during a build do the following

Open the RC file
Select Make:>Toggle Current as Main File
Open the main assembly file
Select Make:>Toggle Current as Main File
"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

Shooter

Quote from: donkey on January 11, 2011, 05:42:12 PM
To force the RC file to compile during a build do the following

Open the RC file
Select Make:>Toggle Current as Main File
Open the main assembly file
Select Make:>Toggle Current as Main File

Thanks.

That worked to getting it to compile, but now I receive the error,
Quotersrc.rc(1) : fatal error RC1015: cannot open include file 'include'.
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

dedndave

that is a resource compiler error
i take it you are trying to include resource.h
Quote#include "\masm32\include\resource.h"
in a resource file, the filename must be surrounded by double quotes

Shooter

Quote from: dedndave on January 11, 2011, 06:20:31 PM
that is a resource compiler error
i take it you are trying to include resource.h
Quote#include "\masm32\include\resource.h"
in a resource file, the filename must be surrounded by double quotes

That's the problem... I can't get in to edit the path that's already in the resource file.
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

dedndave

.RC files are text files
you can open or even associate them with Notepad, if you like
i am sure RadAsm gives you some way to edit them directly

Shooter

Quote from: dedndave on January 12, 2011, 12:13:33 AM
.RC files are text files
you can open or even associate them with Notepad, if you like
i am sure RadAsm gives you some way to edit them directly

Actually, I got around it by deleting the entry and re-adding it. Not sure why I couldn't get RadASM to let me edit the existing entry.
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

Gunner

Quote from: Shooter on January 12, 2011, 02:15:59 AM
Not sure why I couldn't get RadASM to let me edit the existing entry.

Well, for starters... AFAIK, RadASM 3 is BETA!! It is a complete rewrite so there are many bugs to be found!  :toothy
~Rob (Gunner)
- IE Zone Editor
- Gunners File Type Editor
http://www.gunnerinc.com

Shooter

Quote from: Gunner on January 12, 2011, 02:37:39 AM
Well, for starters... AFAIK, RadASM 3 is BETA!! It is a complete rewrite so there are many bugs to be found!  :toothy

Hence my question, if it was a bug or misuse.  :wink
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

KetilO

Hi Shooter

Yes, there is a bug and it will be fixed.

Be aware that the resource compiler converts strings (\r=CR=0Dh, \n=LF=0Ah.\0=0=00h and so on). Avoid using \.
These will all work:
#include <resource.h>
#include "\\masm32\\include\\resource.h"
#include "/masm32/include/resource.h" (RadASM's resource editor uses this one)

You dont need to edit the rc file in text mode. Just double click on filename and type in the new name.

KetilO

Shooter

Quote from: KetilO on January 12, 2011, 08:22:00 AM
Be aware that the resource compiler converts strings (\r=CR=0Dh, \n=LF=0Ah.\0=0=00h and so on). Avoid using \.
These will all work:
#include <resource.h>
#include "\\masm32\\include\\resource.h"
#include "/masm32/include/resource.h" (RadASM's resource editor uses this one)

Question about the paths when dealing with this... using the image above as an example, does the path in the image override the existing $A path setting or include it?

-Shooter
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.

donkey

Quote from: Shooter on January 12, 2011, 11:14:45 PM
Question about the paths when dealing with this... using the image above as an example, does the path in the image override the existing $A path setting or include it?

The path is hard coded, $A is not used.
"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable

cntrump

Quote from: KetilO on May 31, 2010, 12:28:11 PM
RadASM 3.0 is a complete rewrite of RadASM. Some new features and many improvements.
RadASM 3.0 is in no way compatible with older versions of RadASM.
Ini files, project files, api files and addins are all incompatible.

Supported assemblers:
-------------------------------
Masm, GoAsm, Fasm and Tasm

Supported high level languages:
-------------------------------------------
VC6 C/C++, BCC 5.5 C/C++

WARNING!
Do NOT install RadASM 3.0 in the same directory as an older version of RadASM.

Get it here:
https://fbedit.svn.sourceforge.net/svnroot/fbedit/RadASM30/Release/RadASM.zip

KetilO
radasm is the best asm ide!
I hope radasm 3.0 can create a makefile for project. :lol

Shooter

Quote from: donkey on January 12, 2011, 11:35:15 PM
The path is hard coded, $A is not used.

Long pathnames including root drive are required? (I haven't tried a referenced pathname yet. i.e. "\masm32\include\resource.h")
Never use direct references to anything ever. Bury everything in
macros. Bury the macros in include files. Reference those include
files indirectly from other include files. Use macros to reference
those include files.