EPB (PureBasic Editor )

[dobro]

Big Thanks

[Tenaja]

I think keep the name "deblock"
because in fact you can add keywords

"_block" and "_end_block"

to format this type of line...

Oops, I must have skimmed past that, so I missed your block commands. That does make the most sense if it acts on the _block sections.

[dobro]

Originally, the lines cut by "_"
example:

for i_
1 to_
255

was possible, only in the section

_block
_end_block

I added the possibility to cut the lines even outside _block / END_BLOCK

but the menu was to keep the same name ("Unblock")

In addition, the menu, it appears as
"Unblock (_)"
and
"Unpunch (:)"


lines cut, form a kind of code block ... so. I kept that name ..
if you have an idea to rename ..


In fact, the commands "_block / _end_block"
serve only to create an offset, if necessary

[Tenaja]

lines cut, form a kind of code block ... so. I kept that name ..
if you have an idea to rename ..

This is one of the benefits of having the text in a prefs file; users can edit them at will.

BTW, I noticed a few items were missed:
* Couleur fond des Procedures (And all of the color-picker dialog text.)
* None of the items in the TOOLS menu were converted.
* Search and Replace dialog box.

I updated this a bit, but it seems to have problems:
155 = Writes the parameters and updates EPB.
156 = If you exit using the red X, the parameters are saved,
157 = but you must restart EPB to see any changes.
...if you do not click the Refresh EPB button, nothing is saved. I tested it by changing the font, then hitting the red X. When I reopened, the new font was not applied. The only way I could get it to apply the new font was with Refresh EPB. Even the Save Current Style did not save the new font, if I clicked the Red X. If I reloaded the new syle file, then everything was applied.

I edited my file so instead of Remove Tab, it reads Close Tab, which seems to be more common with English programs.

If you UNDO one too many times, the whole file disappears. (Even with a freshly OPENed file!)

It also seems a bit aggressive with the SAVE when you don't want it to...like when you open a file just to view, then you close it. That made the PB IDE complain of file changes.

[dobro]

Version 1.78 online:)
http://michel.dobro.free.fr/download.php?view.25
(or click the menu "update EPB?")


change many things ..

delete your old, EPB directory before reinstalling this version

new properties:
can be accessed through the menu, to create
*. exe, *. asm, *. DLL, console, *. scr

supports the languages ​​English and German ..


fixed some bugs, and adding functionality (including creating DLL that I completely skipped): roll:

while I think:
To add a tool in EPB, it is sufficient to deposit in the directory "Outils"

lines cut, form a kind of code block ... so. I kept that name ..
if you have an idea to rename ..

This is one of the benefits of having the text in a prefs file; users can edit them at will.

yes

BTW, I noticed a few items were missed:
* Couleur fond des Procedures (And all of the color-picker dialog text.)
* None of the items in the TOOLS menu were converted.
* Search and Replace dialog box.

I updated this a bit, but it seems to have problems:
155 = Writes the parameters and updates EPB.
156 = If you exit using the red X, the parameters are saved,
157 = but you must restart EPB to see any changes.
...if you do not click the Refresh EPB button, nothing is saved. I tested it by changing the font, then hitting the red X. When I reopened, the new font was not applied. The only way I could get it to apply the new font was with Refresh EPB. Even the Save Current Style did not save the new font, if I clicked the Red X. If I reloaded the new syle file, then everything was applied.

I edited my file so instead of Remove Tab, it reads Close Tab, which seems to be more common with English programs.

If you UNDO one too many times, the whole file disappears. (Even with a freshly OPENed file!)

Fixed in v1.78 Thanks

It also seems a bit aggressive with the SAVE when you don't want it to...like when you open a file just to view, then you close it. That made the PB IDE complain of file changes.

only if you write something, or space ...
or paste a code ..normally

[Tenaja]

Version 1.78 online:)
http://michel.dobro.free.fr/download.php?view.25
(or click the menu "update EPB?")

I will try it.

only if you write something, or space ...
or paste a code ..normally

Yes, that is my problem...I opened files just to test the editor, but did not want to change them. When I accidentally hit some keystrokes, then in my PB IDE I have new bugs even though I wanted to close EPB without saving.

[Tenaja]

The UNDO still allows totally deleting the contents of a file when combined with automatic save on exit. I had a scare with that on the last version, and this one still has it.

More translation... the Statusbar text is still in French...

I found out why you have the warning "NEVER run the Algorithm twice in a row!" I ran it, then hit UNDO to see what changed... then ran it a second time. Oops. EPB crashed. never again!

[dobro]

hum !

it will be hot fix .. because I do not really understand the history of UNDO


Epb in principle does not change the original bp ***.
he renames in : "*****_Back. pb"

mode conversion code> 4.60 is an expérimental module

I will look carefully, that, thanks

[Tenaja]

Take a look at this page:
http://www.scintilla.org/ScintillaDoc.html#UndoAndRedo

Specifically, this command:

SCI_EMPTYUNDOBUFFER
This command tells Scintilla to forget any saved undo or redo history. It also sets the save point to the start of the undo buffer, so the document will appear to be unmodified. This does not cause the SCN_SAVEPOINTREACHED notification to be sent to the container.

If I understand it, you issue this command immediately following the file open, and then there will be no more undo possible until you perform an action (i.e. typing or deleting).

By the way, I have seen some editors have an option (checkbox) to cause a Save to clear the undo buffer. While I always turn it off so I can undo "forever," it seems like a feature some people would appreciate.

[dobro]

I was careful what you say

However, I am French, and google translation does not help: lol:

I already use in EPB REDO and UNDO
or by use of, Ctrl + Z, Ctrl + y keyboard

either by the pop up menu (right click)

extract of my code:

Code: Select all

Case  #menu_undo 							
         ScintillaSendMessage(onglet, #SCI_UNDO)

Case  #menu_redo							
         ScintillaSendMessage(onglet, #SCI_REDO)

I will try to understand this function: SCI_EMPTYUNDOBUFFER

to know the problem you had ..
(that is, I did not understand)

Thank you, for your patience and your help

for a French reader of passage, and that is Billingual:
si un français passe par là , j'aimerai bien comprendre quel problème il a rencontré exactement


[Reedit]
ho! you want , I use SCI_EMPTYUNDOBUFFER after openfile?
because, Undo stores the changes, an older code before openfile ??

or or to avoid the black page of the early changes
which removes any code?

i understand ? ...

[dobro]

good, I stuck a:
ScintillaSendMessage (onglet, #SCI_EMPTYUNDOBUFFER, 0); clears the undo
at load file:)
The Undo, do not erase the editor ...

I think it's that, you were talking

valid in the next version

[dobro]

Version 1.80 online:)
http://michel.dobro.free.fr/download.php?view.25

Adding the completion of our procedures

if we print "procedure foo (t, f, d, re,)" ...

later, the writing "foo" will bring up the completion
support of a return or Tab write to our place ...

the default is that I use the library of Srod "Go scintilla"

and the function of completion ()

Code: Select all

GOSCI_RemoveKeywords(onglet, completioooo$)  ; ici on retire les precedentes declarations dans goscintilla 
GOSCI_AddKeywords( onglet,  completioooo$ ,#STYLES_FUNCTIONS ,#GOSCI_ADDTOCODECOMPLETION,#False)

is a very long init ..
but the result is nice

Default :
Therefore, more procedure() ; more slowly

a++

[Danilo]

Using '_' without required space is not so good in my opinion.

Code: Select all

Define.i var1_, var2_
Define.l var3, var4

This would produce

Code: Select all

Define.i var1_, var2_Define.l var3, var4

and lead to an error?

With required space ' _' it would be better, not? Of course not perfect
for PureBasic, because a simple '_' is a variable in PureBasic:

Code: Select all

Define.i x, a=12, _
_ = 5
x = a + _
Debug x

Not many people seem to use '_' as a variable so far, but if somebody
uses it, it would again make errors with your code.
But 'variable_' is more common, so with required space ' _' would be little bit better.

[dobro]

ok! thank you, Danilo

I will consider this in the next version

[dobro]

ok, archive Updated , with this change " _" (space+"_" for a cut line ) (not a new version,always, Version 1.80)

http://michel.dobro.free.fr/download.php?view.25

Code: Select all

If OpenWindow(0, _
100, _
200, _
195, _
260, _
"PureBasic Window", _
#PB_Window_SystemMenu _
| #PB_Window_MinimizeGadget _
| #PB_Window_MaximizeGadget)

or

Code: Select all

_block
	If OpenWindow(0, _
 	100, _
 	200, _
 	195, _
 	260, _
 	"PureBasic Window", _
 	#PB_Window_SystemMenu _ 
	| #PB_Window_MinimizeGadget _
 	| #PB_Window_MaximizeGadget)
_endblock

this run correctly :

Code: Select all

calldebugger
Define.i x, a=12,_= 5 _
,x = a +_
Debug x