Facepunch Desktop Application

[Zeb Brown]

Ok, what's so bad about it?

[ZeekyHBomb]

Nothing. ShaRose just accidentally bumped, while he wanted automerge to merge his post.

[ShaRose]

Fucking lazy automerge.

Also, it's great! I've made my own implementation of events (and I finally succumbed to importing windows.forms) so that if you add a delegate on thread B, even though the ticker runs on thread C or D or whatever it is, your results will show up on thread B! That means that if you are using windows forms, and you know nothing of threading, you won't need to learn to use this.

I'm running out of ideas on what else to add though.

[Zeb Brown]

Sharose are you going to post this?

Or am i blind.

[ShaRose]

[QUOTE=Zeb Brown;23242664]Sharose are you going to post this?

Or am i blind.[/QUOTE]

I WILL, but I want to get everything ready first.

Threading was confusing as hell to me when I first started, and so I want to make it as insanely easy as possible.

[andersonmat]

I've created an even better settings file and I'm working on an interface that delivers more depth to it.

[Zeb Brown]

Hurry up please

[ShaRose]

[QUOTE=Zeb Brown;23251324]Hurry up please[/QUOTE]

Fine, fine. I'll release a beta.

I'm still going to comment everything though first.

[Zeb Brown]

PM it to me when your done.

[ShaRose]

Beta.

[url]http://filesmelt.com/dl/Facepunch_Ticker.zip[/url]

Known issues:

When stuff fades, sometimes it will flicker. I tried to fix it as much as I can, but it still does when fading. I'm sure there's an easy, non-hack non-workaround way to do what I want, but I can't find it.

The GUI sucks. I was never good at it. This is probably the closest you will get to my 'A-game'. That's why all the good stuff is in the dll.

Any issues, post them here and I'll check it / fix it / add it. Enjoy.

[itsDivine]

It keeps crashing in XP, won't let me login either.

[ShaRose]

[QUOTE=itsDivine;23264239]It keeps crashing in XP, won't let me login either.[/QUOTE]

Eh.

[editline]10:35PM[/editline]

When does it crash? For login failures, does it just say 'login failed'?

[itsDivine]

Hmmh, let me try again.

[editline]6:06 PM[/editline]

Yeah, it says 'Login Failed' and then proceeds to encounter a problem.

[ShaRose]

Oh, I built it as .net 4 for some reason. Duh. Second, rebuilding as 3.5.

[itsDivine]

Ok.

[ShaRose]

I remember why I was building it as .net 4 now. Fucking "ResGen.exe" exited with code -2147483645. Time to see if I can figure out what the hell is going on with that now.

[editline]10:54PM[/editline]

All right, I think I managed to get it to work. I'll test in an XP machine (without .net 4) first though, just to make sure.

[editline]10:57PM[/editline]

Seems to work fine.

[editline]10:58PM[/editline]

[url]http://filesmelt.com/dl/Facepunch_Ticker1.zip[/url]

There.

[itsDivine]

Thanks.

[editline]03:19AM[/editline]

Still doing the exact same thing.

[ShaRose]

[QUOTE=itsDivine;23266394]Thanks.

[editline]03:19AM[/editline]

Still doing the exact same thing.[/QUOTE]

Crashing, or failing to log in?

[itsDivine]

Failing and crashing.

[ShaRose]

[QUOTE=itsDivine;23266546]Failing and crashing.[/QUOTE]

Where does it crash? On startup? When you try to log in? If when you try to log in, when? When you click 'Try Login'? When you click 'Save Preferences'?

[itsDivine]

When I click try login, it says Login Failed. and crashes.

[ShaRose]

[QUOTE=itsDivine;23266664]When I click try login, it says Login Failed. and crashes.[/QUOTE]

When you used the updated version, did you copy and replace all three files?

[itsDivine]

Yes.

[ShaRose]

[QUOTE=itsDivine;23266685]Yes.[/QUOTE]

Let me try one thing. Second.

[editline]01:27AM[/editline]

Try this itsDivine.

[url]http://filesmelt.com/dl/Facepunch_Ticker2.zip[/url]

If it's an exception crashing it, this should catch it and output it to xml.

[itsDivine]

Crashed again.

Or it gave the same error.

Here:

Unhandled except has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Thread was being aborted.

Details:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Form.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmSysCommand(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FPTickerNotice
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/FPTickerNotice.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3614 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
FPTicker
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/FPTicker.DLL
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.1 built by: SP
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Rather long, I must say.

[editline]9:05 PM[/editline]

It gave me the message to give this to you:

<System.Threading.ThreadAbortException>
  <Message>Thread was being aborted.</Message>
  <StackTrace>
    <Frame>System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</Frame>
    <Frame>System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG&amp; msg)</Frame>
    <Frame>System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)</Frame>
    <Frame>System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)</Frame>
    <Frame>System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)</Frame>
    <Frame>System.Windows.Forms.Application.Run()</Frame>
    <Frame>FPTickerNotice.Program.Main()</Frame>
  </StackTrace>
</System.Threading.ThreadAbortException>

[editline]04:06AM[/editline]

And then finally, it crashed.

[ShaRose]

[QUOTE=itsDivine;23267129]Crashed again.

Or it gave the same error.

Here:

Unhandled except has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Thread was being aborted.

Details:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Form.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmSysCommand(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FPTickerNotice
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/FPTickerNotice.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3614 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
FPTicker
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/FPTicker.DLL
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.1 built by: SP
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Rather long, I must say.

[editline]9:05 PM[/editline]

It gave me the message to give this to you:

<System.Threading.ThreadAbortException>
  <Message>Thread was being aborted.</Message>
  <StackTrace>
    <Frame>System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</Frame>
    <Frame>System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG&amp; msg)</Frame>
    <Frame>System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)</Frame>
    <Frame>System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)</Frame>
    <Frame>System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)</Frame>
    <Frame>System.Windows.Forms.Application.Run()</Frame>
    <Frame>FPTickerNotice.Program.Main()</Frame>
  </StackTrace>
</System.Threading.ThreadAbortException>

[editline]04:06AM[/editline]

And then finally, it crashed.[/QUOTE]

Well, at least now I have somewhere to look. The ONLY place that uses Thread.Abort is in the login method, and it would make sense from that where it's happening. But on that note, it works perfectly. I'll look closer over it though.

[Zeb Brown]

I'm not crashing but my login's failing

And the font is a bit retarded.

[itsDivine]

I'm crashing because I got XP.

:D

[ShaRose]

[QUOTE=itsDivine;23267545]I'm crashing because I got XP.

:D[/QUOTE]

No it's not, I'm also testing it on an xp VM.

[editline]02:11AM[/editline]

How long is it roughly before it fails / crashes for you two?

[Jawalt]

Login fail and font is unreadable.

[editline]01:01AM[/editline]

When logging in the app freezes up for a moment. And then just says login failed.