ftp.xmission.com/2014.06.ftp.xmission.com.tar/ftp.xmission.com/pub/lists/fractdev/archive/v01.n012

Internet Message Format | 1998-08-06 | 40KB

From: [e-mail] (fractdev-digest)
To: [e-mail]
Subject: fractdev-digest V1 #12
Reply-To: fractdev-digest
Sender: [e-mail]
Errors-To: [e-mail]
Precedence: bulk


fractdev-digest        Thursday, August 6 1998        Volume 01 : Number 012




----------------------------------------------------------------------

Date: Thu, 23 Jul 1998 21:29:59 -0400
From: Jonathan Osuch <[e-mail]>
Subject: Re: (fractdev) Fractint in dosemu

Kragen,

>> - When I select 800x600x256 from the DEL screen, it works properly, an=
d
dosemu says: vesa_set_SVGA_mode(): mode=3D0x5e.  But if I TAB to the info=

screen, then hit TAB again to get back to the picture, it doesn't print
that message, and it also doesn't redisplay the picture. <<

Have you tried using the textsafe=3Dsave option?

>> - Sometimes, in VESA mode, solid-guessing doesn't fill in the solids o=
n
some lines.  I'll see a fractal with big black cracks across it, with dot=
s
scattered in the cracks.  The cracks go away on later iterations; I menti=
on
this because it might be of help with other problems. <<

What happens with passes=3D1?  Could this be a periodicity problem?  Try
using the command periodicity=3D0.

>> I think this happens every time you try to browse images (with "L").  =
I
seem to remember that this used to crash the computer in real MS-DOS as
well.  Running fractint, hitting F3, and typing "L" makes it crash, too (=
in
dosemu, that is). <<

This may be fixed in the 19.6 developer's version.  Would you please run
Fractint with the debug=3D10000 command line option, and tell me what it
reports?   Also, it would be helpful to know how much memory is free on
your system (below 640K, expanded, extended).  Also, any other pertinent
information which may be useful. For example, a non-Intel CPU.

Jonathan

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Thu, 23 Jul 1998 23:43:19 -0400 (EDT)
From: [e-mail] (Kragen)
Subject: Re: (fractdev) Fractint in dosemu

On Thu, 23 Jul 1998, Jonathan Osuch wrote:
> Kragen,
> >> - When I select 800x600x256 from the DEL screen, it works properly, and
> dosemu says: vesa_set_SVGA_mode(): mode=0x5e.  But if I TAB to the info
> screen, then hit TAB again to get back to the picture, it doesn't print
> that message, and it also doesn't redisplay the picture. <<
>
> Have you tried using the textsafe=save option?

You know, I should have tried that right away, but I didn't think it
would help any -- I guess I misunderstood the problem it was supposed
to solve.  (I haven't read the textsafe documentation since probably
1994. :).  It works!  Thanks!

> >> - Sometimes, in VESA mode, solid-guessing doesn't fill in the solids on
> some lines.  I'll see a fractal with big black cracks across it, with dots
> scattered in the cracks.  The cracks go away on later iterations; I mention
> this because it might be of help with other problems. <<
>
> What happens with passes=1?  Could this be a periodicity problem?  Try
> using the command periodicity=0.

I'd think that, if it were a periodicity problem, the cracks would not
go away on later passes.  Indeed, fractint textsafe=save periodicity=0
continues to display the cracks.

> >> I think this happens every time you try to browse images (with "L").  I
> seem to remember that this used to crash the computer in real MS-DOS as
> well.  Running fractint, hitting F3, and typing "L" makes it crash, too (in
> dosemu, that is). <<
>
> This may be fixed in the 19.6 developer's version.

I'll probably grab 19.6 one of these days soon.

> Would you please run
> Fractint with the debug=10000 command line option, and tell me what it
> reports?

CPU type: 386  FPU type: 387  IIT FPU: 0  Video: 5  Video chip: 14 (vesa)

 1954 NEAR bytes free
 120928 FAR bytes free
 8612 STACK bytes free
 12680 used by HISTORY structure
 21600 video table used

> Also, it would be helpful to know how much memory is free on
> your system (below 640K, expanded, extended).  Also, any other pertinent
> information which may be useful. For example, a non-Intel CPU.

Some other pertinent information you might be interested in is at the
top of the message you were replying to.

My dosemu settings for amount of RAM available in unconventional ways follow:

# Memory.

dpmi 8192 # 1/4 of all RAM

# I don't think I'll actually use these:
xms 1024
ems 1024

The "1/4 of all RAM" comment refers to the fact that I actually have 32
megs in my machine, physically.

Thanks very much for your interest!  (Particularly since most of these
problems are probably in dosemu or OpenDOS, not Fractint.)

Kragen



- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 24 Jul 1998 21:32:56 -0400
From: Jonathan Osuch <[e-mail]>
Subject: Re: (fractdev) Fractint in dosemu

Kragen,

>> I'd think that, if it were a periodicity problem, the cracks would not=

go away on later passes.  Indeed, fractint textsafe=3Dsave periodicity=3D=
0
continues to display the cracks. <<

Ah, in that case, I'm clueless <G>.  Does this happen with the default
fractal types, or is it a specific zoom?  And, does this particular image=

generate okay on other machines?

>> I'll probably grab 19.6 one of these days soon. <<

I wouldn't count on 19.6 fixing the problem with the browser locking thin=
gs
up.  Although, using the textsafe=3Dsave option should at least let you s=
ee a
message displayed.  My experience has been that with Fractint using
expanded memory is more reliable than using extended memory.  The browser=

needs large amounts of memory, although you have enough far memory
available that it should work.

The developer's version (based on 19.6) has reworked the memory handling
routines such that calls for allocating memory for data structures should=

not fail.  At least, that's my hope.  The theory is that if one type of
memory is requested, but enough isn't available, the next type of memory
will be allocated (or attempted to be allocated).  The sequence is far,
expanded, extended, and then disk.  If you run out of disk space, you've
got big problems.  But, that isn't really a Fractint problem <G>.

I'd recommend using 4 - 8 MB of expanded memory for running Fractint.  Th=
is
will keep the browser happy.

>> Thanks very much for your interest!  (Particularly since most of these=

problems are probably in dosemu or OpenDOS, not Fractint.) <<

You're welcome.  You can never tell when something will flush out an
obscure bug.  Reports of problems are always welcome, especially with new=

and different environments.

Jonathan

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Mon, 27 Jul 98 16:57:11 -0700
From: Tim Gilman <[e-mail]>
Subject: (fractdev) An incredibly small bug

While coding up some Mac dialogs to fake the Basic Options screen, I came
across this:

Sound (no, yes, x, y, z)

But the arrow keys actually perform like this:

<->  yes  <->  no  <->  x  <->  y  <->  z  <->


More hard-hitting bug reports coming soon....   ;-P

- -= tim gilman
[e-mail]
[e-mail]

"There is no truth, in which passing through awareness, does not lie.
 Yet we chase after it all the same."

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Mon, 27 Jul 1998 21:19:23 -0400
From: Jonathan Osuch <[e-mail]>
Subject: Re: (fractdev) An incredibly small bug

Tim,

>>
Sound (no, yes, x, y, z)

But the arrow keys actually perform like this:

<->  yes  <->  no  <->  x  <->  y  <->  z  <->
<<

Got it, thanks.  I changed the prompt so it reads:

Sound (yes, no, x, y, z)

Jonathan

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Wed, 29 Jul 1998 10:50:24 -0400 (EDT)
From: [e-mail] (Kragen)
Subject: Re: (fractdev) Fractint in dosemu

Sorry it took so long for me to answer!

On Fri, 24 Jul 1998, Jonathan Osuch wrote:
> >> I'd think that, if it were a periodicity problem, the cracks would not
> go away on later passes.  Indeed, fractint textsafe=save periodicity=0
> continues to display the cracks. <<
>
> Ah, in that case, I'm clueless <G>.  Does this happen with the default
> fractal types, or is it a specific zoom?  And, does this particular image
> generate okay on other machines?

It seems to happen with all escape-time fractal types; I noticed it
first with mandel, zooming in on the crack between the main cardioid
and the big circle next to it.  It happens with lots of images, but not
necessarily all.

> >> I'll probably grab 19.6 one of these days soon. <<
>
> I wouldn't count on 19.6 fixing the problem with the browser locking things
> up.

You mean, when I try to do "L"?

> Although, using the textsafe=save option should at least let you see a
> message displayed.  My experience has been that with Fractint using
> expanded memory is more reliable than using extended memory.

I could turn off XMS without much trouble.  What about DPMI?  Does
Fractint support it?

> The browser
> needs large amounts of memory, although you have enough far memory
> available that it should work.

Well, it could just be a problem with dosemu's memory management --
although it *did* happen under raw DOS on the 5x86.  (I don't remember
whether it was MS-DOS or OpenDOS.)

> The developer's version (based on 19.6) has reworked the memory handling
> routines such that calls for allocating memory for data structures should
> not fail.  At least, that's my hope.  The theory is that if one type of
> memory is requested, but enough isn't available, the next type of memory
> will be allocated (or attempted to be allocated).  The sequence is far,
> expanded, extended, and then disk.  If you run out of disk space, you've
> got big problems.  But, that isn't really a Fractint problem <G>.

Heh :)

In dosemu, it's quite reasonable for me (on my 32M machine) to make 90M
available through EMS, XMS, or DPMI (provided those interfaces can
support such large amounts of memory -- can they?) and let Linux handle
swapping to disk.

> I'd recommend using 4 - 8 MB of expanded memory for running Fractint.  This
> will keep the browser happy.

OK, I'll try that.

> >> Thanks very much for your interest!  (Particularly since most of these
> problems are probably in dosemu or OpenDOS, not Fractint.) <<
>
> You're welcome.  You can never tell when something will flush out an
> obscure bug.  Reports of problems are always welcome, especially with new
> and different environments.

That's wonderful!

Kragen (who just read the Algorithmic Beauty of Plants, and is
salivating over the thought of rendering IFSes as escape-time fractals)


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Wed, 29 Jul 1998 15:43:02 -0400
From: Ron Barnett <[e-mail]>
Subject: (fractdev) test

I don't seem to be getting fractdev list mail. This is a test.

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Wed, 29 Jul 1998 21:34:52 -0400
From: Jonathan Osuch <[e-mail]>
Subject: Re: (fractdev) Fractint in dosemu

Kragen,

>> It seems to happen with all escape-time fractal types; I noticed it
first with mandel, zooming in on the crack between the main cardioid
and the big circle next to it.  It happens with lots of images, but not
necessarily all. <<

Would it be a problem for you to email me a small GIF illustrating the
problem?  Is this only a problem with solid guessing?  Is the final image=

affected?  Is the crack vertical or horizontal?  What happens if you use
"symmetry=3Dno"?

>> > >> I'll probably grab 19.6 one of these days soon. <<
> =

> I wouldn't count on 19.6 fixing the problem with the browser locking
things
> up.  =


You mean, when I try to do "L"?
<<

Yes, pressing "L" invokes the browser unless you are in color cycling or
the palette editor.

>> What about DPMI?  Does Fractint support it? <<

Not at present, and I think DPMI support is way beyond my skills.

>> In dosemu, it's quite reasonable for me (on my 32M machine) to make 90=
M
available through EMS, XMS, or DPMI (provided those interfaces can
support such large amounts of memory -- can they?) and let Linux handle
swapping to disk. <<

I don't know what the limits are.

Jonathan

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Thu, 30 Jul 1998 21:21:43 -0400
From: Jonathan Osuch <[e-mail]>
Subject: Re: (fractdev) Fractint in dosemu

Kragen,

>> Here's a 13K GIF.  It was generated by xv, not fractint, and it
illustrates some problems erasing the zoom box, the "problem" in which
parts of the old image are not erased until the drawing process reaches
them, and the horizontal-crack problems. <<

That's an interesting image.  What video adapter are you using?  Because
this happens with more than one program, the video adapter might be causi=
ng
the problem.  Depending on your video adapter, what happens when you forc=
e
the detection with the command line adapter=3Dxxxx?  This should prevent =
the
use of the VESA routines.

>> >  Is the final image affected?

Interestingly, no, not at all.
<<

That pixel data has to be going somewhere.  Perhaps what is happening is
that we are crossing a boundary when we are doing the pixel write.  Some =
of
the pixels get written because they are on the correct side of the
boundary.  Do the cracks always appear in the same location on the screen=
?

>> >  What happens if you use "symmetry=3Dno"?

Where do I use that? <<

Either on the command line or by pressing the <g> key.

Jonathan

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 02:03:24 -0400
From: "Peter Gavin" <[e-mail]>
Subject: (fractdev) C complex types

This is a multi-part message in MIME format.

- ------=_NextPart_000_0001_01BDBC27.666E6820
Content-Type: text/plain;
    charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I know this probably sounds really stupid, but it's the *only* thing in =
C that confuses me...  Can someone explain to me how I can interpret and =
create variable types such as:

const int * const annoying[3];

I want to make an array of constant pointers to constant chars, such as:

typedef const char /* a bunch of confusing stuff */ stupid;

stupid adjectives =3D { "idiot", "moron", "Bill Gates" }

Now, as you can see, the 3 strings are constant, but varying length, so =
I want an array of 3 pointers to characters.  The pointers are constant, =
as are the characters.  How the @#$% do I do this? <g>
(I know this is somewhat unnecessary [I suppose using char ** would =
work] but I want to prevent all modifications, since the strings are to =
be global. I also want to learn how to do this without using typedefs =
since alot of people do and I'll need to figure this out eventually.)

Peter Gavin
<[e-mail]>

// End transmission



- ------=_NextPart_000_0001_01BDBC27.666E6820
Content-Type: text/html;
    charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D600004805-31071998><FONT color=3D#000000 =
face=3DVerdana size=3D2>I=20
know this probably sounds really stupid, but it's the *only* thing in C =
that=20
confuses me...  Can someone explain to me how I can interpret and =
create=20
variable types such as:</FONT></SPAN></DIV>
<DIV><SPAN class=3D600004805-31071998><FONT color=3D#000000 =
face=3DVerdana=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D600004805-31071998><FONT size=3D2><FONT =
face=3D"Courier New"><FONT=20
color=3D#000000>const int * const =
annoying[3];</FONT></FONT></FONT></SPAN><FONT=20
color=3D#000000><FONT face=3D"Courier New"><FONT =
size=3D2></FONT></FONT></FONT></DIV>
<DIV><SPAN class=3D600004805-31071998><FONT color=3D#000000 =
face=3DVerdana=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D600004805-31071998><FONT color=3D#000000 =
face=3DVerdana size=3D2>I=20
want to make an array of constant pointers to constant chars, such=20
as:</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=3D600004805-31071998><FONT size=3D2><FONT =
face=3D"Courier New"><FONT=20
color=3D#000000>typedef const char /* a bunch of confusing stuff */=20
stupid;</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D600004805-31071998><FONT size=3D2><FONT =
face=3D"Courier New"><FONT=20
color=3D#000000></FONT></FONT></FONT></SPAN><FONT color=3D#000000><FONT=20
face=3D"Courier New"><FONT size=3D2></FONT></FONT></FONT> </DIV>
<DIV><SPAN class=3D600004805-31071998><FONT color=3D#000000 =
face=3D"Courier New"=20
size=3D2>stupid adjectives =3D { "idiot", "moron", =
"Bill=20
Gates" }</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><FONT color=3D#000000 face=3D"Courier New" size=3D2></FONT><SPAN=20
class=3D600004805-31071998><FONT color=3D#000000 face=3DVerdana =
size=3D2>Now, as you can=20
see, the 3 strings are constant, but varying length, so I want an array =
of 3=20
pointers to characters.  The pointers are constant, as are the=20
characters.  How the @#$% do I do this? =
<g></FONT></SPAN></DIV>
<DIV><SPAN class=3D600004805-31071998><FONT color=3D#000000 =
face=3DVerdana size=3D2>(I=20
know this is somewhat unnecessary [I suppose using char ** would work] =
but I=20
want to prevent all modifications, since the strings are to be global. I =
also=20
want to learn how to do this without using typedefs since alot of people =
do and=20
I'll need to figure this out eventually.)</FONT></SPAN></DIV>
<P><FONT face=3D"" size=3D2><BR>Peter Gavin<BR><<A=20
href=3D"mailto:[e-mail]">[e-mail]</A>><BR><B=
R><EM><FONT=20
face=3D"" size=3D1>// End transmission</FONT></EM></FONT></P>
<DIV> </DIV></BODY></HTML>

- ------=_NextPart_000_0001_01BDBC27.666E6820--


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 10:37:12 -0400 (EDT)
From: [e-mail] (Kragen)
Subject: Re: (fractdev) C complex types

On Fri, 31 Jul 1998, Peter Gavin wrote:
> I want to make an array of constant pointers to constant chars, such as:
>
> typedef const char /* a bunch of confusing stuff */ stupid;
>
> stupid adjectives = { "idiot", "moron", "Bill Gates" }

IIRC, there's 'char const *x' (which is the same as const char *x) and
then there's 'char * const x', which means that x is const, although
what it points to may not be.

I think what you want is an array of 'char const * const'.  So you can say:
typedef char const * const stupid;
stupid adjective = "stupid";
stupid adjectives[] = { "de Raadt", "Randy Loux", NULL};

and get what you want.

But I don't use const much, so all that could be wrong.

Kragen


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 12:05:59 -0400 (EDT)
From: [e-mail] (Kragen)
Subject: Re: (fractdev) Fractint in dosemu

On Thu, 30 Jul 1998, Jonathan Osuch wrote:
> Kragen,
>
> >> Here's a 13K GIF.  It was generated by xv, not fractint, and it
> illustrates some problems erasing the zoom box, the "problem" in which
> parts of the old image are not erased until the drawing process reaches
> them, and the horizontal-crack problems. <<
>
> That's an interesting image.  What video adapter are you using?  Because
> this happens with more than one program, the video adapter might be causing
> the problem.

I'm running dosemu in X-windows on a Cirrus Logic CLGD5446.  While it's
possible it might be the video adapter, I believe it's more likely to
be dosemu.  I haven't seen it with any other programs (in dosemu or
otherwise).

>  Depending on your video adapter, what happens when you force
> the detection with the command line adapter=xxxx?  This should prevent the
> use of the VESA routines.

I'm not sure what xxxx should be.

> >> >  Is the final image affected?
>
> Interestingly, no, not at all.
> <<
>
> That pixel data has to be going somewhere.  Perhaps what is happening is
> that we are crossing a boundary when we are doing the pixel write.  Some of
> the pixels get written because they are on the correct side of the
> boundary.  Do the cracks always appear in the same location on the screen?

Well, I'm not sure.  But they do disappear on later passes.

> >> >  What happens if you use "symmetry=no"?
>
> Where do I use that? <<
>
> Either on the command line or by pressing the <g> key.

I tried both.  It said it didn't know what I was talking about.

Kragen


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 12:05:59 -0400 (EDT)
From: [e-mail] (Kragen)
Subject: Re: (fractdev) Fractint in dosemu

On Thu, 30 Jul 1998, Jonathan Osuch wrote:
> Kragen,
>
> >> Here's a 13K GIF.  It was generated by xv, not fractint, and it
> illustrates some problems erasing the zoom box, the "problem" in which
> parts of the old image are not erased until the drawing process reaches
> them, and the horizontal-crack problems. <<
>
> That's an interesting image.  What video adapter are you using?  Because
> this happens with more than one program, the video adapter might be causing
> the problem.

I'm running dosemu in X-windows on a Cirrus Logic CLGD5446.  While it's
possible it might be the video adapter, I believe it's more likely to
be dosemu.  I haven't seen it with any other programs (in dosemu or
otherwise).

>  Depending on your video adapter, what happens when you force
> the detection with the command line adapter=xxxx?  This should prevent the
> use of the VESA routines.

I'm not sure what xxxx should be.

> >> >  Is the final image affected?
>
> Interestingly, no, not at all.
> <<
>
> That pixel data has to be going somewhere.  Perhaps what is happening is
> that we are crossing a boundary when we are doing the pixel write.  Some of
> the pixels get written because they are on the correct side of the
> boundary.  Do the cracks always appear in the same location on the screen?

Well, I'm not sure.  But they do disappear on later passes.

> >> >  What happens if you use "symmetry=no"?
>
> Where do I use that? <<
>
> Either on the command line or by pressing the <g> key.

I tried both.  It said it didn't know what I was talking about.

Kragen


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 11:31:33 -0600
From: Phil McRevis <[e-mail]>
Subject: Re: (fractdev) C complex types

In article <000001bdbc48$ed76e060$ea83cdcf@p60>,
    "Peter Gavin" <[e-mail]>  writes:
> I want to make an array of constant pointers to constant chars, such as:
>
> typedef const char /* a bunch of confusing stuff */ stupid;
>
> stupid adjectives =3D { "idiot", "moron", "Bill Gates" }

gcc accepted this perfectly fine:

    const char *const adjectives[3] = { "one", "two", "three" };

did you try that?  This is a const character string:

    const char *constant_string = "initializer";

That says the characters themselves can't be changed, but the pointer
can be changed, i.e. "constant_string++" is valid.  This is a constant
pointer to a constant character string:

    const char *const constant_ptr_to_constant_string = "initializer";

Since you want an array of these strings, just make it an array and
provide an aggregate initializer as in the first example above.  If
the first example doesn't work, I'd begin suspecting your compiler.  I
just tried it on Borland C++ Builder 1.0 on my PC and that also
accepted the construct.
- --
http://www.xmission.com/~legalize/    Legalize Adulthood!
[e-mail]
``Ain't it funny that they all fire the pistol,     <URL: http://
  at the wrong end of the race?''--PDBT     www.eden.com/~thewho>

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 22:35:15 +0200
From: "Dean-Christian Strik" <[e-mail]>
Subject: Re: (fractdev) Fractint in dosemu

Kragen,

:> >> >  What happens if you use "symmetry=no"?
:>
:> Where do I use that? <<
:>
:> Either on the command line or by pressing the <g> key.
:
:I tried both.  It said it didn't know what I was talking about.


It should be "symmetry=none".

Christian




- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 20:10:41 -0400
From: "Peter Gavin" <[e-mail]>
Subject: RE: (fractdev) C complex types

Okay... I have something equivalent to this: (I'm using VC++ 4, BTW)

class stupid {
private:
    static const wchar_t * const adjectives[];
};

const wchar_t * const stupid::adjectives[] = { _T("one"), _T("two"),
_T("three") };

It may be the fact that it's a static class member thats messing it up...  I
get
this as a complaint: "error C2230: 'initializing' : indirection to different
types".

Any ideas?



Pete
<[e-mail]>

//  -----Original Message-----
//  From: [e-mail]
//  [mailto:[e-mail]]On Behalf Of Phil McRevis
//  Sent: Friday, July 31, 1998 1:32 PM
//  To: [e-mail]
//  Subject: Re: (fractdev) C complex types
//
//
//
//  In article <000001bdbc48$ed76e060$ea83cdcf@p60>,
//      "Peter Gavin" <[e-mail]>  writes:
//  > I want to make an array of constant pointers to constant
//  chars, such as:
//  >
//  > typedef const char /* a bunch of confusing stuff */ stupid;
//  >
//  > stupid adjectives =3D { "idiot", "moron", "Bill Gates" }
//
//  gcc accepted this perfectly fine:
//
//      const char *const adjectives[3] = { "one", "two", "three" };
//
//  did you try that?  This is a const character string:
//
//      const char *constant_string = "initializer";
//
//  That says the characters themselves can't be changed, but the pointer
//  can be changed, i.e. "constant_string++" is valid.  This is a constant
//  pointer to a constant character string:
//
//      const char *const constant_ptr_to_constant_string = "initializer";
//
//  Since you want an array of these strings, just make it an array and
//  provide an aggregate initializer as in the first example above.  If
//  the first example doesn't work, I'd begin suspecting your compiler.  I
//  just tried it on Borland C++ Builder 1.0 on my PC and that also
//  accepted the construct.
//  --
//  http://www.xmission.com/~legalize/    Legalize Adulthood!
//  [e-mail]
//  ``Ain't it funny that they all fire the pistol,     <URL: http://
//    at the wrong end of the race?''--PDBT     www.eden.com/~thewho>
//
//  --------------------------------------------------------------
//  Thanks for using Fractdev, The Fractint Developer's Discussion List
//  Post Message:   [e-mail]
//  Get Commands:   [e-mail] "help"
//  Administrator:  [e-mail]
//  Unsubscribe:    [e-mail] "unsubscribe fractdev"
//


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 20:13:46 -0400
From: "Peter Gavin" <[e-mail]>
Subject: RE: (fractdev) C complex types

Geez, I'm an idiot...  it was the stupid _T() macro...  forgive me, please?
:)



Pete
<[e-mail]>

//  -----Original Message-----
//  From: [e-mail]
//  [mailto:[e-mail]]On Behalf Of Phil McRevis
//  Sent: Friday, July 31, 1998 1:32 PM
//  To: [e-mail]
//  Subject: Re: (fractdev) C complex types
//
//
//
//  In article <000001bdbc48$ed76e060$ea83cdcf@p60>,
//      "Peter Gavin" <[e-mail]>  writes:
//  > I want to make an array of constant pointers to constant
//  chars, such as:
//  >
//  > typedef const char /* a bunch of confusing stuff */ stupid;
//  >
//  > stupid adjectives =3D { "idiot", "moron", "Bill Gates" }
//
//  gcc accepted this perfectly fine:
//
//      const char *const adjectives[3] = { "one", "two", "three" };
//
//  did you try that?  This is a const character string:
//
//      const char *constant_string = "initializer";
//
//  That says the characters themselves can't be changed, but the pointer
//  can be changed, i.e. "constant_string++" is valid.  This is a constant
//  pointer to a constant character string:
//
//      const char *const constant_ptr_to_constant_string = "initializer";
//
//  Since you want an array of these strings, just make it an array and
//  provide an aggregate initializer as in the first example above.  If
//  the first example doesn't work, I'd begin suspecting your compiler.  I
//  just tried it on Borland C++ Builder 1.0 on my PC and that also
//  accepted the construct.
//  --
//  http://www.xmission.com/~legalize/    Legalize Adulthood!
//  [e-mail]
//  ``Ain't it funny that they all fire the pistol,     <URL: http://
//    at the wrong end of the race?''--PDBT     www.eden.com/~thewho>
//
//  --------------------------------------------------------------
//  Thanks for using Fractdev, The Fractint Developer's Discussion List
//  Post Message:   [e-mail]
//  Get Commands:   [e-mail] "help"
//  Administrator:  [e-mail]
//  Unsubscribe:    [e-mail] "unsubscribe fractdev"
//


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 21:40:08 -0400
From: Jonathan Osuch <[e-mail]>
Subject: Re: (fractdev) Fractint in dosemu

Kragen,

>> I'm running dosemu in X-windows on a Cirrus Logic CLGD5446.  While it'=
s
possible it might be the video adapter, I believe it's more likely to be
dosemu.  I haven't seen it with any other programs (in dosemu or
otherwise).

>  Depending on your video adapter, what happens when you force
> the detection with the command line adapter=3Dxxxx?  This should preven=
t
the
> use of the VESA routines.

I'm not sure what xxxx should be.
<<

Yes, I see the problem.  First, try: adapter=3Dvga.  This will limit Frac=
tint
to only vga modes, but if it works okay, it's a clue to where the problem=

may lie.

Then, try: vesadetect=3Dno

This second should autodetect your video card.  For some reason we didn't=

implement adapter=3Dcirrus.

>> > >> >  What happens if you use "symmetry=3Dno"?
> =

> Where do I use that? <<
> =

> Either on the command line or by pressing the <g> key.

I tried both.  It said it didn't know what I was talking about.
<<

Sorry, my fault.  As Christian pointed out, it should be symmetry=3Dnone.=


Jonathan

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Fri, 31 Jul 1998 22:34:06 -0400 (EDT)
From: [e-mail] (Kragen)
Subject: RE: (fractdev) C complex types

On Fri, 31 Jul 1998, Peter Gavin wrote:
> Geez, I'm an idiot...  it was the stupid _T() macro...  forgive me, please?
> :)

Lemme guess... you didn't define UNICODE, so _T("") was a const char *,
not a const wchar_t *?

Kragen


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Mon, 3 Aug 98 15:30:55 -0700
From: Tim Gilman <[e-mail]>
Subject: (fractdev) type-specific parameters question

I'm doing some dynamic dialog building for the type-specific parameters
screen, and it looks like 30 is the maximum number of prompts.  Does
anyone know if any formulas actually use this many prompts?  If none do,
does anyone know what the ceiling value is?

I don't want to get into dynamic window-resizing at this point, but I
also don't want to have a massive, full-screen dialog...

- -= tim gilman
[e-mail]
[e-mail]

- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Tue, 4 Aug 1998 10:04:27 -0700
From: "darryl" <[e-mail]>
Subject: RE: (fractdev) type-specific parameters question

Tim Gilman wrote:

I'm doing some dynamic dialog building for the type-specific parameters
screen, and it looks like 30 is the maximum number of prompts.  Does
anyone know if any formulas actually use this many prompts?  If none do,
does anyone know what the ceiling value is?

I don't want to get into dynamic window-resizing at this point, but I
also don't want to have a massive, full-screen dialog...

- ---

I went down that road, too ... and quickly determined that dynamic sizing
was the only viable method for displaying all of those parameters. It does
get easier once you've done it :)


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

Date: Thu, 6 Aug 1998 20:26:06 -0400
From: "Peter Gavin" <[e-mail]>
Subject: RE: (fractdev) C complex types

Yep...  actually, I _should_ have used _TCHAR instead of wchar_t, so I
wouldn't have to worry about defines and stuff.



Pete
<[e-mail]>

//  -----Original Message-----
//  From: [e-mail]
//  [mailto:[e-mail]]On Behalf Of Kragen
//  Sent: Friday, July 31, 1998 10:34 PM
//  To: [e-mail]
//  Subject: RE: (fractdev) C complex types
//
//
//  On Fri, 31 Jul 1998, Peter Gavin wrote:
//  > Geez, I'm an idiot...  it was the stupid _T() macro...
//  forgive me, please?
//  > :)
//
//  Lemme guess... you didn't define UNICODE, so _T("") was a const char *,
//  not a const wchar_t *?
//
//  Kragen
//
//
//  --------------------------------------------------------------
//  Thanks for using Fractdev, The Fractint Developer's Discussion List
//  Post Message:   [e-mail]
//  Get Commands:   [e-mail] "help"
//  Administrator:  [e-mail]
//  Unsubscribe:    [e-mail] "unsubscribe fractdev"
//


- --------------------------------------------------------------
Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"

------------------------------

End of fractdev-digest V1 #12
*****************************