Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-02 Thread Sieghard
Hallo Martin, Du schriebst am Wed, 2 Jan 2013 07:40:47 +0100: But as I remarked even in my original remark, I'm too late anyway... I proposed the symbolic link for the OS-support directories too, nobody liked it IIRC. So it is better to rename them to avoid confusion. Did anybody _reject_

Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-02 Thread Sieghard
Hallo Martin, Du schriebst am Wed, 2 Jan 2013 07:18:47 +0100: I did not test recently but MSEide+MSEgui worked well and had a usable performance on my old AMD K6 machine with Windows 98 last time I tried. Interesting, when was that? How long ago? Half a year probabely is too long to be

Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-02 Thread Martin Schreiber
On Wednesday 02 January 2013 19:35:58 Sieghard wrote: Hallo Martin, Du schriebst am Wed, 2 Jan 2013 07:18:47 +0100: I did not test recently but MSEide+MSEgui worked well and had a usable performance on my old AMD K6 machine with Windows 98 last time I tried. Interesting, when was that?

Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-02 Thread Sieghard
Hallo Martin, Du schriebst am Wed, 2 Jan 2013 20:48:34 +0100: I don't understand, why is half a year too long to be relevant? Has MSEgui slowed down so much the last half year? I'm not aware of such a thing. But I got the impression that processing speed had increased quit a bit lately,

Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-01 Thread Graeme Geldenhuys
On 01/01/2013 18:41, Sieghard wrote: Indeed, that wouldn't do. So you're using mseide-msegui on a Windows 95, 98 or ME machine? What processor, and how's the performance? :-O My Windows development is done under Win2000 with NTFS and FAT32 partitions. Graeme.

Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-01 Thread Sieghard
Hallo Graeme, Du schriebst am Tue, 01 Jan 2013 19:16:09 +: My Windows development is done under Win2000 with NTFS and FAT32 partitions. So there's nothing that would keep you from installing mseide-msegui on a NTFS formatted partition (which supports links). That's conforming to my

Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-01 Thread Martin Schreiber
On Tuesday 01 January 2013 19:41:50 Sieghard wrote: Indeed, that wouldn't do. So you're using mseide-msegui on a Windows 95, 98 or ME machine? What processor, and how's the performance? :-O I did not test recently but MSEide+MSEgui worked well and had a usable performance on my old AMD K6

Re: [MSEide-MSEgui-talk] .mseide creation

2013-01-01 Thread Martin Schreiber
On Wednesday 02 January 2013 01:21:26 Sieghard wrote: Hallo Graeme, Du schriebst am Tue, 01 Jan 2013 19:16:09 +: My Windows development is done under Win2000 with NTFS and FAT32 partitions. So there's nothing that would keep you from installing mseide-msegui on a NTFS formatted

Re: [MSEide-MSEgui-talk] .mseide creation

2012-12-31 Thread Martin Schreiber
On Monday 31 December 2012 08:06:07 Martin Schreiber wrote: On Sunday 30 December 2012 19:44:57 Patrick Goupell wrote: Martin, When mseide does not find a .mseide/mseideli.sta file it creates one. When I click on Settings - Configure MSEide: On a 32 bit system it sets the compiler

Re: [MSEide-MSEgui-talk] .mseide creation

2012-12-31 Thread Sieghard
Hallo Martin, Du schriebst am Mon, 31 Dec 2012 09:42:10 +0100: i386-linux is a misleading directory name because lib/kernel/i386-linux ... git master 3e89711aa4783b32ffa63d601c550640c0866fb1 renamed Too late... You could have considered using links here - even Windows' NTFS provide them.

Re: [MSEide-MSEgui-talk] .mseide creation

2012-12-31 Thread Graeme Geldenhuys
On 31/12/12 19:15, Sieghard wrote: You could have considered using links here - even Windows' NTFS provide them. No, because MSEide doesn't dictate that NTFS is a requirement. FAT16 or FAT32 could be used too. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using

Re: [MSEide-MSEgui-talk] .mseide creation

2012-12-30 Thread Patrick Goupell
On 12/30/2012 01:44 PM, Patrick Goupell wrote: On my 64 bit system the compiler was set to ppcx86 and the target was set as i386-linux. Can that be set to x86_64-linux? Correction, that should say the compiler is set to ppcx64. Patrick

Re: [MSEide-MSEgui-talk] .mseide creation

2012-12-30 Thread Graeme Geldenhuys
On 30/12/12 18:44, Patrick Goupell wrote: On my 64 bit system the compiler was set to ppcx86 and the target was set as i386-linux. Can that be set to x86_64-linux? No, it must be i386-linux, because that is a hard-coded directory path. I've raised this issue years ago. If you change that,

Re: [MSEide-MSEgui-talk] .mseide creation

2012-12-30 Thread Patrick Goupell
On 12/30/2012 05:43 PM, Graeme Geldenhuys wrote: No, it must be i386-linux, because that is a hard-coded directory path. I've raised this issue years ago. If you change that, then msegui cannot compile. Annoying I know, so for my projects I had to setup custom platform macros, and can't

Re: [MSEide-MSEgui-talk] .mseide creation

2012-12-30 Thread Martin Schreiber
On Sunday 30 December 2012 19:44:57 Patrick Goupell wrote: Martin, When mseide does not find a .mseide/mseideli.sta file it creates one. When I click on Settings - Configure MSEide: On a 32 bit system it sets the compiler to ppc386 and target to i386-linux. On my 64 bit system the