wxlua-users

[Wxlua-users] Problems with wxStEdit on Linux

[Francesco M. <f18...@ya...>]

Hi John,
    maybe the right place to post this would be wxCode mailing list but 
since it also regards wxLua I'm posting it here...

Nor the wxStEdit CVS nor the archive I've downloaded from SF contain the 
configure script. That was easy for me to fix but probably not for the 
generic user which has not passed the last months experimenting with 
bakefile and autoconf :)
So I suggest to generate it and add it to CVS.

Second, I've got problems about missing wx/stedit/setup.h file; I copied 
setup0.h in setup.h and solved this. Should this file be generated by 
the configure script ?

Last, I have problems with the usual void* -> int conversions which on 
64bit machines like mine are not valid.

Since I have access to wxCode CVS, I could check in the required changes...

All of this regards wxLua because I need to compile and install wxStEdit 
in order to check if wxLua configure script successfully finds it ;)

Francesco

Re: [Wxlua-users] Problems with wxStEdit on Linux

[John L. <jla...@gm...>]

On 2/8/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi John,
>     maybe the right place to post this would be wxCode mailing list but
> since it also regards wxLua I'm posting it here...
>
> Nor the wxStEdit CVS nor the archive I've downloaded from SF contain the
> configure script. That was easy for me to fix but probably not for the
> generic user which has not passed the last months experimenting with
> bakefile and autoconf :)
> So I suggest to generate it and add it to CVS.

If you could do this easily it would be great. I just copied the
bakefile stuff for wxStEdit from one of your projects a long time ago
and haven't updated them since.

> Second, I've got problems about missing wx/stedit/setup.h file; I copied
> setup0.h in setup.h and solved this. Should this file be generated by
> the configure script ?

It's one of those things where the user should set it up the way they
like. I don't want to put it into CVS since it'll just get overwritten
and be annoying. I suppose that configure could just copy it for
people.

> Last, I have problems with the usual void* -> int conversions which on
> 64bit machines like mine are not valid.
>
> Since I have access to wxCode CVS, I could check in the required changes.=
..

Please do, I can't think of where this would be in wxStEdit off the
top of my head.

> All of this regards wxLua because I need to compile and install wxStEdit
> in order to check if wxLua configure script successfully finds it ;)

Thanks,
    John Labenski

[Wxlua-users] Re: Problems with wxStEdit on Linux

[Francesco M. <f18...@ya...>]

John Labenski ha scritto:
> On 2/8/06, Francesco Montorsi <f18...@ya...> wrote:
>> Hi John,
>>     maybe the right place to post this would be wxCode mailing list but
>> since it also regards wxLua I'm posting it here...
>>
>> Nor the wxStEdit CVS nor the archive I've downloaded from SF contain the
>> configure script. That was easy for me to fix but probably not for the
>> generic user which has not passed the last months experimenting with
>> bakefile and autoconf :)
>> So I suggest to generate it and add it to CVS.
> 
> If you could do this easily it would be great. I just copied the
> bakefile stuff for wxStEdit from one of your projects a long time ago
> and haven't updated them since.
done




>> Second, I've got problems about missing wx/stedit/setup.h file; I copied
>> setup0.h in setup.h and solved this. Should this file be generated by
>> the configure script ?
> 
> It's one of those things where the user should set it up the way they
> like. I don't want to put it into CVS since it'll just get overwritten
> and be annoying. I suppose that configure could just copy it for
> people.
updated configure to do it



>> Last, I have problems with the usual void* -> int conversions which on
>> 64bit machines like mine are not valid.
>>
>> Since I have access to wxCode CVS, I could check in the required changes...
> 
> Please do, I can't think of where this would be in wxStEdit off the
> top of my head.
you can see them in cvs diffs ;)


I'm currently stopped by errors about include paths like:


#include "../../contrib/src/stc/scintilla/include/Platform.h" // for 
PRectangle
#include "../../contrib/src/stc/scintilla/include/PropSet.h"  // for SString


which refer to non-existent files in my wxCode tree.
These should be really transformed into something else...
unfortunately I checked the wxWidgets contrib section and I've found 
that on Unix scintilla headers are not installed anywhere...

so my proposed fix is:
1) on win32, add the %WXWIN%/contrib/src/stc/scintilla/include path
2) on unix, add a check for these headers. If they are not available, 
tell the user to use the --with-wxdir option to indicate the full path 
of the wxWidgets source tree and use it to install scintilla headers.
Or else, ask the wxdev to add scintilla headers to install rules.


Francesco

Re: [Wxlua-users] Re: Problems with wxStEdit on Linux

[John L. <jla...@gm...>]

On 2/8/06, Francesco Montorsi <f18...@ya...> wrote:
> > If you could do this easily it would be great. I just copied the
> > bakefile stuff for wxStEdit from one of your projects a long time ago
> > and haven't updated them since.
> done
>
> >> Second, I've got problems about missing wx/stedit/setup.h file; I copi=
ed
> >> setup0.h in setup.h and solved this. Should this file be generated by
> >> the configure script ?
> >
> > It's one of those things where the user should set it up the way they
> > like. I don't want to put it into CVS since it'll just get overwritten
> > and be annoying. I suppose that configure could just copy it for
> > people.
> updated configure to do it
>
> >> Last, I have problems with the usual void* -> int conversions which on
> >> 64bit machines like mine are not valid.
> >>
> >> Since I have access to wxCode CVS, I could check in the required chang=
es...
> >
> > Please do, I can't think of where this would be in wxStEdit off the
> > top of my head.
> you can see them in cvs diffs ;)

Thanks.

> I'm currently stopped by errors about include paths like:
>
> #include "../../contrib/src/stc/scintilla/include/Platform.h" // for
> PRectangle
> #include "../../contrib/src/stc/scintilla/include/PropSet.h"  // for SStr=
ing
>
> which refer to non-existent files in my wxCode tree.
> These should be really transformed into something else...
> unfortunately I checked the wxWidgets contrib section and I've found
> that on Unix scintilla headers are not installed anywhere...
>
> so my proposed fix is:
> 1) on win32, add the %WXWIN%/contrib/src/stc/scintilla/include path
> 2) on unix, add a check for these headers. If they are not available,
> tell the user to use the --with-wxdir option to indicate the full path
> of the wxWidgets source tree and use it to install scintilla headers.
> Or else, ask the wxdev to add scintilla headers to install rules.

3) I removed the dependence on them by just copying the needed class
declarations from the scintilla headers. :) (the license is ok with
that)

I started working on this before and I thought I changed some things,
but maybe I never committed them. Anyway all the #includes are gone
now. I'm trying to keep the code as similar as possible to the
original since some of the export functions are not trivial.

Thanks
    John Labenski

[Wxlua-users] Re: Problems with wxStEdit on Linux

[Francesco M. <f18...@ya...>]

Hi,

John Labenski ha scritto:
>> I'm currently stopped by errors about include paths like:
>>
>> #include "../../contrib/src/stc/scintilla/include/Platform.h" // for
>> PRectangle
>> #include "../../contrib/src/stc/scintilla/include/PropSet.h"  // for SString
>>
>> which refer to non-existent files in my wxCode tree.
>> These should be really transformed into something else...
>> unfortunately I checked the wxWidgets contrib section and I've found
>> that on Unix scintilla headers are not installed anywhere...
>>
>> so my proposed fix is:
>> 1) on win32, add the %WXWIN%/contrib/src/stc/scintilla/include path
>> 2) on unix, add a check for these headers. If they are not available,
>> tell the user to use the --with-wxdir option to indicate the full path
>> of the wxWidgets source tree and use it to install scintilla headers.
>> Or else, ask the wxdev to add scintilla headers to install rules.
> 
> 3) I removed the dependence on them by just copying the needed class
> declarations from the scintilla headers. :) (the license is ok with
> that)
> 
> I started working on this before and I thought I changed some things,
> but maybe I never committed them. Anyway all the #includes are gone
> now. I'm trying to keep the code as similar as possible to the
> original since some of the export functions are not trivial.
much better and simpler solution ;)

Now the configure script of wxStEdit successfully compiles it.
However I have to report a bug in samples/stedit program: when I run it 
and type something in the first row of untitled.txt, everything is okay.
When I hit enter to go in the row below, any key pressed is just ignored 
and nothing appears on the screen...
This is with Ubuntu 5.10, GTK2, wxCVS (maybe a little outdated - I'll 
update it...).

Francesco

Re: [Wxlua-users] Re: Problems with wxStEdit on Linux

[John L. <jla...@gm...>]

On 2/9/06, Francesco Montorsi <f18...@ya...> wrote:
> Now the configure script of wxStEdit successfully compiles it.
> However I have to report a bug in samples/stedit program: when I run it
> and type something in the first row of untitled.txt, everything is okay.
> When I hit enter to go in the row below, any key pressed is just ignored
> and nothing appears on the screen...
> This is with Ubuntu 5.10, GTK2, wxCVS (maybe a little outdated - I'll
> update it...).

This was a bug w/ wxWidgets CVS HEAD a few weeks back. It was some
unicode translation thing they were trying, hopefully it still works.

John Labenski

[Wxlua-users] Re: Problems with wxStEdit on Linux

[Francesco M. <f18...@ya...>]

John Labenski ha scritto:
> On 2/9/06, Francesco Montorsi <f18...@ya...> wrote:
>> Now the configure script of wxStEdit successfully compiles it.
>> However I have to report a bug in samples/stedit program: when I run it
>> and type something in the first row of untitled.txt, everything is okay.
>> When I hit enter to go in the row below, any key pressed is just ignored
>> and nothing appears on the screen...
>> This is with Ubuntu 5.10, GTK2, wxCVS (maybe a little outdated - I'll
>> update it...).
> 
> This was a bug w/ wxWidgets CVS HEAD a few weeks back. It was some
> unicode translation thing they were trying, hopefully it still works.
you're right; I've tested it with an updated wxWidgets and the problem 
has disappeared.

Francesco