Page 1 of 1

message path outside the IDE

Posted: Fri Dec 11, 2009 12:20 am
by reelstuff
I was wondering if there were a practical method of discovering the message path outside the IDE.

I have a stack that functions perfectly while inside the IDE, :!:

However once you save it as a standalone application, the message path stops at some point exactly which line number I do not know.

Code: Select all

 load URL with message
Usually, if a stack runs in the IDE it will run outside it, but in this case something is just not working.

I am hoping to be able to figure out where the message path is stalling, because once compiled into a standalone, I get no error message, so somewhere,
the message path is not being passed,

any thoughts or suggestions,)

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 12:25 am
by sturgis
This sounds similar to another post. Do you have a preOpenStack handler? If so, can you comment it out and use an openStack handler instead and see if your issues go away?

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 12:36 am
by reelstuff
sturgis wrote:This sounds similar to another post. Do you have a preOpenStack handler? If so, can you comment it out and use an openStack handler instead and see if your issues go away?
Yes, I was using some preOpenCard handlers, have they been depreciated, ? if so that could explain some of the problems, thanks for posting.

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 12:51 am
by sturgis
Not sure if they've been deprecated but the theory is that they are firing before all libraries are loaded and thus causing problems. Not sure this is what is up with the problems you are having, but worth a check. If moving things out of preOpen solves it maybe a bug report is in order.
reelstuff wrote:
sturgis wrote:This sounds similar to another post. Do you have a preOpenStack handler? If so, can you comment it out and use an openStack handler instead and see if your issues go away?
Yes, I was using some preOpenCard handlers, have they been depreciated, ? if so that could explain some of the problems, thanks for posting.

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 12:57 am
by sturgis
http://forums.runrev.com/phpBB2/viewtop ... =12&t=4538 Here is the other thread that I consider similar. Also, when I was first trying things with rev I had problems making preOpen work correctly for a stack I was building and ended up scrapping my initial method to avoid using it.

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 1:04 am
by reelstuff
sturgis wrote:http://forums.runrev.com/phpBB2/viewtop ... =12&t=4538 Here is the other thread that I consider similar. Also, when I was first trying things with rev I had problems making preOpen work correctly for a stack I was building and ended up scrapping my initial method to avoid using it.
Yes, come to think of it, I have had some trouble using preOpenCard looks like I need to go over all my code to see if there is something else, I shifted to OpenCard
and it appears to work but still have a message problem in the standalone,

interesting, though, I have also noticed a message path issue when attempting to load the script editor.

I also put some simple answer "message1" ect, to see how far along the message path executes, and I found out where it stops, but not why it stops,

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 1:07 am
by sturgis
Just re-read, I was referring to preOpenStack but I'd guess there could be problems with preOpenCard also for the same reason. Hope you figure out whats up with the rest of everything, got me curious now!

Edit: In the other thread I linked malte says

Did you include the error dialog into your standalone? (Standalone application settings-> Bug reports)

If so, does it throw anything? If not, could you?

Cheers,

Malte
Might not hurt to try his suggestion.

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 1:30 am
by reelstuff
sturgis wrote:Just re-read, I was referring to preOpenStack but I'd guess there could be problems with preOpenCard also for the same reason. Hope you figure out whats up with the rest of everything, got me curious now!

Edit: In the other thread I linked malte says

Did you include the error dialog into your standalone? (Standalone application settings-> Bug reports)

If so, does it throw anything? If not, could you?

Cheers,

Malte
Might not hurt to try his suggestion.
Yes, thought of that as well, and so I did the bug report, but it does not throw an error at all, but I am looking at something now,
I think my problem my be somewhere in here,

Code: Select all

  put fld "fileType" into tFiletype
       set the itemDel to slash
       put fld "fileName" into tFilename
       put fld "folderLocation" into tFolder
       put tFolder and slash before tFilename
       put tFilename into fld testing
        set the filetype to tFiletype
        put URL pURL into URL ("binfile:" & tFileName)

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 1:48 am
by sturgis
Alas, I haven't worked with files much so won't be much help with this. The only suggestions I might have would be to throw up answer dialogs to make sure filetype and tFileName, tFileType and pUrl end up with the expected values. Doesn't seem like it should work in the IDE if this were the case, but since something apparently does end up different, doesn't hurt to validate.

Re: message path outside the IDE

Posted: Fri Dec 11, 2009 1:55 am
by reelstuff
sturgis wrote:Alas, I haven't worked with files much so won't be much help with this. The only suggestions I might have would be to throw up answer dialogs to make sure filetype and tFileName, tFileType and pUrl end up with the expected values. Doesn't seem like it should work in the IDE if this were the case, but since something apparently does end up different, doesn't hurt to validate.
Yes, thanks for replying, I think it is something I probably have done myself, at this point, because it now is broken in the IDE too, so it is definitely something in the callback message, This stuff is really fascinating, thanks again for taking time to post,