Nicknack
09-19-2009, 04:13 PM
PPL 2 has still many teething problems, I have encountered so many of them I'm quite sure to forget telling now a few:
category PPL 2 Demo:
1. the welcome isn't correctly shown after you resize it at one side and scroll afterwards. it also looks as whole a bit disordered (more items on the right side than on the left). don't forget to give the user manual and tutorial book buttons a function.
2. you should make a hint in your installation which advices to install Active Sync before PPL 2, so the mobile part get also installed. or you add an option to install the mobile part later.
3. you should overwork the project demos, nearly the half doesn't work properly:
IfElse: combobox.text only returns "combobox" and not the written value
ListBox: the Set button can't change the selected item, since ListBox.itemtext = any value doesn't work
GroupBox: the items in the GroupBox aren't correctly shown, they appear only completly as black boxes
TextEditor: the ToolBar graphics are invisble and the menu buttons have no function except close. you can only cut,copy and paste with keystrokes, but the keystrokes for eg. new file don't do anything, too.
Dialogs: the compiler returns the error: PFILELIST not found at speficic code line.
4. there is also in every project your runtime path still saved, so when we run one project, we get the message the runtime is not found, although the default runtime path is correctly adjusted.
5. concerning mobile: your cab installation does some strange settings for file associations, the command path for .ppc files is set up broken and .ppl files get associated to pocket word.
6. although I corrected the associations, I can't run a project from the pc on the mobile device. the file gets transfered (at least I know it for compiling), but nothing happens on the device after the pc transfered it. if I run a ppl file manually on the device it works.
7. why do you put PPL2.exe in the startmenu when it has no real functionality?
8. a easy accesible quick guide would be good, where is shortly described where you find demos, how to run a file ... etc.
category PPL 2 general:
9. the debug mode isn't stopped automatically after you exit a running program, is this intended?
10. you can't open two new empty code files in a series, if you don't rename the first before you add the next.
11. PPL makes for every file you open in the explorer a new instance, wouldn't it be more compfortable if a new opened file would add itself as tab to the existing window? a drag&drop feature in this context would be also helpful ;)
12. save as code template doesn't do it's job.
13. the old skeletons like GameAPI and WinAPI are still needed for manual coding, where are they hidden in PPL 2?
14. code files for forms get now quite long, because each parameter for each control has a own code line. how about hiding code lines between begincreating and endcreating by default in the same way like you can hide functions? you don't need to change params that often.
category programming:
15. a bug I found with 1.53 on ppc, works with 2.x:
#define HELLO -3
a$=-3;
case(a$)
HELLO: showmessage("hello");
end;
16. general problem with compiler directives of variables in combination with objects/structs:
#define TEST s$
proc main
struct(TEST, "a", "b");
TEST.a$=55;
showmessage(TEST.a$);
end;
I think that was it for now, there might be more to follow :D hope this helps you kornalius and not makes you crazy...
category PPL 2 Demo:
1. the welcome isn't correctly shown after you resize it at one side and scroll afterwards. it also looks as whole a bit disordered (more items on the right side than on the left). don't forget to give the user manual and tutorial book buttons a function.
2. you should make a hint in your installation which advices to install Active Sync before PPL 2, so the mobile part get also installed. or you add an option to install the mobile part later.
3. you should overwork the project demos, nearly the half doesn't work properly:
IfElse: combobox.text only returns "combobox" and not the written value
ListBox: the Set button can't change the selected item, since ListBox.itemtext = any value doesn't work
GroupBox: the items in the GroupBox aren't correctly shown, they appear only completly as black boxes
TextEditor: the ToolBar graphics are invisble and the menu buttons have no function except close. you can only cut,copy and paste with keystrokes, but the keystrokes for eg. new file don't do anything, too.
Dialogs: the compiler returns the error: PFILELIST not found at speficic code line.
4. there is also in every project your runtime path still saved, so when we run one project, we get the message the runtime is not found, although the default runtime path is correctly adjusted.
5. concerning mobile: your cab installation does some strange settings for file associations, the command path for .ppc files is set up broken and .ppl files get associated to pocket word.
6. although I corrected the associations, I can't run a project from the pc on the mobile device. the file gets transfered (at least I know it for compiling), but nothing happens on the device after the pc transfered it. if I run a ppl file manually on the device it works.
7. why do you put PPL2.exe in the startmenu when it has no real functionality?
8. a easy accesible quick guide would be good, where is shortly described where you find demos, how to run a file ... etc.
category PPL 2 general:
9. the debug mode isn't stopped automatically after you exit a running program, is this intended?
10. you can't open two new empty code files in a series, if you don't rename the first before you add the next.
11. PPL makes for every file you open in the explorer a new instance, wouldn't it be more compfortable if a new opened file would add itself as tab to the existing window? a drag&drop feature in this context would be also helpful ;)
12. save as code template doesn't do it's job.
13. the old skeletons like GameAPI and WinAPI are still needed for manual coding, where are they hidden in PPL 2?
14. code files for forms get now quite long, because each parameter for each control has a own code line. how about hiding code lines between begincreating and endcreating by default in the same way like you can hide functions? you don't need to change params that often.
category programming:
15. a bug I found with 1.53 on ppc, works with 2.x:
#define HELLO -3
a$=-3;
case(a$)
HELLO: showmessage("hello");
end;
16. general problem with compiler directives of variables in combination with objects/structs:
#define TEST s$
proc main
struct(TEST, "a", "b");
TEST.a$=55;
showmessage(TEST.a$);
end;
I think that was it for now, there might be more to follow :D hope this helps you kornalius and not makes you crazy...