On Fri, Jun 11, 2010 at 01:18, Lex Trotman wrote:
> On 11 June 2010 01:24, Jiří Techet wrote:
>> On Thu, Jun 10, 2010 at 14:59, Lex Trotman wrote:
>>> On 10 June 2010 21:23, Nick Treleaven wrote:
On Thu, 10 Jun 2010 11:44:24 +0200
Jiří Techet wrote:
> >> Yes, it's pretty con
> To me this seems to be much better than the current state and would
> solve all the problems I have with the current settings
As I have said just because you have problems doesn't mean that other
people should give up functionality that they use.
(like the mess
> with the project filetype conf
On Fri, 11 Jun 2010 00:17:13 +0200
Jiří Techet wrote:
> > Find in project segfaults. I'll compile a -g version tomorrow.
>
> Fixed & pushed (I knew about this and had the fix, just forgot to push
> it). It was because the active file you were looking at didn't belong
> to the project (or you jus
On Fri, Jun 11, 2010 at 19:30, Dimitar Zhekov wrote:
> On Fri, 11 Jun 2010 00:17:13 +0200
> Jiří Techet wrote:
>
>> > Find in project segfaults. I'll compile a -g version tomorrow.
>>
>> Fixed & pushed (I knew about this and had the fix, just forgot to push
>> it). It was because the active file
>> Instead of *.gpc, store the gproject settings in *.geany, removing
>> the duplicates.
>
> I would have to be able to add extra settings to .geany - not possible now.
>
Hi Jiri,
To do this catch the "project-open" and "project-save" signals from
the Geany object, the user_data is a pointer to
On Fri, Jun 11, 2010 at 14:07, Lex Trotman wrote:
>> To me this seems to be much better than the current state and would
>> solve all the problems I have with the current settings
>
> As I have said just because you have problems doesn't mean that other
> people should give up functionality that t
On 12 June 2010 10:15, Jiří Techet wrote:
> On Fri, Jun 11, 2010 at 14:07, Lex Trotman wrote:
>>> To me this seems to be much better than the current state and would
>>> solve all the problems I have with the current settings
>>
>> As I have said just because you have problems doesn't mean that o
> My current thinking is that the dialog that is shown is read only and
> shows what will actually be run, and then there is an edit button
> which shows a sub-dialog. If a project is open the subdialog has two
> sets of fields, if no project then only one set, or the project fields
> are insens
Hi Nick, Enrico, Jiri,
I have made a version of build such that In the build config dialogs,
that is both "set build commands" dialog and project properties tab:
1. settings being overridden from another source are insensitive
(current behaviour)
2. fields where the setting is set from another so
On Sat, Jun 12, 2010 at 01:06, Jiří Techet wrote:
> On Fri, Jun 11, 2010 at 19:30, Dimitar Zhekov
> wrote:
>> On Fri, 11 Jun 2010 00:17:13 +0200
>> Jiří Techet wrote:
>>
>>> > Find in project segfaults. I'll compile a -g version tomorrow.
>>>
>>> Fixed & pushed (I knew about this and had the fi
10 matches
Mail list logo