User forums > Using Code::Blocks

COM server

<< < (2/2)

daniloz:

--- Quote from: jens on November 25, 2010, 01:30:44 pm ---If you uncheck "Settings -> General settings -> Allow only one running ..." and check "Settings -> General settings -> Use an already running ..." and "Settings -> General settings -> Bring it on ...", you just have to call C::B with the appropriate parameters (e.g. --file=name[:line] to open a file in a running instance of C::B).
In this case all the DDE-stuff is done by C::B itself and you don't have to care about it.

--- End quote ---

Shouldn't it be CHECK "Settings -> General settings -> Allow only one running ..." ?? I don't want another one to be opened...

daniloz:
Actually, I don't see any difference here whether "Settings -> General settings -> Allow only one running ..." is checked or unchecked... I'm puzzled  :shock:

What should be the difference??

Another point, if C::B is minimized, it's not automatically maximized, it only gains the focus... Don't you think it should be automatically maximized in this case?

Btw, thank you very much for your reply, I really like this solution...

Jenna:
If you do not run another instance of C::B, that does not allow DDE-/IPC (started with -nd/-ni), it does not matter.
But if you have a running instance of C::B, that does not run a DDE-/IPC-Server, it will fail, if "Allow only one running instance" is checked, because the signal can be send, but "nobody" will answer and no new instance can be started.

That's the normal situation for me, if I work in C::B on C::B.

Jenna:

--- Quote from: daniloz on November 25, 2010, 01:51:43 pm ---Actually, I don't see any difference here whether "Settings -> General settings -> Allow only one running ..." is checked or unchecked... I'm puzzled  :shock:

What should be the difference??

Another point, if C::B is minimized, it's not automatically maximized, it only gains the focus... Don't you think it should be automatically maximized in this case?

Btw, thank you very much for your reply, I really like this solution...

--- End quote ---

If "Bring it on top..." is checked the MainFrame of C::B is raised via the (wxWidgets) Raise()-function, but it seems not always work as expected:


--- Quote from: http://docs.wxwidgets.org/stable/wx_wxwindow.html#wxwindowraise ---wxWindow::Raise

void Raise()

Raises the window to the top of the window hierarchy (z-order).

In current version of wxWidgets this works both for managed and child windows.


--- End quote ---

Navigation

[0] Message Index

[*] Previous page