Author Topic: fixing EVT_PROJECT_OPEN  (Read 18088 times)

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: fixing EVT_PROJECT_OPEN
« Reply #15 on: June 28, 2007, 11:41:04 pm »
I see... well, i added that event just this week to fix a bug in the codecompletion parsing (and I never liked the Timer-based startup anyway, it leaves so much to luck).  I admit it, that it caused a crash, but that was fixed in only one day, and that's because I overlooked something. And I don't want to leave loose ends in the code that I write. That double-triggering is a loose-end.

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: fixing EVT_PROJECT_OPEN
« Reply #16 on: June 29, 2007, 10:40:36 am »
I see... well, i added that event just this week to fix a bug in the codecompletion parsing
Well, that's what I'm talking about. We're in a feature freeze phase. I personally don't agree with the freeze at this time, as I don't like releasing the API as it is, but the decision for the freeze has been made.

However, we're still regularly adding features and making modifications to core functionality which are not necessary. Things that previously worked fine are starting to become dodgy again.

The problem with events being sent twice has been known for a long time (about half a year). Yiannis looked at it half a year ago and was unable to fix it without either rewriting the whole thing or breaking something else.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline Biplab

  • Developer
  • Lives here!
  • *****
  • Posts: 1874
    • Biplab's Blog
Re: fixing EVT_PROJECT_OPEN
« Reply #17 on: June 29, 2007, 10:52:58 am »
Well, that's what I'm talking about. We're in a feature freeze phase. I personally don't agree with the freeze at this time, as I don't like releasing the API as it is, but the decision for the freeze has been made.

I thought of not issuing couple editor events while the ProjectManager is busy. Accordingly I talked to Yiannis and got his nod. But feature freeze was the reason why I didn't change the occurrence of editor events. Because not issuing them may have some negative impacts. :)

IMHO, we should now declare Feature freeze officially so that people stop adding new features. :)
Be a part of the solution, not a part of the problem.

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: fixing EVT_PROJECT_OPEN
« Reply #18 on: June 29, 2007, 11:04:09 am »
We're in a feature freeze phase.

Technically we 're not but we should be acting like we are :).
Be patient!
This bug will be fixed soon...

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: fixing EVT_PROJECT_OPEN
« Reply #19 on: June 30, 2007, 02:45:39 pm »
OK :)

Offline pauliusz

  • Multiple posting newcomer
  • *
  • Posts: 73
Re: fixing EVT_PROJECT_OPEN
« Reply #20 on: July 01, 2007, 10:47:10 pm »
Feature freeze is OK, but...
Maybe it would be better to branch the "1.0 RC3 stable" version and continue working on trunk without any restrictions? I know that this will require a little bit more work on merging bug fixes from trunk to this branch, but maybe it is better then stalling development?

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: fixing EVT_PROJECT_OPEN
« Reply #21 on: July 02, 2007, 10:53:30 pm »
Feature freeze means that bugs should still be fixed. There are some bugs which need attention before releasing RC3, and we can't branch until those are fixed.