AZJIO wrote: Thu Dec 05, 2024 10:05 pm
I made a
partial translation. Some words don't fit on the buttons, so I made them abbreviated. I used Google, so some words, although different, have the same meaning, so your version is quite normal.
All right! I've adapted some gadgets width in order to support longer strings. So, I keep my Russion language version which is more complete. If, in the future, you find any word or sentence that is not the right one, please tell me.
AZJIO wrote: Thu Dec 05, 2024 10:05 pmCtrl+F - Rechercher, Chercher, Respecter, Mot entie - no translation
That was an authentic bug. It's fixed with beta 0.22
AZJIO wrote: Thu Dec 05, 2024 10:05 pmI'm using Win10x64 with Arial 11/12
larger font
So, I decided to reset the font used by PBBrowser's gadgets to the standard Segoe UI - 9 pts. The explanation is bellow:
AZJIO wrote: Thu Dec 05, 2024 10:05 pmYou can set the height of the button in the PBBrowser.prefs settings and use this for the input field and button when calculating window resizing. Then if someone has a large font, he can fix it with the height of the button.
I appreciate the suggestion, but it won't solve all the potential problems: for example, width of many gadgets will probably be to tight.
Of course, I could mesure the size of each string and adapt the size of each gadget to it, and, then, adapt the global design of the window to the new gadgets width, but it's a nightmare to put together. Tell me if my solution seems satisfying to you.
AZJIO wrote: Thu Dec 05, 2024 10:05 pmWhy do you use EditorGadget for source and expression input fields when StringGadget would be suitable?
To be able to manage sliders, when the content is to big to fit in the field.
AZJIO wrote: Thu Dec 05, 2024 10:05 pmOn the "Macros" tab, on a black background, there is black text "No element was found."
It was another authentic bug. Fixed with beta 0.22
AZJIO wrote: Thu Dec 05, 2024 10:05 pmWhy duplicate the "Close" button at the bottom? There is also a button at the top (X) and a hot key (Esc).
To respect all possible user habits.
AZJIO wrote: Thu Dec 05, 2024 10:05 pm"Time spent exploring" -> "Time spent scanning".
I don't agree. The 'exploration' expression has a particular meaning in the PBBrowser vocabulary. It corresponds to the 'Elements' identification.
AZJIO wrote: Thu Dec 05, 2024 10:05 pm"Execute" -> "Site" (HyperLinkGadget?)
Why not. But what for?
AZJIO wrote: Thu Dec 05, 2024 10:05 pmWhy does only the GUI change when changing the language? From this I conclude that the windows are created but hidden, otherwise using the updated variables would lead to modified windows.
The editorGadgets content is not reset by the 'Language' command. But as soon as you launch a new search, this content is refreshed with the chosen language. It's really a detail, because we don't change languages every day. But I grant you that it could be improved.
AZJIO wrote: Thu Dec 05, 2024 10:05 pmWhy include help texts in the executable file? Isn't it possible to make an external CHM file?
I wanted to combine help texts and Tools/menu settings because it seem very important to me that each tool (even custom tools added by the user) has its own little description text. As you can see, when you choose a tool description in this pannel, you get access to its shortcut configuration its menu visibility and a possibility to execute it.
AZJIO wrote: Thu Dec 05, 2024 10:05 pm"Cosmetic Enhancer" has a problem with "
Define * element" pointers. Here you can check whether there is a digit after the asterisk; the variable cannot begin with a digit. Also check which element is before the asterisk; if it is the beginning of a line or a keyword, then the asterisk is a pointer marker. You can look at my
Tide utility. I use tabs for indentation.
Checking if the variable begin with a digit solves only some cases. Looking at what is before the "*" char is safer. There was a bug in that part of the Cosmetic enhancer. It's fixed in Beta 0.22.
I did'nt know your tool which is very interresting. I've seen that it's a sort of dupplicate from another similar tool. If you think that one of these does the things in a better manner than my "Cosmetic Enhancer", please describe what you want to add or modify.
You gave me a wonderful list of comments and bug reports. A huge thank you! I hope I have answered most satisfactorily.
If you have special wishes, I am here to listen to you.
Beta 0.22 is online.