Cruisers Forum
 


Join CruisersForum Today

Reply
 
Thread Tools Rate Thread Display Modes
Old 28-05-2015, 14:16   #1
Registered User

Join Date: Dec 2013
Location: Rogoznica, Croatia
Boat: Bavaria Cruiser 40
Posts: 619
Images: 16
Bug in waymark/properties/description text entry

I'm running OpenCPN version 4.0.0 on a MacBook Pro with OSX10.10.3 and have found a glitch.

When you drop a mark then go to edit the properties and try to enter any text into the descriptions box you find that if you need to enter any of the letters used for the control menu items (such as T,L,S & A which are in the View menu) the character does not enter into the text box but activates the menu option. In the above examples this switches the ENC Text, Lights, Soundings or Lights.

The only method to enter descriptions I have been able to use is copy and paste from Open Office.

Cheers

Keiron
__________________

__________________
kas_1611 is offline   Reply With Quote
Old 28-05-2015, 14:33   #2
Registered User

Join Date: Jul 2010
Location: Monastir, Tunisia
Boat: Amel Sharki
Posts: 1,777
Re: Bug in waymark/properties/description text entry

That is a known bug of OpenCPN for Mac OS X but there is still no fixed version released.

Gerhard
__________________

__________________
CarCode is offline   Reply With Quote
Old 28-05-2015, 18:30   #3
Marine Service Provider
 
bdbcat's Avatar

Join Date: Mar 2008
Posts: 4,884
Re: Bug in waymark/properties/description text entry

Keiron/ Gerhard...

First I have heard of it. Maybe a Flyspray bug report would elevate the priority.

Thanks
Dave
__________________
bdbcat is offline   Reply With Quote
Old 28-05-2015, 23:08   #4
Registered User

Join Date: Dec 2013
Location: Rogoznica, Croatia
Boat: Bavaria Cruiser 40
Posts: 619
Images: 16
Re: Bug in waymark/properties/description text entry

Perhaps instead of using plain letters for keyboard shortcuts of menu items all that needs to happen is to use cmd+letter or CTRL+letter to distinguish between plain text entry and actual command entries.

Glad to know it is known about and not just me
__________________
kas_1611 is offline   Reply With Quote
Old 29-05-2015, 02:23   #5
Registered User

Join Date: Nov 2014
Location: Netherlands
Posts: 179
Re: Bug in waymark/properties/description text entry

Quote:
Originally Posted by bdbcat View Post
Keiron/ Gerhard...

First I have heard of it. Maybe a Flyspray bug report would elevate the priority.

Thanks
Dave
FS#1655 is opened for this.
It says Solution Pending
The fix is committed on 13 March
Correct keyboard accelerator logic for WXOSX (FS#1698/1655)
__________________
ptulp is offline   Reply With Quote
Old 29-05-2015, 02:35   #6
Registered User

Join Date: Jul 2010
Location: Monastir, Tunisia
Boat: Amel Sharki
Posts: 1,777
Re: Bug in waymark/properties/description text entry

Quote:
Originally Posted by bdbcat View Post
Keiron/ Gerhard...

First I have heard of it. Maybe a Flyspray bug report would elevate the priority.

Thanks
Dave
Yes, I know, the port for Mac OS X is not cared about too much.

Gerhard
__________________
CarCode is offline   Reply With Quote
Old 29-05-2015, 04:16   #7
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 9,398
Re: Bug in waymark/properties/description text entry

Didn't Caesar Schinad have some fixes for this?

Sent from my SCH-I545 using Cruisers Sailing Forum mobile app
__________________
rgleason is online now   Reply With Quote
Old 29-05-2015, 04:51   #8
Registered User

Join Date: Jul 2010
Location: Monastir, Tunisia
Boat: Amel Sharki
Posts: 1,777
Re: Bug in waymark/properties/description text entry

Quote:
Originally Posted by rgleason View Post
Didn't Caesar Schinad have some fixes for this?

Sent from my SCH-I545 using Cruisers Sailing Forum mobile app
It was fixed long time ago in github but never a fixed compiled version was released.

Gerhard
__________________
CarCode is offline   Reply With Quote
Old 29-05-2015, 19:09   #9
Marine Service Provider
 
bdbcat's Avatar

Join Date: Mar 2008
Posts: 4,884
Re: Bug in waymark/properties/description text entry

Mac Users...

Sorry, my bad memory. This bug is well known, and the fix is in process.

School time...Listen up, please:

1 "Solution Pending" means (and has always meant) that the fix is in github master branch, has been functionally verified, and will be in place for all systems in the next Beta release.

2. There has been no Beta for any systems since O4.0.0 was released.

3. Ergo, no one not building from github master source will have seen this fix yet.

4. You may expect to see this fix in place when the Beta 4.1 series starts, and so it will propagate into the OCPN 4.2.0 Release.

5. This is the way we manage controlled Releases over (now) 5 platforms. There may be other ways, but this is ours.

Just so you will know, we tend to prioritize our cross-platform development efforts on overall PC market share. If you think OCPN development for the OS X platform is de-focused, you may wish to study those numbers...

Thanks
Dave
__________________
bdbcat is offline   Reply With Quote
Old 30-05-2015, 01:55   #10
Registered User

Join Date: Jul 2010
Location: Monastir, Tunisia
Boat: Amel Sharki
Posts: 1,777
Re: Bug in waymark/properties/description text entry

There is one point missing however:
What happens when a released version is unusable for a platform?

Gerhard
__________________
CarCode is offline   Reply With Quote
Old 30-05-2015, 03:16   #11
Registered User

Join Date: Dec 2013
Location: Rogoznica, Croatia
Boat: Bavaria Cruiser 40
Posts: 619
Images: 16
Re: Bug in waymark/properties/description text entry

Knowing a fix is "in progress" is good with me

It is not like this is a critical bug that prevents the system working, rather a minor niggle that has a work around through "copy/paste" from a text file. Doesn't spoil the experience in any way once you know that.

Keiron
__________________
kas_1611 is offline   Reply With Quote
Old 30-05-2015, 06:52   #12
Marine Service Provider
 
bdbcat's Avatar

Join Date: Mar 2008
Posts: 4,884
Re: Bug in waymark/properties/description text entry

Gerhard...

re:
Code:
What happens when a released version is unusable for a platform?
That is a simple indication that there has not been enough testing and Flyspray feedback for that platform. We make every effort not to release when there is an outstanding critical usability bug still open in Flyspray.

It is simply not practical for the developers to test every corner case feature on every platform at every Beta. Too many dimensions. That is why we do broad-spectrum Beta testing.

Thanks
Dave
__________________

__________________
bdbcat is offline   Reply With Quote
Reply

Tags
rope

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Scuba Dive Sites with GPS / Description - Tonga, Fiji, Vanuatu, New Caledonia knoebi Pacific & South China Sea 11 31-07-2010 23:11
Ken Barnes' Description of Situation Trim50 General Sailing Forum 205 10-11-2009 10:11



Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -7. The time now is 06:23.


Google+
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Social Knowledge Networks
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.

ShowCase vBulletin Plugins by Drive Thru Online, Inc.