Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Skippy on December 30, 2009, 05:55:31 PM

Title: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: Skippy on December 30, 2009, 05:55:31 PM

I can't seem to load this application, the console window reports:

"cannot create application". I'm assuming it can't setup the GUI environment?

I've ensured all the relevant requirements, latest MUI/.mcc's, LIBs are installed as stated in the read-me-first.docs.

I'm testing the Amiga OS 3.x 68k version using:

a1200 68030@50 w/ 32MB fast, OS3.1, only difference is I'm using MUI3.8 as opposed to MUI 3.9 it mentions, perhaps this is my problem?



I've tried increasing the stack but this makes no difference.

What would be the key factors not permitting it from loading that I can check against.


Skipos la bathos.

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: ikepgh on December 30, 2009, 07:23:47 PM

Sounds like an MUI issue to me, since that error is part of the app initialization code.  

My mistake on the readme, that should have stated 3.8 for MUI, thanks, I'll fix that.  Have you run SnoopDos?

IKE

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: Skippy on December 30, 2009, 07:53:54 PM

Quote from: ikepgh;535473

Sounds like an MUI issue to me, since that error is part of the app initialization code.  
IKE

Yes! What an awesome day this is, now I'm using AmiTwitter and SimpleMail.

Absolutely, SnoopDOS diagnosed "MCC_Urltext", many thanks for the quick response and sharing your valued development of this production.

Now my Amiga can tweet!

Best regards.

Paul.

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: Skippy on December 30, 2009, 09:00:05 PM

AmiTwitter - Classic Amiga a1200

http://www.flickr.com/photos/skippyxp/4229378594/

Works great!

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: Skippy on December 31, 2009, 12:03:09 AM

1: Indirect AmiTwitter related question: With OpenURL my default Browser is configured as IBrowse %f (Also tried with quotations "%f")

IBrowse seems to take the %f string and literally points the Browser to http://%f/

How can I rectify this so that it carries the url address in the string over to the Browser.

- The alternate is to use the clipboard copy/paste otherwise.

2: Can the timeline/tweets ascending/descending order be changed to have the most recent tweets first? Can't see anything detailing in the literature. Otherwise with exhaustive listings they require scrolling down to the bottom and reading upwards.

Cheers.

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: x303 on December 31, 2009, 12:29:33 AM

Quote from: Skippy;535496

1: Indirect AmiTwitter related question: With OpenURL my default Browser is configured as IBrowse %f (Also tried with quotations "%f")

If i'm correct it should be set as "%u" instead of "%f".

x303 :D :D :D

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: Skippy on December 31, 2009, 01:05:42 AM

Quote from: x303;535497

If i'm correct it should be set as "%u" instead of "%f".

x303 :D :D :D

Thank you good Sir, works a treat!!

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: Drummerboy on December 31, 2009, 01:08:29 AM

Quote from: Skippy;535475

Yes! What an awesome day this is, now I'm using AmiTwitter and SimpleMail.

Absolutely, SnoopDOS diagnosed "MCC_Urltext", many thanks for the quick response and sharing your valued development of this production.

Now my Amiga can tweet!

Best regards.



Paul.

You know, you can Twitt with Ibrowse, Direct from Twitter Site.. just check @drummerboycr

But i test Amitwitter and Work fine.. just i fill, eat some of RAM..


Regards

Title: Re: AmiTwitter Ver. 0.23 Public Beta Release 1
Post by: Skippy on December 31, 2009, 02:45:11 AM

Quote from: Skippy;535500

Thank you good Sir, works a treat!!

Can you enlightenment me to a definitive listing of the string variables for future reference instead of a "quick fix" solution without clarity of definition.

Many thanks,

Skipster.