XYplorer Beta Club

Since a few versions the nethood is empty. The single resources are still shown, but they can't be opened. They are all empty.

I'm sorry that I didn't report this earlier. I didn't found the time...

And I know that this was reported in the wishes forum, but I think this is the better place for it...

Ok Peter, thanks for opening this topic here -- it's for sure a bug we are talking about.

Shit. It would have been so nice to have more speed without having more problems. It's tough for me to handle because my local network works just like before (only a bit faster). To help me finding my way in the dark, can you describe as exactly as possible what happens if you try to select/open a network resource.
- What are you doing: clicking or expanding a tree node?
- What should happen but doesn't?
- Are we talking about "computer resources" (with "computer icon")?
- Do all resources fail to open or just some?
- Any error messages?
- Does the app take time (is it trying to do something and failing)?
- Any other hint?

Thanks for any contribution!

- What are you doing: clicking or expanding a tree node?
Sometimes so, sometimes so. It's all the same.

- What should happen but doesn't?
The content should be displayed, but it looks like empty folders. Even my own shared folders aren't displayed.

- Are we talking about "computer resources" (with "computer icon")?
Yes.

- Do all resources fail to open or just some?
First the content of the server was diplayed. But now after a restart all resources are empty.

- Any error messages?
No.

- Does the app take time (is it trying to do something and failing)?
Yes, the app freezes for a short time when I click on a resource (1-2 sec.).

- Any other hint?
Yes. Some time ago I've had problems with our server (connected network drive). When deleting a file it still was displayed. Do you remember? That's gone.

Thanks.

If you enter an existing UNC path in to the Goto box (Ctrl+G), e.g.:
\\myCompi\SharedDocs\

If do a file search over an existing UNC location, e.g.:
\\myCompi\SharedDocs\

What happens?

admin wrote:If you enter an existing UNC path in to the Goto box (Ctrl+G), e.g.:
\\myCompi\SharedDocs\

Doesn't work. The app jumps to the right resource, but not to the subfolder. The files view remains empty.

admin wrote:If do a file search over an existing UNC location, e.g.:
\\myCompi\SharedDocs\

If I go to a resource and search something I get an error:

Run-time error '9':
Subscript out of range

peterbonge wrote:

admin wrote:If you do a file search over an existing UNC location, e.g.:
\\myCompi\SharedDocs\

If I go to a resource and search something I get an error:

Run-time error '9':
Subscript out of range

And if you don't "go there" but just paste an existing resource path into the search location field and run a search?

I tried something completely different in the latest BETA. I'm curious if you note any changes if not improvements!

Now it works perfect and also very fast! Thanx!

peterbonge wrote:Now it works perfect and also very fast! Thanx!

Man, that's great!!!
What about Ralph?

Apparently we got some movement here...

peterbonge wrote: Now it works perfect and also very fast! Thanx!

I agree, lightning fast and (almost) everything in place.

admin wrote: What about Ralph?

Congratulation, great improvement on the network neighbourhood (NNH) issue.

Don't worry no additional wishes, just some comments:

• 1.) A couple of structure elements of the NNH aren't displayed as in Windows Explorer. (WinE)
  If you compare the jpeg's again, which I've sent you yesterday, the nodes "Gesamtes Netzwerk", "Microsoft Windows-Netzwerk" and "Domhsr" (domain name) are not displayed in TV3, but for me that's fine.
  
  2.) Published shared folders in the NNH are displayed in WinE directly as substructures of NNH, in TV3 you need to select the resource first, to see them, but no problem for me either.

Hope this helps.

Thanks

RalphM wrote:

• 1.) A couple of structure elements of the NNH aren't displayed as in Windows Explorer. (WinE)
  If you compare the jpeg's again, which I've sent you yesterday, the nodes "Gesamtes Netzwerk", "Microsoft Windows-Netzwerk" and "Domhsr" (domain name) are not displayed in TV3, but for me that's fine.

That's on purpose, because displaying those nodes is just useless (in my experience at least).

RalphM wrote:2.) Published shared folders in the NNH are displayed in WinE directly as substructures of NNH, in TV3 you need to select the resource first, to see them, but no problem for me either.[/list]

Neither for me.

Well well. I'm really satisfied with this development. You can imagine that programming kind of blind-folded (because I have no network at home) is not a comfortable situation.
Big thanks for your feedback, folks!

admin wrote:That's on purpose, because displaying those nodes is just useless (in my experience at least).

Might be interesting for people with different networks though.
But we might let people with such environments talk for themselves.

admin wrote: Neither for me.

We missed one thing about the published shared folders:

1) These are listed in the users profile under "...Documents and Settings\User_xxx\Network Neighbourhood\..." as well

2) If you try to open one of them, TV3 crashes with the following message:
"Run-time error '-2147024829 (80070043)':
Automation error
OK"

RalphM wrote:1) These are listed in the users profile under "...Documents and Settings\User_xxx\Network Neighbourhood\..." as well

2) If you try to open one of them, TV3 crashes with the following message:
"Run-time error '-2147024829 (80070043)':
Automation error
OK"

Arrgh. Again, lacking a network I cannot reproduce this. And, frankly, I'm right now too busy with implementing Tabbed Browsing to care. Please, remind me later...