Oxygen Basic

Programming => Example Code => User Interface => Topic started by: Aurel on April 02, 2017, 05:43:12 AM

Title: Aurel Edit
Post by: Aurel on April 02, 2017, 05:43:12 AM

I
.

Title: Re: Aurel Edit
Post by: Arnold on April 05, 2017, 07:11:22 AM

Hi Aurel,

although I will concentrate on my little project, maybe I can make some proposals for your project? Of course this is only my point of view.
I created two folders for my project: project_dev and project. Folder project_dev is my sandbox, the folder project will contain the files which I will deliver.

As long as I do modifications with my code I do not use the #include "$\inc\RTL32.inc" statement. With my editor (PSPad, but Scite or Oxide will work too) it is really easy to run the code and see the bugs at once. And when I then create an executable I will see what is still missing.

E.g. when running AurelEdit.o2bas without the runtime library then SciLexer.dll is not necessary in the working folder as Oxygenbasic will find it. I also make sure that there is no other SciLexer.dll is opened. This can be checked in a Dos Box (cmd.exe) with this command:

where scilexer.dll

Running AurelEdit as an executable is another problem. But for developing the code you will not need an extra scilexer.dll.
I copied AurelEdit.o2bas and awinh.inc into a folder AurelEdit and tried to restore the missing images (not sure if I got the right ones). I would like to suggest to add a routine like this for missing images:

Code: OxygenBasic

1. sub missing(sys id, string name)
2.    if not id then mbox name " not found"
3. end sub
4.  
5. '--------------------------------------
6. 'loadbmp
7. '##################################################
8. INT bmpB0,bmpB1,bmpB2,bmpB3,bmpB4,bmpB5,bmpB6,bmpB7,bmpB8
9. bmpB0 = LoadImage(0,"bPanel.bmp",0,80,24,16) : missing(bmpB0, "bPanel.bmp")
10. bmpB1 = LoadImage(0,"data/rcImg.bmp",0,400,300,16) : missing(bmpB1, "data/rcImg.bmp")
11. '......................................................
12. bmpB2 = LoadImage(0,"data/guiApp.bmp",0,24,24,16) : missing(bmpB2, "data/guiApp.bmp")
13. bmpB3 = LoadImage(0,"data/consoleApp.bmp",0,24,24,16) : missing(bmpB3, "data/consoleApp.bmp")
14. bmpB4 = LoadImage(0,"data/btCut.bmp",0,30,30,16) : missing(bmpB4, "data/btCut.bmp")
15. bmpB5 = LoadImage(0,"data/btCopy.bmp",0,30,30,16) : missing(bmpB5, "data/btCopy.bmp")
16. bmpB6 = LoadImage(0,"data/btPaste.bmp",0,30,30,16) : missing(bmpB6, "data/btPaste.bmp")
17. bmpB7 = LoadImage(0,"data/btCompile.bmp",0,30,30,16) : missing(bmpB7, "data/btCompile.bmp")
18. bmpB8 = LoadImage(0,"data/btRun.bmp",0,30,30,16) : missing(bmpB8, "data/btRun.bmp")
19. '##################################################
20.  
21. and in about line 234:
22.  
23.   hImage = LoadImage(0, "rCodetb.bmp", 0, 280, 20, 24) : missing(hImage, "rCodetb.bmp")
24.  

Do you need some images at all like btCut.bmp, btCopy.bmp etc. They could be integrated with your rcImg.bmp.

You definitively should add a menu to the application. It is not so comfortably easy as with a resource file (which you do not like) but it is possible. A menu will give you much more flexibility than only using a toolbar.

I would also leave the edit fields of the find/replace dialog blank and add labels in front of them e.g. something like this:

Code: OxygenBasic

1. 'create single-line edit control
2. % SS_LEFT=0
3. % WS_GROUP=0x00020000
4. label_1= SetStatic(fWindow, 80,32,60,25,"Enter word:",WS_VISIBLE | WS_CHILD | WS_GROUP | SS_LEFT,0,-1)
5. fwed1 = SetEditBox(fWindow,  150,30,200,23,"",0x50004000,0x200,fwed1ID)
6.  

This is all for now. There are already good starting points in your project and hopefully you will continue with it. This would also extend your awinh.inc.

Roland

Title: Re: Aurel Edit
Post by: Aurel on April 05, 2017, 10:50:52 AM

Hs.

Title: Re: Aurel Edit
Post by: Aurel on April 06, 2017, 02:29:26 AM

T

Title: Re: Aurel Edit
Post by: Aurel on April 06, 2017, 05:32:04 AM

H

Title: Re: Aurel Edit
Post by: Arnold on April 07, 2017, 05:26:19 AM

Hi Aurel,

I was fighting with Scintilla's regex yesterday and lost the first round of the match miserably. But the battle is not yet over.

Maybe I can suggest two small modifications of your code:
I would at least add the extended style WS_TOOLWINDOW | WS_EX_TOPMOST for the fWindow control, I always had to search the find window when I pointed to the text of Scintilla.
For debugging the code I use a very simple but very effective tool:
#include "$/inc/console.inc"

I use printl statements for the console window. If I later comment out the include statement I will easily find the printl statements.
For messages of the application I use mbox (or with awinh.inc I can use MSGBOX)
This way I can follow all kinds of values, variables, controls, messages etc very easily. And when the app crashes I can simply close it by closing the console window. BTW if I close the app and the console window does not close, then something is wrong with my app as gxo2.exe / co2.exe do not release memory and I have to kill them with the task manager. So the console acts as a simple debugging tool for me and has many advantages.

I did this approach for the (print) messages which you added for the find replace dialog. Then I loaded a little test file, entered 'if' and 'uf' in the edit fields and pressed the Replace Button until I got the 'OK' message. Then I set the cursor to the top of the text again and tried to find 'if' again. There are finds, so something is missing. If I try other combinations of using the buttons, something is also missing.

This is not the solution of the problem (I did not explore the code), but I am convinced that the console would help you to find many such critical places very fast. Try it yourself.

Roland


.

Title: Re: Aurel Edit
Post by: Aurel on April 07, 2017, 10:08:08 AM

Y

Title: Re: Aurel Edit
Post by: JRS on April 07, 2017, 01:10:46 PM

Roland,

It might be worth prototyping your IDE using IUP first and if you still want to dabble with the Windows API and styles, use a Spy like utility to see how IUP did it.

Title: Re: Aurel Edit
Post by: Aurel on April 09, 2017, 12:55:10 AM

H

Title: Re: Aurel Edit
Post by: Aurel on April 09, 2017, 05:14:24 AM

H

Title: Re: Aurel Edit
Post by: Aurel on April 09, 2017, 07:06:03 AM

H

Title: Re: Aurel Edit
Post by: Aurel on April 09, 2017, 09:48:47 AM

H

Title: Re: Aurel Edit
Post by: Charles Pegge on April 10, 2017, 08:27:28 AM

Hi Aurel, I'm using VBasic lexing:

Code: [Select]

     '3  cpp
     '8  vb ***
     '40 lout
     '51 powerbasic
     '75 freebasic
      sm SCI_SETLEXER, 8, 0
      include "oxykeywords.inc"
      sm SCI_SETKEYWORDS, 0, strptr OxyKeywords
      sm SCI_COLOURISE, 0, -1


Title: Re: Aurel Edit
Post by: Aurel on April 10, 2017, 11:41:12 AM

sm SCI_SETKEYWORDS, 0, strptr OxyKeywords
      sm SCI_COLOURISE, 0, -1

ahh i see you use  SCI_COLOURISE,
i dont us it in my version but u will try  :)

Title: Re: Aurel Edit
Post by: Aurel on April 11, 2017, 08:57:09 AM

Hi Charles
I have tried your way but nothing .
I only get string and comment colored ..what a heck is with this version >:(

Ok .Charles
Do you can show me where is this all code for scintilla placed ?
In OxIde or somewhere else?
thnx

Title: Re: Aurel Edit
Post by: Aurel on April 12, 2017, 10:43:47 AM

Charles
I look again into your OxIde
and found that you load scilexer.dll under WM_CREATE message.
When i tried to create anything under WM_CREATE then i get nothing  :o
It looks that Window not respond on WM_CREATE ..how is that possible ?

Title: Re: Aurel Edit
Post by: Aurel on April 12, 2017, 11:13:41 AM

I always forget to tell you that in any of my programs written in Oxygen
nothing work under WM_CREATE what is really ..really strange  :o
All other windows messages work proper...which is really crazy ???
so i will post... let say -test version which work with scilexer 2.2.0.0 - VB lexer/8
hmm this lexer it looks that not support commentBlock inside /*....*/ ..right?
other things seems to work..hmmm
this version use your code to load & create scintilla control in main window but
( of course i can reformat code into my coding style but this is quick addition) :D
outside of WM_CREATE ...so you may try.

Title: Re: Aurel Edit
Post by: Aurel on April 26, 2017, 10:07:54 PM

with dark theme
anyone know for good color scheme?

.

Title: Re: Aurel Edit
Post by: Aurel on May 19, 2017, 03:26:08 PM

..now i add selection color- dark back/light fore color

SendMessage hsci,SCI_SetSelBack,1, RGB(49, 106, 197)
SendMessage hsci,SCI_SetSelFore,1, RGB(255, 235, 225)

.

Title: Re: Aurel Edit
Post by: EricE on July 13, 2017, 09:47:52 AM

AurelEdit.o2bas will compile without errors using OxygenBasic A042, but will not when using version A043.

When compiling with A043, the following error message appears:

Quote

O2H
;ASM ERR: edi[ebx+440] = ._direct_!! Unidentified instructions edi
;AFTER:   ._direct_
;LINE:    588

How can this be debugged and fixed?

Title: Re: Aurel Edit
Post by: Charles Pegge on July 21, 2017, 12:41:50 AM

Hi EricE, welcome to the forum.

I have one here which works on my latest OxygenBasic A43.

Perhaps Aurel can post his latest developments.

.

Title: Re: Aurel Edit
Post by: EricE on July 23, 2017, 07:44:35 AM

Thank you Charles for the welcome, and for the new code.

Regarding this A043 version of AurelEdit, I have verified it compiles and runs using A043 on Windows 10.
 
I have this question though, what version of SciLexer should be used with it? (v2.2.0, v3.7.5, or some other version?)   

Title: Re: Aurel Edit
Post by: Charles Pegge on July 27, 2017, 01:52:16 AM

Hi Eric,

Roland prepared a SciLexer for OxygenBasic, based on version 3.7.4 (600k) with some limitations on Regular Expressions. We know it is up to date and a clean build. You are welcome to adopt it.

What puzzles me, however, is why it is larger than oxygen.dll  :o

Title: Re: Aurel Edit
Post by: Aurel on July 27, 2017, 10:25:19 AM

Quote

What puzzles me, however, is why it is larger than oxygen.dll

hi
what is strange to me that he said that in original i use custom version of 1.6.8.0
but i am not sure about that, there are many custom lexers added to sciLexer that is hard to find
which one to use .
i think that i use 2.2.0,0 and with each new version dll grows a lot ,probably because of addition of
new lexers inside dll.
There is also difference between versions..hmmm

Title: Re: Aurel Edit
Post by: Aurel on August 21, 2017, 01:48:09 PM

hi
some changes and cleaning( awinh is now called awinh035 )
some bindings removed,PW functions removed
work with scilexer: 1.6.7.0 also tested with 3.6.1.0
compiled with o2 - A041

.

Title: Re: Aurel Edit
Post by: Charles Pegge on August 24, 2017, 07:54:49 AM

Hi Aurel,

It works nicely with my latest A043, squashed to 140k as it is,  in its present form :)

But I have some more work to do before releasing this version of o2.

Title: Re: Aurel Edit
Post by: Aurel on August 27, 2017, 02:26:47 AM

Hi Charles
OK im glad that compile with 043  :)
But i found that 041 is very stable version and work very well for me
so for now i wont change anything ..
as i say before awinh need more cleaning that anyone can use gui function without
problem..
 ;)

Title: Re: Aurel Edit
Post by: Charles Pegge on August 27, 2017, 09:51:51 PM

I hope that A43 will be the last of the alphas, and we can move to a more stable beta phase. I will stop churning the code with major alterations and new features.

Title: Re: Aurel Edit
Post by: Aurel on August 28, 2017, 09:45:32 AM

I'm glad to hear that Charles
especially on part without core changes( with well known troubles )
 :)

Title: Re: Aurel Edit
Post by: Aurel on February 25, 2018, 11:56:58 AM

Hello Boys !  :)
I was just fixed one small bug in AurelEdit with FindNext() function from
toolwindow Find/Replace/ReplaceAll..
I hope that will work for you .

ps.I also add zip with compiled exe+gxo2+oxygen.dll I use A041
treeview example included so you may recompile and try
 awinh.inc and awinh035
 -->>> scanned with Kaspersky AV
but you may check with your AV.

[attachment deleted by admin]

Title: Re: Aurel Edit
Post by: Arnold on March 22, 2018, 08:22:47 AM

Hi Aurel,

as you asked about awinh35.inc, I downloaded your project and it runs ok with me, if I comment out: include RTL32.inc in AurelEdit.o2bas. I did not use the exe file. I also replaced gxo2.dll, oxygen.dll,Scilexer.dll with the files of Oygen Beta and removed RTL32.inc from the folder.

I did not test much. "Web Site" and "add compiler Path" seem not to be integrated? Find does not work correctly, it does only find whole words. Save seems not to work if I enter a different filename. Running a compiled file does not work: missing oxygen.dll (because oxygen.cfg is missing)

I can only tell you what I would do and have done. I removed gxo2.exe, oxygen.dll, RTL32.inc, SciLexer.dll from the folder. They are really not necessary. And if someone would compile a program he / she will need a path to Oxygen's include files anyway.

At the beginning of AurelEdit.o2bas I inserted:
$ Filename "AurelEdit.exe"
'Include "RTL32.inc"
use corewin
Include "awinh035.inc"
...

For developing I modified the line 147:
string gxName="\gxo2.exe"   ' for oxygen change path to \gxo2.exe
to:
string gxName="c:\oxygenbasic\gxo2.exe"   ' for oxygen change path to \gxo2.exe
and the line 887:
sRet = ShellExecute(0,"open",cdPath,"-c" + fName,"" , 5) ' if work sRet = 42
to:
sRet = ShellExecute(0,"open",gxName,"-c" + fName,"" , 5) ' if work sRet = 42

Then in awinh035.inc I commented out line 579-699

...
#lookahead
/*
Dim kernel32,user32,gdi32,riched32,comdialog32,comctl32
...
Declare Function ImageList_AddMasked Lib "comctl32.dll" (byval hImageList as sys,byval hBitmap as sys,byval crMask as sys) as sys
'-----------------------------------------------------------------------------------------------------------
*/
...

After saving Aureledit.o2bas and awinh035.inc I ran AurelEdit.

Following the error messages, I modified in AurelEdit:
Line 150: GetCurrentDirectory
and in awinh035.inc I added in Line 700:
Declare Function timeGetTime   Lib "winmm.dll" () As Long

I now have at least a running AurelEdit.o2bas. It does not work correctly, because for using the unprotyped WinApi functions most probably some parameters must be applied differently, e.g. after compiling a loaded file and running the compiled exe (with error message) the tabs will disapear.

But before examining the subs and functions I would first check which structures and constants I will not need, because they are already included in WinData.inc. Then I would go into the details.

But as I stated, this is only what I would do (trial and error).

Roland

Title: Re: Aurel Edit
Post by: Aurel on March 22, 2018, 09:22:59 AM

First
thank you Arnold for try ...
... and you probably figured what kind of troubles I have when i try to compile
and run AurelEdit on progress_o2 version
for example #lookahead works different in progress version than in old A041
that also complicate things and some stuff ...

It looks that  constants with &H not respond like before
My problem with toolbar control is because i use ImageList and I figured that
also i must modify toolbar style too.

all in all
thanks   :)
 

Title: Re: Aurel Edit
Post by: Charles Pegge on March 22, 2018, 09:30:20 AM

Aurel and Roland,

I now have the skeleton Menu/Toolbar Test working 64bit, using corewin, and ensuring all handles are sys

I've put in a few annotations.

Title: Re: Aurel Edit
Post by: Aurel on March 22, 2018, 10:28:51 AM

Hi Charles and Roland/Arnold
Thank you !

So main problem is with this stupid structure  TBBUTTON
everything else seems to me same - as i see ?
i suspect that something is wrong with that  ::) !"#$%&/((#$%%  >:(
I am wondering how then work with old way-  is a mistery ...
ok i can continue...
 :)

tnx
Aurel

Title: Re: Aurel Edit
Post by: chrisc on March 22, 2018, 10:43:14 AM

very beautiful menu

it would be nice to have tooltips and the button working as well

Title: Re: Aurel Edit
Post by: Arnold on March 22, 2018, 11:15:21 AM

Yes Charles,

this is exactly the way I would suggest to Aurel. Your example can be used in JIT mode and created as a 32-bit or 64-bit executable. Perhaps Aurel can be convinced too. If he gets rid of the unnecessary constants and types, he will get a better overview of what is missing or does not work.

Roland

Title: Re: Aurel Edit
Post by: Aurel on March 22, 2018, 12:11:03 PM

hi chrisc
tooltips work in Charles example just keep mouse pointer over toolbar button.

Arnold
Yeah maybe this is the way to avoid all problems .
I try to use Charles example but with api declaration with changes he made
and i get again nothing ..
so somewhere types are strict and somewhere are not...
I will try to compile AurelEdit with CoreWin.inc that is not problem
but i suspect that would work like in with old version scintilla not respond very well to.  ::)

Title: Re: Aurel Edit
Post by: chrisc on March 22, 2018, 04:41:49 PM

Hello Aurel

i have placed the mouse over the toolbar but there isn't any tooltips?

Title: Re: Aurel Edit
Post by: Charles Pegge on March 22, 2018, 07:22:28 PM

A few more INT to sys, and the tooltips are now working 64bit.

Title: Re: Aurel Edit
Post by: Aurel on March 22, 2018, 10:50:37 PM

Quote

A few more INT to sys

Charles
Is that general problem?
I see that  - when i replace INT with SYS in Function Declaration
o2 throw error  - linker found unidentified name
I mean why is this time too strict?
In another word why we dont have ERROR TYPE  -> ERROR -> VARIABLE WRONG TYPE ! at LINE

Title: Re: Aurel Edit
Post by: Charles Pegge on March 23, 2018, 02:33:47 AM

Hi Aurel,

That error may be caused by a mismatch between forward-declaration and prototype. In 64bit, int no longer matches sys.

Title: Re: Aurel Edit
Post by: Aurel on March 23, 2018, 04:01:29 AM

Hi Charles
but i use 32bit win7
and also if is not matched sys /int and int/sys
In my programs i prefer to use INT...but i don't have nothing against SYS
if i must i will use sys.

Title: Re: Aurel Edit
Post by: Arnold on March 23, 2018, 04:02:29 AM

This is also something which I forgot to mention. During creating the app I do not use #lookahead. Either I declare the subs/functions at the beginning of the programm or I use the bottom_up way. If everything works correctly then I can use #lookahead also.
From now on I will also use #autodim off, which enforces variable declarations. I think some of my problems in the past arose because I forgot to declare some sensitive variables.

Title: Re: Aurel Edit
Post by: Aurel on March 23, 2018, 04:06:23 AM

Quote

#autodim off

Yes Arnold #lookahead make problems and also it looks that i will start use #autodim off
I always (only when forget   ::)) like first to define all  variables.

Title: Re: Aurel Edit
Post by: Charles Pegge on March 23, 2018, 04:53:07 AM

#lookahead runs through the rest of the script collecting function prototypes, and turning them into declarations. These declarations are then inserted into the script.

If the prototypes contain any types or typedefs defined below #lookahead, the declarations will not be properly processed.

I will see if this situation can be improved

Title: Re: Aurel Edit
Post by: chrisc on March 23, 2018, 06:37:42 AM

i have downloaded the reply #38 code and compiled it
BUT when i run the exe there is still no tooltips. 

 my pc is  Win 10 64bits

Title: Re: Aurel Edit
Post by: Charles Pegge on March 23, 2018, 06:54:25 AM

I've checked the download on #38. I found that the window does not have focus until you click on it somewhere. Then hovering should produce tooltips. That is also the case with the 32bit version.

Title: Re: Aurel Edit
Post by: chrisc on March 23, 2018, 07:05:40 AM

Clicking on it first to produce tooltips ... ok  got it

i think it would be better that to have it automatically display tooltips when mouse hover over
the toolbar?   maybe use setfocus on the toolbar whenever the program is loaded?

Title: Re: Aurel Edit
Post by: Charles Pegge on March 23, 2018, 07:21:21 AM

SetFocus win

Drop it in just above 'message loop

:)

Title: Re: Aurel Edit
Post by: chrisc on March 23, 2018, 09:09:00 AM

Thanxx Charles
it works now

Title: Re: Aurel Edit
Post by: Aurel on March 30, 2018, 01:37:25 PM

In this fixing session of Aurel Edit i stuck little bit with
TOOLWINDOW - FindWindow
In older version i just use :

fWindow = CreateWindowEx ( WS_TOOLWINDOW|WS_EX_TOPMOST,wcx.lpcClassName,"Find/Replace...", 524288 , 600, 160, 412, 300, 0, 0, null, 0)
524288 is just ws_sysmenu
and as result when i click on Find button i get nothing... what?
then i figured that I must use registered CLASS NAME?
and it is "Oxygen"
so now is:
fWindow = CreateWindowEx ( WS_TOOLWINDOW|WS_EX_TOPMOST,"Oxygen","Find/Replace...", 524288 , 600, 160, 412, 300, 0, 0, null, 0)

Title: Re: Aurel Edit
Post by: Aurel on March 31, 2018, 03:53:32 PM

..and more menu item + bitmaps added
,,now I need to add functions for menu items.. ahh

 :)

Title: Re: Aurel Edit
Post by: Aurel on June 10, 2018, 05:43:50 AM

Here is latest code compiled with o2Progress (not last one i think)

Title: Re: Aurel Edit
Post by: matthew on June 11, 2018, 02:51:01 AM

Hi Aurel, I just compiled with the latest version of OxygenBasic. Everything looks good here.

Title: Re: Aurel Edit
Post by: Aurel on June 11, 2018, 07:38:56 AM

Thanks Matthew !

Title: Re: Aurel Edit
Post by: Aurel on January 18, 2019, 10:10:39 AM

Just to let you know if someone ask why WM_CREATE not work
with awinh include created by me.
When i do some testing (learning) some programming in C winapi programs
i figured why WM_CREATE not work with mine include file.
Also i remove from skelton program message loop as separate function called Wait()
and put MessageLoop inside ( something like in C )

Title: Re: Aurel Edit
Post by: Aurel on January 18, 2019, 10:51:28 AM

In attachment is awinh038.inc
EDIT: deleted because of strange problems ..sorry

Title: Re: Aurel Edit
Post by: Aurel on February 04, 2020, 12:32:30 PM

Hello
After some time i finally compiled AurelEdit with last self-compiled o2 version 0.2.8.
In attachment is complete Scintilla.zip so you just must to unpack content into existing folder.
\projectsB\Scintilla
What is new , well some things are fixed, i just started on config file and you can change theme then when you start
editor again your theme would be ON.
This is still just 32bit version but i will create 64bit version too.