Jump to content

Matoyak

Members
  • Posts

    45
  • Joined

  • Last visited

Posts posted by Matoyak

  1. Guys, keep in mind that MOST of these glitches are PHPBB3's fault, NOT Rick's. He has almost no control over most of these problems, they are just minor glitches that come with PHPBB3 being in a Release Candidate state.

    I think no one says they are Rick's faults. But the sense of this topic is to post bugs and we are invited to do so by Rick himself. I as simple user don't know if I can provide help to detect and to solve bugs when I'm posting them, so I post them hoping it's support for other people.

    I know no one has yet t say it, I was just posting that as a preventative :D

    @Bob: And whether it is feature complete or not, quick reply is not included in phpbb from the get-go. Hence it being called a quick reply mod. there are a few QRMs in development, but thephpbb3 forum warns against using them until they are out of beta/alpha/RC stage. :S trust me, I'd love to have QRM back, meself...

  2. I really miss the quick reply box. When can we have that back?

    PhPbb3 Does not yet HAVE a quick reply mod. PhPbb3 is still in release candidate mode, in so far as I know, and even if it isn't, then there STILL isn't a quick reply mod for any phpbb3 forum out there, as of yet. So I guess we can get it back as soon as a nonbuggy, reliable, safe, Quick Reply Mod is made. Whenever that'll be.

  3. Quick Reply:

    -In the old forum, rather than having to click Reply in a thread, there was a Quick reply box in the bottom left corner that you could directly enter your post into.

    As far as I know, there are no quick reply mods for PhPBB3 forums, as bb3 just now either got out of release candidate mode or is still in. So that's not something Rick can fix, until one is made. We're having the same problem over at a forum I frequent very frequently.

  4. I have a stick of SDRAM 256 Megs. The crash happened after I clicked cancel. Like I said, I thought it was no big deal, it was just that my memory was overloaded most likely *shrug*, or that's what I thought. I'm slowly trying to build my own better computer but that'll take a while. If anybody knows a a really really good deal on a 512 stick of SDRAM or a Gig, even, on a reputable site, let me know. PLEASE. I just can't deal with the amount of ram I have anymore. It's absurd when Google Talk lags your computer.

  5. Paint Dot Net crashed on me the other day, but I felt it wasn't due to paint.net itself, and more due to the fact that I'd accidentally left it running on film effect for 3 hrs or more (like, I ran the effect, and had to go do something and forgot to click apply) :roll: But now I feel that, just in case, I might as well post the error log in a place that won't bog down somebody's email even more than it most likely already is.

    This text file was created because Paint.NET crashed.

    Please e-mail this file to paint.net@hotmail.com so we can diagnose and fix the problem.

    Application version: Paint.NET v3.10 (Beta Release build 3.10.2765.28557)

    Time of crash: 8/6/2007 9:56:07 PM

    Application uptime: 03:56:46.9687500

    OS Version: 5.1.2600.131072 Service Pack 2 Workstation x86

    .NET Framework version: 2.0.50727.832 x86

    Processor: 1x "IntelĀ® PentiumĀ® 4 CPU 1.60GHz" @ ~1594MHz (SSE, SSE2)

    Physical memory: 254 MB

    Tablet PC: no

    Locale: pdnr.c: en-US, hklm: en-US, hkcu: n/a, cc: en-US, cuic: en-US

    Exception details:

    System.NullReferenceException: Object reference not set to an instance of an object.

    at PaintDotNet.SystemLayer.PdnGraphics.GetRegionScans(Region region, Rectangle[]& scans, Int32& area)

    at PaintDotNet.PdnRegion.GetRegionScansReadOnlyInt()

    at PaintDotNet.Effects.Effect.Render(EffectConfigToken parameters, RenderArgs dstArgs, RenderArgs srcArgs, PdnRegion roi)

    at FilmEffect.FilmDialog.InitTokenFromDialog()

    at PaintDotNet.Effects.EffectConfigDialog.FinishTokenUpdate()

    at FilmEffect.FilmDialog.timer1_Tick(Object sender, EventArgs e)

    at System.Windows.Forms.Timer.OnTick(EventArgs e)

    at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

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

×
×
  • Create New...