Page 38 of 104
Posted: Fri Oct 20, 2006 8:01 am
by gnozal
freak wrote:I don't think it is a good idea to invent your own system just out of lazyness.
It seems I am not the only one out here using this system (see other tailbited userlibs), maybe because PB should include better SDK tools.
freak wrote:You can easily add stuff like the _UNICODE postfix with a macro, and compile the same code multiple times with the different flags. (its what we do with the PB libraries as well.)
Maybe some ready-to-compile-with-tailbite example would be nice ?
freak wrote:The problem I see is that by adding it to jaPBE, you are encouraging others to do the same with their libraries, instead of using the proposed way. (which is much better for the users of the libraries, as everything is in one file, no subsystems etc to worry about.)
I do not encourage anybody, but maybe if others use the same system it's because of the poverty of the SDK tools (just my opinion).
And it's totally optional in jaPBe, nobody has to use it. If the 'special' subsystems don't exist, jaPBe does nothing.
freak wrote:Why not simply edit your custom tailbite to handle this, instead of forcing your users to use your own system ?
Because I am not the tailbite guru, I do not fully understand how it works.
But maybe I will have a closer look.
Posted: Fri Oct 20, 2006 12:50 pm
by remi_meier
I think freak means something like that:
Code: Select all
CompilerIf #PB_Compiler_Unicode ;>
CompilerIf #PB_Compiler_Thread ;>
Macro name(name)
name#_THREAD_UNICODE
EndMacro
CompilerElse ;=
Macro name(name)
name#_UNICODE
EndMacro
CompilerEndIf ;<
CompilerElse ;=
CompilerIf #PB_Compiler_Thread ;>
Macro name(name)
name#_THREAD
EndMacro
CompilerElse ;=
Macro name(name)
name
EndMacro
CompilerEndIf ;<
CompilerEndIf ;<
Procedure name(Test)(hello.l)
Debug hello
EndProcedure
name(Test)(4)
You could probably modify Tailbite to compile this source in all modes
once to create all the object files with the different functions. And then
create the lib out of all these object files.
Edit: And of course you also have to edit the .DESC
Posted: Sun Oct 22, 2006 7:26 am
by magicjo
@gnozal,
i would be submit just 2 little changes :
1) the possibility to copy the current selection from source window to search window when opened,
2) on first search from search window the focus returns on current source window, then pressing again F3 for repeat search the current selection got cancelled: i ask you if is possible change this logic and retain the focus on search window while stay opened.
Thanks in advance for you reply (i hope
)
Posted: Mon Oct 23, 2006 8:07 am
by gnozal
magicjo wrote:1) the possibility to copy the current selection from source window to search window when opened
Good idea, I will see what I can do. I will have to translate the selected text from current code page (if not default) to ANSI before pasting it in the search StringGadget.
magicjo wrote:2) on first search from search window the focus returns on current source window, then pressing again F3 for repeat search the current selection got cancelled: i ask you if is possible change this logic and retain the focus on search window while stay opened.
Hum, I don't know, I think it's more convenient if the source window has the focus during search.
Posted: Mon Oct 23, 2006 10:22 am
by gnozal
Update
Changes :
- the current selection is copied from source window to search window when the search window is opened (CTRL+F) ; big and/or multiline selections are not copied.
Posted: Mon Oct 23, 2006 10:43 am
by magicjo
Thanks gnozal for the changes and for your support , i can't live without JAPBE !
Posted: Mon Oct 30, 2006 4:00 pm
by chen
When you are writing down a PB procedure appears in the status bar the
procedure name, parameters and a small description...
is it possible that small description in our procedures? if it is not
implemented, could it be?
it could be adding a small comment in our procedure definition, then
the status bar show this comment in addition to the procedure name
and parameters...
myprocedure(param1, param2, [param..]) ; Show formated messages
thanks.
Posted: Mon Oct 30, 2006 5:38 pm
by gnozal
chen wrote:it could be adding a small comment in our procedure definition, then the status bar show this comment in addition to the procedure name and parameters...
myprocedure(param1, param2, [param..]) ; Show formated messages
It already works.
If you create a procedure like this :
Code: Select all
Procedure MyProcedure(Arg1, Arg2) ; My comment
EndProcedure
you should see the comment in the status bar.
Note that you can also add definitions files (have a look at the %jaPBe%\Definitions directory).
Posted: Mon Oct 30, 2006 8:50 pm
by chen
gnozal wrote:
Code: Select all
Procedure MyProcedure(Arg1, Arg2) ; My comment
EndProcedure
you should see the comment in the status bar.
Note that you can also add definitions files (have a look at the %jaPBe%\Definitions directory).
thats true! great
Posted: Tue Oct 31, 2006 12:52 pm
by gnozal
Update
Changes :
- enhanced 'Activate Help Hotspots' option ; see Preferences.
Posted: Tue Oct 31, 2006 3:15 pm
by dobro
tu pourrai pas ajouter la possibilité de modifier la fenêtre du constante explorer , voir d'ajouter l'agrandissement total
car actuellement, c'est pas génial de devoir utiliser les ascenseurs pour lire les définitions
Merci d'avance
Google Translation :
will be able you to add the possibility of modifying the window of “constants-explorer”, to see to currently add the total enlarging bus, it is not brilliant to have to use the elevators to read the definitions
Posted: Tue Oct 31, 2006 3:33 pm
by gnozal
dobro wrote:tu pourrai pas ajouter la possibilité de modifier la fenêtre du constante explorer , voir d'ajouter l'agrandissement total
car actuellement, c'est pas génial de devoir utiliser les ascenseurs pour lire les définitions
Ok, j'ajoute çà à ma petite liste.
(On the todo list).
Posted: Tue Oct 31, 2006 5:21 pm
by gnozal
Update
Changes :
- 'Constant Explorer' tool is now resizable
Posted: Tue Oct 31, 2006 7:03 pm
by dobro
Merci beaucoup
Posted: Fri Nov 03, 2006 10:59 am
by dobro
Sorry for the txt in French
but is easy for me !
problem avec la V3610.580
tu met ceci dans le premier onglet de Japbe () apres une ouverture neuve
Code: Select all
; au bout du deuxieme onglet voir du troisieme et des autres
; la recherche ne fonctionne plus
; mais en retournant sur le premier la recherche marche sur le premier onglet , mais toujours pas sur le deuxiemme
; bmp
; tga
; coucou
; test
ensuite tu effectue une Recherche du terme "bmp" en ayant la coche
"Min/Maj" de coché !
ok la recherche fonctionne
tu cree un deuxiemme onglet et tu copie le contenue de l'onglet 1 dans le nouvel onglet 2
et tu effectue une recherche du meme terme "bmp" dans l'onglet 2
Japbe ne trouve rien !
et c'est pareil pour tous les autre nouveaux onglet !!
il m'est meme arrivé qu'en revenant sur l'onglet 1, il ne trouvais plus rien non plus
en esperant que tu trouvera le Bug
(bon courage
)
****************************************************************
****************************************************************
google Translation
***************************************************************
**************************************************************
problem with V3610 you put this, in the first onglet of Japbe () after a new opening puts
Code: Select all
; au bout du deuxieme onglet voir du troisieme et des autres
; la recherche ne fonctionne plus
; mais en retournant sur le premier la recherche marche sur le premier onglet , mais toujours pas sur le deuxiemme
; bmp
; tga
; coucou
; test
then you a Research of the term “bmp” by having carries out the stage coach “Min/Maj” of notched! ok research functions you creates a second onglet and you contained onglet 1 in new onglet 2 copies and you a research of the same term “bmp” in mitre 2 carries out Japbe does not find anything!
and it is similar for all the other new onglet!! it same happened to me that while returning on onglet 1, he did not find anything any more either:? by hoping that you will find Bug: D (good courage: D)[/code]