Beta Test / Technical

[transmitterdan]

Robert,

You can compress the log file into zip format then rename it opencpn.zip.doc. Then it should be small enough to upload with a message.

I don't think the Windows 7 is the problem either but the way to find the problem may be different for different operating systems (Mac, Linux, etc).

[bdbcat]

tdan, et al...

If the the Settings icon is inaccessible, it means that an invalid PlugIn is trying to load. Delete the Plugins, except the 4 standard PlugiIns as provided by the installer, and O42 should start up ok. This is a known bug in 4.2. Logfile will so indicate PlugIn difficulty. Sounds like the BSB4 PlugIn is not really the latest.

Dave

[betelnuss]

Hi everybody.....hope this is the right place to ask


i have a raspberry pi 2 with ubuntu arm mate 15.10.1 installed. I compiled open cpn 4.2, it runs fine. Then i started to compile the plugins, starting with radar_pi. Compiling also no problem but how do i get opencpn to see the plugin now.

Hope this is not a redundant question....i can't get them from the repository i think. Maybe someone can point me to the right thread?

Thanx a lot Georg

[nohal]

Georg...
The beta PPA at https://launchpad.net/~nohal/+archiv...ncpn/+packages has all the plugin packages available for ARM as well.
If you compile locally, a

make install

should install the plugins to the right place, just make sure the installation prefix is the same as you used for the core program.

Pavel

[betelnuss]

...thanx al lot Pavel

[rgleason]

Windows rtlsdr_pi v4.2.0 Plugins Download page
both the Link and Plugin are not working. Suggested to Pavel "Not Available" and test it with some users by upload to File Thingie.

Changed the url and downloaded plugin. Installed on Win10 Surface with Ov4.2. O loads. Click Settings and it hangs. Remove rtlsdr_pi and it runs fine. For me on Win10 machines, building from Sean's and Pavel's fork, I get the same problem. Also confirms what bdbcat said below about Settings.

Of course Norton calls navnux.org unsafe and I have to override Norton's removal of the plugin when downloaded. Have finally joined Norton Safeweb and filed a good website rating, but it still shows as malicious. Perhaps with others adding a rating and over time it will stop picking on OpenCPN.

[rgleason]

I have been having difficulty with the formatting of menus in plugins in Windows10. A fair number of menus are formatted acceptably, but many are not. I have tried using wxFormBuilder to fix this, but sometimes the menu structure is so encapsulated I don't know what to do to get the Values to force the format larger. Also I think something has change about this since the change to wxWidgets 3.0.2 so that old plugins which are not following the new stricter rules are suffering, but this is just a suspicion. A few hints about how to use wxFormbuilder to fix these problems would be appreciated, as many of Sean's plugins suffer and he is not around and there are others, including some of Mike Rasbats. This involves released plugins and beta. Some users are noticing and complaining a little too.

I have considered that the problem might also be with my particular setup. Last year my Surfacepro3 had Win8 and was configured with a screen resolution somewhat less than the 2160-x1440 recommended, thinking it would save memory and make it faster and give me larger text too. At that time I had my text size set at 125%, now after upgrade to Win10 it is set at the recommended 2160x1440 and "text size, apps and other items" at 200%.

In OpenCPN Options > Display > Advanced Physical Screen Width is set to "Auto"
for v4.0 , v4.2 and v4.2.1

Should this be ok insofar as the use of Plugin Menus, such that formatting is not affected adversely?

[nohal]

Rick...
Your problem is obvious - the 200% buttons and other widgets take too much space, please create tickets in the respective bugtrackers, if possible with the screenshots of the "broken" dialog attached to each of them so that the devs see what should be changed to make the layout work better in such a situation.

Thanks

Pavel

[rgleason]

Thanks Pavel. Will do that.

[rgleason]

There will be more iterarions. -and work for you.

[Hakan]

New Git update issue:
Win10, VS2013
Commit fb600f68c4d77...."Cause immediate jump to last known position on autofollow enable."
Causes "Auto follow" mode and "Look Ahead" mode to not work.

If I comment the line: "JumpToPosition(gLat, gLon, cc1->GetVPScale());" out both are working again.

Håkan

[rgleason]

Has anyone heard from Sean? Where his is? etc?

[CarCode]

Originally Posted by Hakan

New Git update issue:
Win10, VS2013
Commit fb600f68c4d77...."Cause immediate jump to last known position on autofollow enable."
Causes "Auto follow" mode and "Look Ahead" mode to not work.

If I comment the line: "JumpToPosition(gLat, gLon, cc1->GetVPScale());" out both are working again.

Håkan

Another one is the commit "Correct potential fault in bitmap depth conversion algorithm" which is a memory leak now.

Gerhard

[bdbcat]

@CarCode...

re:
Another one is the commit "Correct potential fault in bitmap depth conversion algorithm" which is a memory leak now.

Good catch. Fixed in github master now.

Thanks
Dave

[CarCode]

Originally Posted by bdbcat

@CarCode...

re:
Another one is the commit "Correct potential fault in bitmap depth conversion algorithm" which is a memory leak now.

Good catch. Fixed in github master now.

Thanks
Dave

Your fix:

     wxImage im_front = front.ConvertToImage();
-
+    unsigned char *pfront = im_front.GetData();
+    if(!pfront)
+        return wxNullBitmap;
+    
     unsigned char *presult = (unsigned char *)malloc(front.GetWidth() * front.GetHeight() * 3);
+    if(!presult)
+        return wxNullBitmap;
+    
     unsigned char *po_result = presult;
-    unsigned char *pfront = im_front.GetData();
 
-    if(!presult || !pfront)
-        return wxNullBitmap;
     
     unsigned char *afront = NULL;
     if( im_front.HasAlpha() )

My fix:

    unsigned char *pfront = im_front.GetData();

    if(!presult || !pfront){
+        free( po_result );
        return wxNullBitmap;
    }
    unsigned char *afront = NULL;

Why you don't like to free allocated memory once it is not used anymore?
Your code style is always a little bit strange to me.

Gerhard