Author Topic: Testing RichEditBib (Highlight Syntax Richedit) (Read 9251 times)

HSE · « **Reply #15 on:** May 30, 2021, 07:38:41 AM »

Hi all!

Corrected Iczelion tut 35 mistake.

Also can open files to see better the effect.

Updated in first post.

Regards, HSE

Biterider · « **Reply #16 on:** May 30, 2021, 02:22:01 PM »

Hi HSE
Compiles right out of the box and runs perfectly

Biterider

jj2007 · « **Reply #17 on:** May 30, 2021, 06:52:06 PM »

TestRichBib.rc(13) : fatal error RC1015: cannot open include file 'VER\Version.rc'.
TestRichBib.rc(14) : fatal error RC1015: cannot open include file 'MFT\Manifest_Invoker.rc'.
TestRichBib.rc (20): error RC2135 : file not found: ICO\OA.ico
TestRichBib.rc (24): error RC2135 : file not found: BMP\WndBkgnd.bmp

HSE · « **Reply #18 on:** May 31, 2021, 04:27:01 AM »

Quote from: Biterider on May 30, 2021, 02:22:01 PM

Compiles right out of the box and runs perfectly

Fantastic. Thanks

Quote from: jj2007 on May 30, 2021, 06:52:06 PM

TestRichBib.rc(13) : fatal error RC1015: cannot open include file 'VER\Version.rc'.
TestRichBib.rc(14) : fatal error RC1015: cannot open include file 'MFT\Manifest_Invoker.rc'.
TestRichBib.rc (20): error RC2135 : file not found: ICO\OA.ico
TestRichBib.rc (24): error RC2135 : file not found: BMP\WndBkgnd.bmp

Yes, you have to use make.cmd for the easy way. Other way you must provide to RC the include path to ObjAsm\Resources.

jj2007 · « **Reply #19 on:** May 31, 2021, 06:29:28 AM »

Quote from: HSE on May 31, 2021, 04:27:01 AM

Yes, you have to use make.cmd for the easy way. Other way you must provide to RC the include path to ObjAsm\Resources.

C:\Masm32\Members\HSE\TestRichBib>make.cmd
Impossibile trovare il percorso specificato.

So I looked into the issue...:

Code: [Select]

C:\Masm32\Members\HSE\TestRichBib>set objasm_path=C:\ObjAsm

C:\Masm32\Members\HSE\TestRichBib>make
Building TestRichBib project ...

User Interface: WINDOW
Binary Format:  EXE
Bitness:        64
OOP support:    ENABLED
String Type:    ANSI
Mode:           RELEASE

BuildInfo is processing TestRichBib_Shared.inc ...
Inc2RC is converting TestRichBib_Shared.inc ...
Compiling TestRichBib.rc resources ...
Impossibile trovare il percorso specificato.

***************************
********** ERROR **********
***************************

HSE · « **Reply #20 on:** May 31, 2021, 06:59:36 AM »

Quote from: jj2007 on May 31, 2021, 06:29:28 AM

Impossibile trovare il percorso specificato.

Have you tested:

Code: [Select]

RC /i D:\ObjAsm\Resources testrichbib.rc
What version you have (release or GitHub)?

jj2007 · « **Reply #21 on:** May 31, 2021, 07:23:04 AM »

Quote from: HSE on May 31, 2021, 06:59:36 AM

Have you tested:
Code: [Select]
RC /i D:\ObjAsm\Resources testrichbib.rc

Code: [Select]

C:\Masm32\Members\HSE\TestRichBib>\Masm32\bin\RC /i C:\ObjAsm\Resources testrichbib.rc
testrichbib.rc(14) : fatal error RC1015: cannot open include file 'MFT\Manifest_Invoker.rc'.

Quote

What version you have (release or GitHub)?

No idea. Are their two versions, and if yes, why?

HSE · « **Reply #22 on:** May 31, 2021, 07:56:58 AM »

Quote from: jj2007 on May 31, 2021, 07:23:04 AM

No idea.

Interesting. Perhaps a history file with version number is missing. In Object.inc you can see version.

Quote from: jj2007 on May 31, 2021, 07:23:04 AM

Are their two versions, and if yes, why?

I think there are C.1.0 to C.1.2 releases, and GitHub C1.3 in development version.

If you don't have 'MFT\Manifest_Invoker.rc', perhaps is an older version.

Biterider · « **Reply #23 on:** June 01, 2021, 12:47:35 AM »

Hi
I maintain 2 versions, one is the official stable version (C.1.0) from the ObjAsm homepage and the dev version from Github.
The last one contains files that will not be shared publicly and files that have been contributed and not fully tested.
There are obvious differences between them, but at the moment I don't plan an official release in the coming weeks.

Biterider

HSE · « **Reply #24 on:** June 01, 2021, 01:20:37 AM »

Hi Biterider!

Quote from: Biterider on June 01, 2021, 12:47:35 AM

I maintain 2 versions, one is the official stable version (C.1.0) from the ObjAsm homepage and the dev version from Github.

I don't have a clue what I'm using like stable version in this machine, how you know version?

HSE.

Biterider · « **Reply #25 on:** June 01, 2021, 01:35:49 AM »

Hi HSE
If you have installed ObjAsm with the WebInstaller, you have at least C.1.0 as a base. If you've added or updated files from the repository, or added your own, then you've got something in between. Only with a fresh installation can you say with absolute certainty that I have version x.x.x.
The next version step using the installer will be C.2.0.
For each version I have marked the "created" and the "modified" attributes of all files of the release distribution so far. For version C.1.0 I used 11/01/2017 00:00 UTC. That way, if these dates are unchanged, then you haven't changed the file.

Biterider

HSE · « **Reply #26 on:** June 01, 2021, 01:43:24 AM »

Quote from: Biterider on June 01, 2021, 01:35:49 AM

Only with a fresh installation can you say with absolute certainty that I have version x.x.x.

I suspected that

Thanks.

HSE · « **Reply #27 on:** June 01, 2021, 11:38:52 PM »

Now I remember a detail!!

In 64 bits I'm using UASM 2.49 because a later version apparently is not fully compatible with code.

Regards.

Biterider · « **Reply #28 on:** June 02, 2021, 02:28:07 AM »

Hi
For each new version of UASM I recompile most of the code base and try to check the functionality of the binaries.
I keep some older version of UASM to check for new "features", but currently I'm using version 2.52 and all seems to be perfectly fine.

Biterider

HSE · « **Reply #29 on:** June 02, 2021, 07:55:57 AM »

Quote from: Biterider on June 02, 2021, 02:28:07 AM

currently I'm using version 2.52

Perhaps JJ have same problem I have with UASM version 2.51.

The MASM Forum

News: