PureBasic Forums - English

Code: Select all

***  
It would be beautiful, if the IDE would break up an individual instruction over several lines.  
If necessary by using of a special character "_" or so.    

Example:
OpenWindow(#PB_Any, 0, 0, 659, 329, "Testprogramm",  #PB_Window_SystemMenu | #PB_Window_MinimizeGadget |_
  #PB_Window_MaximizeGadget | #PB_Window_SizeGadget | #PB_Window_TitleBar )

***  
I miss a function to show a list of well defined constants, variables etc. which were never used in the source.    

***  
If you want to move whole procedures within the SOURCE, you can only do it by unfold the procedure and move the 
entire text (e.g. with cut/paste).  It would be really fine, even if you could move a folded procedure simply 
by marking the single line and performing cut & paste. 
If you perform this action momentarily on a folded procedure, then
  a) the procedure will be displayed unfolded immediately and
  b) only the first line, the procedurehead will be cutted out.  
It would fine, if you could edit a folded procedure like an individual line and the 
automatic unfolding at any edit on a procedurehead will be disabled.

***  
The searchfunction in the IDE stops with a find in such a way that the founded line always is the first line 
in the sourcewindow. It would be better, when those founded line is displayed centrically in the sourcewindow.
So you can recognize, what's up and down of this line in the source without scrolling up first.

***  
If a project consists of a main file and several Includes and the active sourcewindow is a include, you cannot
use "compile to .exe". An error message is indicated "errors in the main file... blah...". Even if the
mainsource is correctly defined in the Compileroptions.
Only if the mainsource is the current active sourcewindw the "compile to .exe" function works fine.

***  
If you use the tool "variable list" on the right side of the IDE, the focus/cursor will be lost in the sourcecode
if you use this tool.
Example: You are in line 33, row 24 and you doubleclick on a variablename in the tool "variable list", then
the variable will be inserted into your source - cool! But if you want to continue writing your source, then
you have to click at first at line 33, row 24 (+ varlenght). The focus is in the toolpanel after the doubleclick.

That disturbs the workflow. It would be better, if the focus and the cursor position in the editor window
would be reactivated after the doubleclick.

***  
"Splitscreen" in the editor would be fine. That means the current sourcearea could be spitted in serval
independent editareas using an splittergadget. The goal is to overwiew more than one locations of the same 
sourcefile. Maybe you know this "splittscreen" from M$ Word. 

Example now:  
+---------------------------------+  
| ......... source text ......... |  
| ....blah 1 .................... |  
| ....blah 2 .................... |  
| ....blah 3 .................... |  
| ....blah 4 .................... |  
| ....blah 5 .................... |  
| ....blah 6 .................... |  
| ....blah 7 .................... |  
| ....blah 8 .................... |  
+---------------------------------+    

Example my wish:  
+---------------------------------+  
| ......... source text ......... |  
| ....blah 1 .................... |  
| ....blah 2 .................... |  
| ....blah 3 .................... |  
|============== *** ==============| < - Splittergadget  
| ....blah 53.................... |  
| ....blah 54.................... |  
| ....blah 55.................... |  
| ....blah 56.................... |  
+---------------------------------+ 

***
An Option "Automatic loading of Includefiles" would be cool.
That means, if this Option is set and you load the main sourcefile, all included files which are a part of 
the mainfile will be loaded automaticly into new TABs in the IDE.

*** 
A little extend of the IDE-funktion "Autocomplete" (german: Autovervollstaendigen).
(I know it from some SQL-Tools which I use at work)
It would be fine, if you could enter a delay in the preferences for the autocomplete window.
That means the autocomplete window will only appear, if you stop typing for this time.

At the moment the Window appers immideately after entering x characters or (if the automation 
is disabled) the window opens only if you press CTRL-SPACE. So, now I'm hitting confused
ESC on every PB keyword or I disable the automation and have to press CTRL-SPACE, on a 
unknown keyword.

The workflow will be less disturbed if this window appears only automaticly when you stop 
typing for x seconds.

example: 
1) You type:      MyXVar = Win [wait for e.g. 1.5 seconds]  -> the autocomplete window pops up.
2) You type fast: MyXVar = WindowX() [no confusing window pops up, because you wrote
                  faster than 0.75 chars per second. ;)

***
Commenting huge blocks of code using an start- and endkeyword
Today the only way to comment large part of sourcecode is to mark all the text and using
CTRL-B. This puts a ';' on the beginning of each line.
It would be great, if you could comment large blocks of source using a "start- and
endcommentor" like this (the second example):

; I'm a normal PB comment
; I'm too
; Hey, I'm also a comment

/*
Wow... 
now we
are all
comments
only by
editing 
two lines!
*/