Author Topic: Bug: 12.0.1.0: Compiled file closed.  (Read 2239 times)

lambertia

  • Senior Community Member
  • Posts: 382
  • Hero Points: 14
  • I have nothing sufficiently witty to say.
Bug: 12.0.1.0: Compiled file closed.
« on: June 07, 2007, 06:50:00 am »
Hi

RE: The option to Automatically close visited files on the General tab of the Extension Options dialog (Tools > Options > General) now works with Next Error (Build > Next Error or next_error command) and Previous Error (Build > Previous Error or prev_error command). 

This is fine, except if you compile a file and then go next error, it closes the file you have just compiled. So when you've fixed an error and you want to compile again you need to reopen the file! This is a pain.

Perhaps when performing the next/previous error thing you should not close any files that are already open. I.E. Only close files which are opened as the result of the user pressing next/prev error.

Cheers,
--
Greg.

hs2

  • Senior Community Member
  • Posts: 2736
  • Hero Points: 285
Re: Bug: 12.0.1.0: Compiled file closed.
« Reply #1 on: November 09, 2007, 12:05:39 pm »
I think I've found the problem causing this quite annoying behaviour:
error.e - next_error() [line 959]: (v12.0.3)
Code: [Select]
      // HS2-CHG: avoid unwanted close of the current buffer
      // _mdi.p_child.push_destination(orig_window_id, orig_buf_id);
      _mdi.p_child.push_destination();

@SlickTeam: Hope I'm right - seems to 'work for me'. But it should be (hot)fixed anyway.

HS2

Edit: The problem occurs if the current buffer doesn't contain an error and 'next-error' is executed.
« Last Edit: November 09, 2007, 12:29:41 pm by hs2 »