Hi, 

Forgot to say: to minimise the problems you're having, you could use a userobject and put your web browser control on that object. When you paste that object on any window, at least you would avoid the problem every time you'd do a modification to the windows.

As for the problem of someone else having to get the object correctly:

- try to check it in using SVN itself, not powerbuilder.

- See if you can then import the file when downloaded with SVN, not powerbuilder

That way, you'd know if it has to do with powerbuilder's implementation of SVN or whether it's SVN itself.

.. or something similar, maybe even zipped to avoid SVN doing anything to the binary code? 

regards,

MiguelL

Hi Miguel,

Thank you for your answer.

I have the window since several years and some changes in this time and never problems. I also have another OLEControl with Web browser as an object in another library and no problem with it.

It's not only on other machines. Also if I force a GetLatestVersion on the good object on my machine it's going wrong.

I tried your suggestion. I compared the versions from CheckIn and Get outside Powerbuilder and there were no differences. So I think it's not a problem with SVN.

Then I compared the versions after GetLatestVersion and now there are differences in the binary part.

So it seems to be a problem with the SCC plugin (PushOk) or with the import into the library or with library management.

I also tried to remove object from source control and add it again. Does not work.

I have only changed a window function. Function code was 4385 byte before the change and is now 1988 byte. I tried to change the function and filled it with comments so the script size is still 4385 byte and it works!

I reduced the function length to 2087 bytes and it works. But with 2001 bytes it doesn't work anymore.

So I have a workaround: I insert some comments to the script.

Hi René,

We use TFS and seem to have no problems.

My guess is that SVN somehow screws with the binary part of the exported window / object.

When you "edit the source" of you window you won't see it, but when you "export" the window to a file, you will see something like this at the end:

Start of PowerBuilder Binary Data Section : Do NOT Edit
0Ewtest.bin
2600000a00e011cfd0e11ab1a1000000000000000000000000000000000003003e0009fffe000000060000000000000000000000010000000100000000000010000000000200000001fffffffe0000000000000000fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff........

......
1Ewtest.bin
End of PowerBuilder Binary Data Section : No Source Expected After This Point

Why don't you do the following test:

1) create a new simple control with the web browser object

2) export it to 1.srw 

3) add to source control

4) check out

5) do changes

6) check in

7) do getlatest on someone else's pc, export to 2.srw and compare the 2 files.

That way at least you will know if it has something to do with SVN.

Are the other users running the same windows version / updates? I'm thinking if there could be different versions of the control on different window versions/updates.

HTH