[Gambas-devel] Integrated Help

[Robert Rowe]

Oh, that's cool. I thought it read the file each time. More Windows junk 
cluttering my mind. Settings files are very much like ini files in 
Windows. The tool I use for ini files does not cache like this.

I think that you introduced a small bug when you changed the VSplit to a 
side panel. If you exit the IDE with the Property window showing and 
with an editor window as the active window then when you reload the 
project the new side panel is made very tall and it won't shrink or 
collapse. I'll add the code to re-establish the last size and see if it 
fixes it.

Nice fix on the removal of the links. I thought about maybe making the 
links open a browser to the linked page. Until this is done I agree that 
the links should be removed.

Robert Rowe

Benoit Minisini wrote:
> On vendredi 21 mars 2008, Robert Rowe wrote:
>   
>> See below.
>>
>> Benoit Minisini wrote:
>>     
>>> On jeudi 20 mars 2008, Robert Rowe wrote:
>>>       
>>>> I've committed my integrated help changes. This is actually only the
>>>> first of two changes that I'm doing for the integrated help. The other
>>>> will show a help message to the right of the completion window for the
>>>> selected completion item. Since this will take a while I thought that I
>>>> should go ahead an check in what I had.
>>>>
>>>> Robert Rowe
>>>>         
>>> Hi,
>>>
>>> I have fixed a few things in your integrated help (see the ChangeLog).
>>>
>>> A few remarks:
>>>
>>> - Prefix the name of a local variable with its type (b for boolean, i for
>>> integer, s for string, c for Collection, a for any array, h for an object
>>> handle...)
>>>       
>> I thought that I had done this but I guess that I missed some places. :(
>>
>>     
>>> - $xxx is a name for a private variable. Public variables should be named
>>> with letters only, the first one of each word being in uppercase.
>>>       
>> I thought that the $ signified class scope. I understand now.
>>
>>     
>>> - You put $bDisableIntegratedHelp in FMain. Why? You should have put it
>>> in FProperty, as it does not concern FMain at all. This way, it does not
>>> have to PUBLIC anymore!
>>>       
>> I didn't want the property window to have to read the config file every
>> time that it opened. The value would only change on startup and when it
>> was changed on FOption. Am I misunderstanding how the Settings object
>> works?
>>
>>     
>
> The Open and Close event of FProperty are raised once, so you will read and 
> write the setting once.
>
> Moreover, the Settings actually reads the file once, at startup. It writes it 
> when the program exits, or if you manually calls its Save() method.
>
> Regards,
>
>