jaPBe 3.13.4 [IDE for PB 4 and PB 5]

gnozal · Post by **gnozal** » Thu Mar 23, 2006 9:11 am

About the visual designer plugin : no alarm with F-Prot.
It's simply packed with PECompact (as is jaPBe.exe !).
You can compile the file 'Visual Designer Starter.pb' if you like, so you have a non packed executable.

gnozal · Post by **gnozal** » Thu Mar 23, 2006 12:49 pm

Update

- Fixed a potential crash when using new code view feature.

EDIT (17:35 GMT+1) :

- Changed file association (didn't work well for me on NT)

chen · Post by **chen** » Fri Mar 24, 2006 5:44 am

Hi,

Is there a way that when Im testing my code (running) only use one executable in memory?

For example... If a run the first time and I dont like the position of a button
I change the x,y and test again... I want to reuse the same executable
and not open as many executables as testing Im doing....

Hope is clear... I dont understand myself

gnozal · Post by **gnozal** » Fri Mar 24, 2006 10:37 am

chen wrote:Hi,

Is there a way that when Im testing my code (running) only use one executable in memory?

For example... If a run the first time and I dont like the position of a button
I change the x,y and test again... I want to reuse the same executable
and not open as many executables as testing Im doing....

Hope is clear... I dont understand myself

I don't understand what you mean

You can do F5/F6 as many times you want using the same code window.

gnozal · Post by **gnozal** » Fri Mar 24, 2006 5:11 pm

Update

Rewriting of the event code for the new code viewer panel : now supports #SCN_STYLENEEDED notification and should be more reactive.

zikitrake · Post by **zikitrake** » Fri Mar 24, 2006 6:00 pm

first of all, thank you for continue updating jaPBe...

bugs:
- When I push in 'Include Viewer' button, the windows is empty in another include file different of the principal

Flype · Post by **Flype** » Fri Mar 24, 2006 6:10 pm

Just a little wish :

In "jaPBe - Constants Explorer" can you make the search a little bit easier.

At the moment you have to type the constant entirely to find it.
What i would like is to be able to search a 'part of' the constant by typing for example 'wheel' for finding '#WM_MOUSEWHEEL'.

chen · Post by **chen** » Fri Mar 24, 2006 6:38 pm

Gnozal Wrote

I don't understand what you mean
You can do F5/F6 as many times you want using the same code window.

Im creating my own Visual Designer... a simple one.... I created a
PB program that contains all the PB objects... when you click on an object
you are copying the creation code of that object with default values..... using
the clipboard feature.

As my objects have default values, I need to adjust them in my application,
then I do several tries until the object get the position I want.....

As Im using jaPBe, every time I change values I run the application to see
if the objects appears where I want, if not I change again and test... and so on....

In every try appears a new instance of the application with the new values..
It comes the time when I have a lot of open instances......

Is there a way (a parameter to adjust) to use only one instance...? That every
time I try new values jaPBe destroy the old instance and comes out with
a new instance .... to avoid so many open instances

Thanks hope this time is clear

gnozal · Post by **gnozal** » Sat Mar 25, 2006 8:54 am

Flype wrote:Just a little wish :
In "jaPBe - Constants Explorer" can you make the search a little bit easier.
At the moment you have to type the constant entirely to find it.
What i would like is to be able to search a 'part of' the constant by typing for example 'wheel' for finding '#WM_MOUSEWHEEL'.

Ok, will see.
You already can do this : uncheck 'Only value', it will search for '#WHEEL*' (but it's not exactly what you want : *WHEEL*).

Chen wrote:Is there a way (a parameter to adjust) to use only one instance...? That every
time I try new values jaPBe destroy the old instance and comes out with
a new instance .... to avoid so many open instances

If you are speaking of jaPBe instances, did you try the option (in Preferences dialog) 'Run one instance only' ?
If you are talking about your application instances (when run from jaPBe with F5 or F6), you have to terminate the application yourself. Each time you press F5/F6, jaPBe is creating a new EXE (it does not check and terminate a previous instance of the EXE).

gnozal · Post by **gnozal** » Sat Mar 25, 2006 10:49 am

zikitrake wrote:When I push in 'Include Viewer' button, the windows is empty in another include file different of the principal

I cannot reproduce this, but I do not use this feature myself, so maybe I don't understand what you mean ?
Does this bug also exists in the 'old' jaPBe ?

gnozal · Post by **gnozal** » Sat Mar 25, 2006 10:51 am

Flype wrote:In "jaPBe - Constants Explorer" can you make the search a little bit easier.

Updated : just uncheck 'Exact match' and it should do what you want.

zikitrake · Post by **zikitrake** » Sat Mar 25, 2006 1:49 pm

gnozal wrote:
zikitrake wrote:When I push in 'Include Viewer' button, the windows is empty in another include file different of the principal
I cannot reproduce this, but I do not use this feature myself, so maybe I don't understand what you mean ?
Does this bug also exists in the 'old' jaPBe ?

In previous version no problem to display all include files in any tab :S

gnozal · Post by **gnozal** » Sun Mar 26, 2006 11:48 am

I've done some tests :
Old jaPBe

New jaPBe

The results are identical. Or am I missing something ? Could you post a small code that illustrates your problem ?

Dräc · Post by **Dräc** » Sun Mar 26, 2006 12:06 pm

Concerning the code panel:

In fact (and you will do it more quickly than me), can I suggest to you that instead of having a code panel, to directly split the current code screen with a "SplitterGadget"?

It is the most common approach in other editors and that allows:
- to release the space of right-hand side
- to benefit of the optimal space for the open file panel display

Thus, it should be necessary:
- to give to the user the choice of splitter or not the current screen
- to manage if, from opened file to opened file, the screen is splitter or not
- to preserve the parameters of split (height of the screens, positions of the lines of codes displayed...)

gnozal · Post by **gnozal** » Mon Mar 27, 2006 5:14 pm

Dräc wrote:Concerning the code panel, can I suggest to you that instead of having a code panel, to directly split the current code screen with a "SplitterGadget"?

The actual solution was easier to implement : the SplitterGadget and the parent window were already there and so was the event handling (and it was an experience to see how the multiple view works).
I have the horizontal SplitterGadget solution in mind (I was expecting this kind of question sooner or later

) , but I don't know yet how exactly to implement it.