Improper Window Placement when transfering settings to new computer

[Cool Javelin]

Hello:

I recently purchased a new laptop, and wanted to use the settings from my desktop.

Laptop computer, Win10 64bit C::B v17.
Desktop computer, Win7 32bit C::B v16.

My desktop has multiple monitors, and, of course, the laptop has only one.

I copied the default.conf file from desktop C:\Users\Mark\AppData\Roaming\CodeBlocks into the similar location on the laptop.

I found and compiled one of my projects and when I went to debug, C::B loaded the debug perspective.

It turns out the watch window and others were on different monitors on the desktop, and did not display on the laptop.

No matter what I did, I could not correct the issue using C::B. I tried to de-click the little check boxes on the tool bar windows icon and other things.

Finally, I deleted the "defaults.conf" file and, of course, C::B recreated using the defaults and it works.

So, I guess I have a couple of choices.
#1) Open C::B on the desktop, start a debug session, move any windows that are on other monitors to my main monitor, stop debug, close out, then copy the config to the laptop.

#2) (I did not try this) On the laptop, start debug and try to get Windows to rearrange the windows somehow, (maybe right click Windows desktop ...)

This may not be so much of a bug as a feature request, but it took me a while to figure out what was happening.

Could C::B detect it is trying to open a window in a location that does not exist and, if so, change the coordinates of that window to something sane?

Thanks, Mark.

PS, One last thought while I write this, I guess the window settings, being in default.conf, are global and are the same across all the projects. I did not notice this, but thinking back all my projects look the same. It might be better to have each project have its own window settings.

M.

[oBFusCATed]

PS, One last thought while I write this, I guess the window settings, being in default.conf, are global and are the same across all the projects. I did not notice this, but thinking back all my projects look the same. It might be better to have each project have its own window settings.

This would be super confusing and also it will be quite annoying...

[BlueHazzard]

I have created a ticket for this https://sourceforge.net/p/codeblocks/tickets/770/
feel free to comment so you get notification as soon as we fix it...

[stahta01]

Suggested solution: I think the user should use cb_share_config to move the configs from one computer to another.

Does this problem exist when using cb_share_config?

If yes; then, I think that changes are needed in cb_share_config instead of changes in CB core program.

Tim S.

[BlueHazzard]

Suggested solution: I think the user should use cb_share_config to move the configs from one computer to another.

It is always a bug if the windows appear on an non existent display

[BlueHazzard]

I have posted a fix in the ticket. It would be cool if you can test it... But you have to compile c::b by yourself to test it...

[BlueHazzard]

fixed in trunk thank you for the report

[Miguel Gimenez]

There is a compilation error with wx3.1.2 because now wxDisplay has two constructors and both can match the call:

Code Select Expand

const wxDisplay currentDisplay(0);

should be

Code Select Expand

const wxDisplay currentDisplay;

[BlueHazzard]

What wx version version are you using? What operating system? It compiles fine for me windows wx30

[Miguel Gimenez]

Sorry, I have just edited my message. wx3.1.2 added a second constructor to wxDisplay.

[BlueHazzard]

Sorry, I have just edited my message. wx3.1.2 added a second constructor to wxDisplay.

i see.... Thank you. Fixed in trunk. I have switched my environment to wx312 for future builds