Page 23 of 104
Posted: Thu May 11, 2006 8:02 pm
by chen
I can't make it work in JaPBe... Im running PB4 Final, last jaPBe...
it doesnt recognize the directives: ENABLEOOP, DISABLEOOP
I installed it in jaPBe\Plugins... JaPBe detects it but it doesnt work..
Is there some info you can post to start?
Posted: Thu May 11, 2006 10:55 pm
by AL90
gnozal wrote:What do you suggest ?
I have now disable the option
create new file and enable the
overwrite file option.
It works now very good and 100%. Firstly I think the Original Source will be overwrite with
the converted code, therefore I select the "NewFile" option. However, now I have only
two Panels and all is correct. I think you must not anymore change it. Great Work. [Thumbs Up]
Posted: Thu May 11, 2006 11:24 pm
by inc.
@chen
Even its not on topic ....
In case of jaPBe usage u still have to compile by choosing the OOP plugin in the plugins dropdown menue of jaPBe as its still not updated.
Posted: Fri May 12, 2006 2:59 am
by Shannara
Any chance to add autocomplete for Imports?
Posted: Fri May 12, 2006 6:25 am
by Lars
I'm unsure whether this problem has already been posted.
"Find Next" (CTRL+F) behaves very sometimes behaves more than
strangely and finds previous searches' results instead of the new search-
word. Can't really reproduce the error, but maybe this description already is enough?
[Edit:]
Probably located:
It seems to happen when I look for something with ALT+F over a marked
word to look for that word. Once I give the focus to the 'look for' string
gadget it works fine.
Posted: Fri May 12, 2006 7:35 am
by gnozal
Shannara wrote:Any chance to add autocomplete for Imports?
It already works ?!
Example :
Code: Select all
Import "OnlyATest.lib"
MyNewImportIsAutocompleted()
EndImport
"MyNewImportIsAutocompleted(" is in the autocomplete dropdown list.
Or do you mean something else ?
Posted: Fri May 12, 2006 7:40 am
by gnozal
inc. wrote:@chen
Even its not on topic ....
In case of jaPBe usage u still have to compile by choosing the OOP plugin in the plugins dropdown menue of jaPBe as its still not updated.
Sorry, but I am not sure if I will support the OOP plugin (where ebp is loaded with the address of the structure element), as Fred says it's not safe to assume it will always work (undocumented feature).
Posted: Fri May 12, 2006 9:00 am
by oryaaaaa
2byte charator-code (SJIS) Trouble
Procedure LoadLanguage(lan$)
Procedure MenuTitleAlt(Text$)
Procedure MenuItemAlt(id,Text$)
Procedure OpenSubMenuAlt(Text$)
It did because of these codes.
It is because these do not consider two byte character.
I can solve this problem. Is the judgment code in two bytes better?
Posted: Fri May 12, 2006 9:31 am
by inc.
gnozal wrote:inc. wrote:@chen
Even its not on topic ....
In case of jaPBe usage u still have to compile by choosing the OOP plugin in the plugins dropdown menue of jaPBe as its still not updated.
Sorry, but I am not sure if I will support the OOP plugin (where ebp is loaded with the address of the structure element), as Fred says it's not safe to assume it will always work (undocumented feature).
I do agree on that! But Hellhound - also member from purebasic-lounge did offer an approach where you can obtain the same comfort but where the code in the background will be translated based on interfaces etc.:
http://www.purebasic-lounge.de/viewtopi ... hlight=oop
Also the final code resulting there seems shorter and Hellhound mentioned that by this only every object increases by 4 bytes instead 4 bytes per method.
Means ... the supported OOP syntax in jaPBe would still make sense. It just depends all on the used Preprocessor plugin and maybe we get some time to write a proprocessor or updating edels one using the same highlightning sytax but diff. routines (like Hellhounds one) to be translated to in the background.[/code]
Posted: Fri May 12, 2006 11:50 am
by gnozal
Lars wrote:I'm unsure whether this problem has already been posted.
"Find Next" (CTRL+F) behaves very sometimes behaves more than
strangely and finds previous searches' results instead of the new search-
word. Can't really reproduce the error, but maybe this description already is enough?
[Edit:]
Probably located:
It seems to happen when I look for something with ALT+F over a marked
word to look for that word. Once I give the focus to the 'look for' string
gadget it works fine.
I think I found the problem.
Please try http://people.freenet.de/gnozal/jaPBeForPB400_beta.zip
Posted: Fri May 12, 2006 11:57 am
by gnozal
oryaaaaa wrote:2byte charator-code (SJIS) Trouble
Procedure LoadLanguage(lan$)
Procedure MenuTitleAlt(Text$)
Procedure MenuItemAlt(id,Text$)
Procedure OpenSubMenuAlt(Text$)
It did because of these codes.
It is because these do not consider two byte character.
I can solve this problem. Is the judgment code in two bytes better?
I don't fully understand your problem (can't test it), but if you can solve it and it still work in 1 byte character code, I will gladly update the jaPBe code.
Posted: Fri May 12, 2006 2:30 pm
by Lars
Seems to be fixed, thanks.
Posted: Fri May 12, 2006 10:59 pm
by oryaaaaa
I don't fully understand your problem (can't test it), but if you can solve it and it still work in 1 byte character code, I will gladly update the jaPBe code.
Posted: Sat May 13, 2006 7:57 am
by gnozal
Ok, I see. What did you change in the source code ?
Posted: Sat May 13, 2006 9:01 am
by Le Soldat Inconnu
My own Tool don't works correctly, jaPBe don't run the correct tool, always the last tool in the menu.
I look the code and find why it's don't work fine.
In the file Tools.pbi
When we use %file parameter, you run SaveSourceCode() but this procedure put the list AddTools_Entries() to the end.
So, when jaPBe launch the tools, it don't use the correct element of AddTools_Entries().
To correct, I just add
Code: Select all
SelectElement( AddTools_Entries(), MenuID - 1 )
after SaveSourceCode()
I don't read all the post, may be this bug is already report.
Thanks for correction
