Certain links do not open from within iSilo anymore (iSilo for Palm OS)

[Pride Of Lions]

I'm noticing that certain links do not open from within iSilo like they usedto. I usually just select them from the Document List wen I want the open, but now iSilo is ignoring me.

I have ZLauncher and one of my tabs is a list of the iSilo documents on my handheld's RAM, and I can select them from the ZL tab and they will open, but trying to open them in iSilo will not work.

I had this behavior in a few documents and I assumed that it was because I'd upgraded to the latest beta (from 4.25 to 4.26b1) on the PDA but not on iSiloX and the incompatibility existed because the doc's were trying to open in 4.26b1, but were being converted in iSiloX 4.25. I've since upgraded to iSiloX 4.26b1 and the particular doc's began to open from within iSilo.

Now I'm noticing that other documents that are being converted in iSiloX 4.26b1 and are trying to be accessed from iSilo 4.26b1 are ignoring my selectings.

Examples of such behavior include:

http://www.stonepages.com/news/index.rdf
http://www.complete-review.com/saloon/rss.xml

Hopefully this information helps to make iSilo and iSiloX better than ever.
POL9A

[iSilo]

The version of iSiloX you used to convert the documents should have no bearing on whether iSilo responds. It should always respond in some way when you tap the name of a document in the document list.

It sounds like you are saying that when you tap the names of the documents in the document list that iSilo does not respond at all. Does the name highlight? Does tapping the icon to the left of the name do anything? Could it possibly be a digitizer alignment issue?

[Pride Of Lions]

I know it's not a digitizer issue on my Zodiac2. (The digitizer is perfect, I know digitizer issues because my old T|3 had a terrible digitizer.) Also, it will not open the article if I select the article with the hardware buttons (the analog joystick on the left side, as you know, will scroll the articles one-by-one in the Document List while the blue and green buttons on the right will scroll up and down in the Document List a page at a time.) Then when I get to the article, I just press in on the joystick and traditionally the article will open.

I've just noticed this behavior recently. I suppose it has something to do with the recent beta. My documents haven't changed in a while (settings-wise) so it couldn't be some new setting that's affecting the opening of them in iSilo.

Hopefully the fix is easy. For me, I can workaround it by opening the document in ZLauncher, but if I'm already in iSilo that means that I have to exit iSilo and re-enter it via the article in question.

As additional information, I do tend to install beta software and sometimes alpha software, so maybe one of these is causing an incompatibility, but then why (assuming it does) then affect only a few documents and not the rest?
POL9A

[Pride Of Lions]

I thought the latest beta would fix this problem behavior, but the weirdness still exists.

It's as though iSilo won't take that last step to open the document. It selects normally, either by tapping on the document in the Document List or by scrolling to it with the Zodiac2 buttons, but tapping on it or clicking into the analog joystick (pressing into it) wil not open the certain documents like they used to.

Do you think it may be a software incompatibility with some other stuff on my Zodiac2? Should I send you the document as a test?
POL9A

[iSilo]

If you use the stylus to tap the names of the documents in question, does iSilo highlight the name? Does tapping the icon to the left of the name do anything?

[Pride Of Lions]

The document is highlighted in iSilo, but still doesn't respond to other stimuli (doesn't open.) Tapping the icon to the left brings up the drop-down menu with "Open, Catagories,..." and selecting "Open" still doesn't open the document. The other options in the drop-down menu still function as normally as possible.

I'm wondering why this behavior is only exhibited in a few documents, and not in all of them. Could it be how iSiloX treats these certain documents? Or how the feeds are given to iSiloX? Or something?
POL9A

[iSilo]

You said that the documents that do not open are all located internally and not on a memory card. Is that correct? Or is it a mix of internal and external documents?

In the context menu that you get when you tap the icon for the files at issue, if you tap Information, does it give the correct information in the Document Information form that appears?

[Pride Of Lions]

The "Information" option of the pull-down menu works fine and gives me (I assume) all the information I'd want to know about the document. However, the "Open" button there doesn't work either.

Open to more suggestions.
POL9A

[iSilo]

You said that the documents that do not open are all located internally and not on a memory card. Is that correct? Or is it a mix of internal and external documents?

[Pride Of Lions]

It was answered in the subject line. Yes, the documents are in "Internal" memory.
POL9A

[iSilo]

Sorry about that. I overlooked the title.

Okay, we're going to need to probably go through several iterations to determine where the problem is. First, let's have you download and install a special version of iSilo from here (http://www.iSilo.com/info/beta/dl/iSilob2a.zip). After downloading it, unzip it, and install it to your device. Then start iSilo and go to the About form and verify that the version says 4.26b2a. Next go back to the document list view and tap on one of the files that does not open. It should present a Message form with two characters in brackets. What are the two characters that the Message form shows?

[Pride Of Lions]

Having confirmed that the special iSilo version is indeed 4.26b2a, tapping on an un-openable document gives the following message:

[ae][][]

In fact, all of the un-openable documents list the same message when tapping on them in this newer iSilo version.

I hope this is helpful. I'm still wondering why ZLauncher will open the documents and iSilo won't. Maybe my version of ZL is to blame?
POL9A

[iSilo]

Which version of ZLauncher are you using?

Also, with the special version of iSilo, what letters does it give when you try to open a document that does normally open (e.g., does not have the problem), and does it open successfully with this special version?

[Pride Of Lions]

I'm using ZLauncher v.5.20. It's the latest as far as I know.

When opening a "normal" document using this special version of iSilo, I still get the "[ae][][]" message, but this time after I click the "OK" button it opens up the document.

I was kinda hoping that I'd get a different error message so that we could further determine the answer to the problem, but alas. It's frustrating, I know, because it just happened one day for no reason (that I can discern.) It must be frustrating for you as the developer because apparently no one else has come across this particular medley of softwares and hardware that it can be re-created somehow.

Open to suggestions.
POL9A

[iSilo]

To help eliminate ZLauncher as a factor in the problem, can you try exiting out of ZLauncher. You should be able to do this by going to the App menu in ZLauncher and tapping Exit. After exiting out of ZLauncher, start iSilo and see if the problem still occurs.

[Pride Of Lions]

It seems so simple, but I've been so in love with ZL that I forgot I had the default Zodiac launcher.

Still, no dice. The ungainly behavior continues even in the default launcher. It was a great idea, though. Fortunately, in ZL I can still open the unhappy documents from within the launcher. If I were to stay with the default launcher, I wouldn't be able to open the documents at all.

So far, it appears that only 2 documents are affected, but at first it was just one with the second one acting up a few days later. Hopefully more don't become afflicted, but precedent has been set.

Crossing fingers.
POL9A

[iSilo]

No really new ideas on what the problem could be.

Are you running any hacks or system utilities other than ZLauncher that stay active in the background or otherwise?

[Pride Of Lions]

I have Fonts4OS5, but I've had that for a while with no problems, so I don't suspect it. ZLauncher, but we've ruled that out. More recently (within the last few weeks) I've added SkinTW (http://www.zlthemes.com/ProductDetailListing.php?PID=96) to change my DIA from the staid Tapwave version to a "Silver Windows XP" version. Do you think this could be it? If so, why does it only affect a small percentage of the iSilo docs?

I wonder if it's the culprit.
POL9A

[Pride Of Lions]

I went to bed last night and was reading myself to sleep with my favorite iSilo docs, when all of a sudden the weird behavior had stopped. I could click on whatever document from within iSilo and it would open. I have no idea what has happened between before and now, I just know that I tried it (again!) and it finally worked.

I haven't deleted any hacks or anything. Still using SkinTW for the DIA replacement, ZLauncher as my launcher, Fonts4OS5 and it mysteriously decided to work last night. I can't even give the latest beta (4.26b4) any credit because I'd downloaded it when it first came out and my weird behavior still continued until last night. Hopefully it'll stay away, but I'll be on the look-out for it's return.

Hopefully, it hasn't decided to move onto different documents.
POL9A

[Pride Of Lions]

So, last night as I was reading for bed, the behavior returned. But, not on each of the previous documents, just (so far) one I really like. I'm beginning to think that the settings on other documents are affecting the other documents, meaning that when other documents have certain settings the behavior is gone, and when those settings are changed, the behavior re-appears.

It sounds crazy, but... I had a certain document to exclude certain links, and the behavior to not open other documents on my Zodiac2 disappeared. When I deleted two of the exclusions in that certain document, the behavior re-appeared in the affected documents.

I such a thing possible? Or am I reaching?
POL9A

[iSilo]

No, it does not sound likely that would be a cause.

On another thought, the Zodiac2 has two SD card slots. Do you have both slots filled with a card or just one?

[Pride Of Lions]

I have both SD card slots filled with SD cards. The iSilo documents that I sync daily are on the Zodiac2's internal RAM (not the internal virtual card) (the documents that act funny are in this group), and the e-books in iSilo format are on the SD card (just one, not some on both.)

I think that maybe some orphaned files on my Z2 are causing havok with the iSilo docs in question, or some settings in certain iSilo docs are affecting iSilo in negative ways towards other iSilo docs.

If that makes sense.
POL9A

[Pride Of Lions]

I set iSiloX to convert my channels from 12:00am-6:30am so that they're ready for a morning HotSync before I'm out the door. Once, with iPodderX running in the background and slowing iSiloX's access to data, the conversion went into 8:00am-ish and I saw the "Conversion created some messages" error message, but I didn't understand it.

This morning it happened again and I was able to "Save" it (usually it goes away after a time if you aren't there to see it, is it possible to make it where we can access the "Conversion Log" even after it automatically goes away for times like this?) and I thought it might shed some light on our situation.

Hope it helps.
POL9A

[iSilo]

Those messages that are generated during conversion would not have anything to do with not being able to open the document. If you want the messages automatically saved to a file, then go to Tools/Options/Logging/Conversion, enable the option to Save conversion messages to a file, and specify a filename.

[Pride Of Lions]

Now, the previous documents appear to open fine from within iSilo, but other documents are afflicted by the "no open when tapped" plague.

I have no idea why this happens. When it hits a document, it seems to stay afflicting that document for a while until it decides to stop. And when it decides to stop, it appears to transfer it's headache-inducing quirks to another random document.
POL9A