RE: Another Code Oddity

Interesting!

I still use RLU for reports but usually use Designer for dspf for the same
reason you said - it's not stable enough.  But for me, designer crashes
always when I move fields when editing a printer file.  It's usually when I
move the last field in a record to another record.  And it's in these
instances that I lose source.

When I edit display files, I have learned to take it easy and save all the
time (like after each change to anything), and to make a backup of the
source member before I edit it.  I've also learned that if I select
file|save that the timer dialog box always increments and then goes away but
when I click the save button the dialog box doesn't always increment, and in
this case doesn't go away unless I click cancel.  At this point I get real
nervous and exit designer and restart.

Regarding scrolling, can you fix the annoying feature that prevents you from
using the scroll wheel on the mouse when the scroll bar isn't visible on the
screen?!  That's an annoying oddity.

Phil

> -----Original Message-----
> From: code400-l-admin@midrange.com
> [mailto:code400-l-admin@midrange.com]On Behalf Of John Taylor
> Sent: Wednesday, April 24, 2002 4:54 PM
> To: code400-l@midrange.com
> Subject: Re: Another Code Oddity
>
>
> Mark,
>
> > The number of these 'bugs' goes up in orders of magnitude in Designer.
>
> Agreed. The only thing I use Designer for is reports, because it's less
> painful than RLU. But I still find myself firing up SDA for screens. I
> prefer Designer over SDA, but it's just not stable enough yet.
> Way too many
> bugs.
>
>
> Regards,
>
> John Taylor