KiCad

wxFormBbuilder version

Asked by Simon Huwyler

Hi,

I keep having trouble with wxFormBuilder. Whenever I open one of Kicad's .fbp files, I get a message telling me that the property "aui_manager_style" is not supported, that probably the file was created by a newer version, and it yells that "YOU WILL LOSE DATA" if I save the file.

If I create the code then, I get very strange artefacts that can't even be compiled. Reduplications of lines, closing braces where there are no opening ones and so on. But With the help of beyondCompare and the original C++ file, I can easily remove these hick-ups again and then everything is fine - including my changes to the dialog. But there are changes in the code that are not related to my changes in the dialog.

I tried the latest nightly build as well as the one that had been used to create the original C++ file (according to the comments at the top. The problem occurred on different (all, I suppose) dialogs, but namely on the layer setup dialog.

I'm working on Windows7 64 Bit

Does anyone have an idea what I could have done wrong?

Question information

Language:
English Edit question
Status:
Solved
For:
KiCad Edit question
Assignee:
No assignee Edit question
Solved by:
Simon Huwyler
Solved:
Last query:
Last reply:
Revision history for this message
Wayne Stambaugh (stambaughw) said : 		#1

I'm using version 3.3.4 beta on 64-bit Windows 7. I just tried to open a few fbp files and it appears to be working just fine. This is the latest version of the installer for Windows on the wxFormBuilder website and can be found here:

http://sourceforge.net/projects/wxformbuilder/files/wxformbuilder-nightly/3.3.04-beta/

Ubuntu users can get the latest version from the wxFormBuilder PPA at:

https://launchpad.net/~wxformbuilder/+archive/release

Perhaps someone is using an newer or custom version of wxFormBuilder built from source (I hope that's not the case) that is causing the problem and I just didn't open the right fbp file.

Revision history for this message
Simon Huwyler (simon-huwyler) said : 		#2

Thank you for your reply!

I had exacly the same version installed, the same OS and an actual testing
branch of Kicad.
What I did now is manually remove all files from FormBuilder's installation
folder and re-installing it again. Now it seems to work fine.

Best regards
Simon

-----Ursprüngliche Nachricht-----
From: Wayne Stambaugh
Sent: Wednesday, May 01, 2013 8:51 PM
To: <email address hidden>
Subject: Re: [Question #227926]: wxFormBbuilder version

Your question #227926 on KiCad changed:
https://answers.launchpad.net/kicad/+question/227926

    Status: Open => Answered

Wayne Stambaugh proposed the following answer:
I'm using version 3.3.4 beta on 64-bit Windows 7. I just tried to open
a few fbp files and it appears to be working just fine. This is the
latest version of the installer for Windows on the wxFormBuilder website
and can be found here:

http://sourceforge.net/projects/wxformbuilder/files/wxformbuilder-
nightly/3.3.04-beta/

Ubuntu users can get the latest version from the wxFormBuilder PPA at:

https://launchpad.net/~wxformbuilder/+archive/release

Perhaps someone is using an newer or custom version of wxFormBuilder
built from source (I hope that's not the case) that is causing the
problem and I just didn't open the right fbp file.

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/kicad/+question/227926/+confirm?answer_id=0

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/kicad/+question/227926

You received this question notification because you asked the question.

Revision history for this message
Simon Huwyler (simon-huwyler) said : 		#3

Oh no, because I answered to tell that it works now, the status is open again! sorry about that!

Revision history for this message
Travis Ayres (trayres) said : 		#4

I actually asked the same message on the list not long ago, and had the same issues! I am glad you fixed the issue for your installation; I will try to replicate your solution when I get home. Thanks Simon!