Re: Help with building from source 4.0.6

------=_Part_2748_1762850236.1561567676875
Content-Type: multipart/alternative; 
	boundary="----=_Part_2749_1790468289.1561567676875"

------=_Part_2749_1790468289.1561567676875
Content-Type: text/plain; charset="UTF-8"

Sorry for the late reply. I took your advice and used a tarball. Everything 
worked perfectly and I was able to build. The reason I wanted to do this is 
due to the changes with accessible. I thought changing 
the flags["wxUSE_ACCESSIBILITY"] = "1" to 0 would solve my problem but it 
did not. For my purposes I am using the accessible properties of the 
elements. When 4.0.4 these properties were changed so I switched all of my 
code to the new property values. With the release of 4.1.0, the 
functionality will go back to before 4.0.3 so all of my changes will need 
to be reverted. 

I am looking for a way around this. I thought turning off that flag would 
not revert the way accessible works, but it still did. Any insight would be 
appreciated. If there is some changes I can make in the source code to 
prevent the old(before 4.0.4) functionality from returning when 4.1.0 
releases that would be great. 

Thanks.

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/wxPython-dev/881ddca9-0113-4cfb-8b49-822002f02e25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

------=_Part_2749_1790468289.1561567676875
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry for the late reply. I took your advice and used a ta=
rball. Everything worked perfectly and I was able to build. The reason I wa=
nted to do this is due to the changes with accessible. I thought changing t=
he=C2=A0flags[&quot;wxUSE_ACCESSIBILITY&quot;] =3D &quot;1&quot; to 0 would=
 solve my problem but it did not. For my purposes I am using the accessible=
 properties of the elements. When 4.0.4 these properties were changed so I =
switched all of my code to the new property values. With the release of 4.1=
.0, the functionality will go back to before 4.0.3 so all of my changes wil=
l need to be reverted.=C2=A0<div><br></div><div>I am looking for a way arou=
nd this. I thought turning off that flag would not revert the way accessibl=
e works, but it still did. Any insight would be appreciated. If there is so=
me changes I can make in the source code to prevent the old(before 4.0.4) f=
unctionality from returning when 4.1.0 releases that would be great.=C2=A0<=
/div><div><br></div><div>Thanks.</div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;wxPython-dev&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">wxPyth=
[email protected]</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/wxPython-dev/881ddca9-0113-4cfb-8b49-822002f02e25%40googlegroups=
.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/ms=
gid/wxPython-dev/881ddca9-0113-4cfb-8b49-822002f02e25%40googlegroups.com</a=
>.<br />
For more options, visit <a href=3D"https://groups.google.com/d/optout">http=
s://groups.google.com/d/optout</a>.<br />

------=_Part_2749_1790468289.1561567676875--

------=_Part_2748_1762850236.1561567676875--