You must haven't looked really farTrond wrote:Just downloaded it and I've already uninstalled it.
This is my editor since I'm using PB, and I would stop using it for nothing
!feature request...
Ok, I downloaded again.Polo wrote:You must haven't looked really farTrond wrote:Just downloaded it and I've already uninstalled it.
This is my editor since I'm using PB, and I would stop using it for nothing
Of course, many of the items below are only my opinion, but my opinion is the most important when I choose which software to have and which software to uninstall.
1. Doesn't allow me to select where I want the program group in the start menu.
2. Ugly toolbar icons.
3. Toolbar icons not done in a consistent style.
4. Ugly hoovering effect on toolbar icons.
5. Ugly background colour on toolbar.
6. Ugly insert cursor.
7. The whole UI looks like it's thrown together in a hurry, no distances are the same.
8. Inconsisten capitalization of menu items.
9. Filters (in the open/save file box, you can select file filters in a combobox) incorrectly written.
10. Non-standard Ok buttons.
11. Flickering when switching between sources.
12. FATAL: NO INTEGRATED DEBUGGER
13. Source view flickers the first time a character is inserted after loading a file/creating a new file.
14. FATAL: NO KEYBOARD SHORTCUT CUSTOMIZATION
15. Refuses to use default directory instead of hard-coded directory for open/save dialog boxes.
16. Flickers when I'm using TAB while text is selected.
17. Flickers a lot and is much slower than PB when opening multiple files.
18. Much fewer shortcut possibilities when configuring keyboard shortcuts for tools.
19. Can't dock ASCII table.
20. ASCII table has less information than PB's visible at once.
21. Cancel button in ASCII table responds to left mouse down instead of left mouse click.
22. Structure viewer doesn't have constants.
23. The colour picker is the standard Windows one which doesn't show the colour in hex.
24. Template browser is slow and flickers a lot.
25. No icons in menus.
26. Ugly about box.
27. Ctrl-Q, Ctrl-E, Ctrl-T, Ctrl-Y, Ctrl-I, Ctrl-Å, etc, etc, gives weird symbols in the editor.
28. Ctrl-Enter is required to insert from autocomplete.
29. Selected font has the same colour as not selected (and that makes it difficult to see unless you choose a selection colour which is very close the usual foreground colour, and that again is ugly.
30. If you click the log view you'll never get rid of that blue bar until you restart.
31. Log view never seems to empty and it's annoying to see things pile up without any option of removing it.
32. Log view has some annoying "whole line must be visible" feature which does not appear to agree with me when the whole line is visible.
33. Statusbar hints for function arguments does not select current parameter perfectly.
34. Probably more but I'm sick already.
35. Uninstaller did not delete the preferences file even though I unchecked "Do not delete new files".
I guess I'm still using JapBE because I don't wanna change...thefool wrote:the new pb ide is beginning to take over now. Before, japbe was much better.
However, i have japbe installed just because of the auto-format using ctrl+tab.
But JapBe is incredibely stable, I never had a crash with it, which is totally different with the PB ide, well, I know, it's better now, but I still prefer Japbe
It crashes when debugging two sources including the same source which is also opened, using the inline debugger.Fred wrote:You are welcome to report any crashs encountered with the IDE (i don't have a signle one since several months now).
It also crashes when pasting a Chr(1).
Edit: Also crashes when pasting Chr(2). I don't want to try to Chr(3). A point here is that you can safely enter a Chr(2) using your keyboard (that is, if you know how) and you can safely copy it, but when you paste it outside a string (you CAN paste it between double or single quotes) the editor goes into an infinite loop or something.
Edit 2: It also crashes if you do this.
1. Copy and paste this into the PB editor.
Code: Select all
Procedure.s RunGetFasmOutput()
Protected ret.l, hReadPipe.l, hWritePipe.l, lngBytesread.l
Protected proc.PROCESS_INFORMATION, start.MySTARTUPINFO, sa.SECURITY_ATTRIBUTES
Protected strBuff.s
ProcedureReturn mOutputs
EndProcedure3. Go to Compiler - Compiler Options.
4. Check "Enable ASM"
5. Click ok.
6. The procedure unfolds. OR The editor crashes.
7. If it hasn't crashed yet, click the Open file button on the toolbar.
8. The editor crashes. OR The editor doesn't crash.
9. If the editor didn't crash, restart PB and go to step one. In about 3 out 4 cases it will crash during the above process here.
Enough crashes for you?
