Re: [Rosegarden-user] File Locking

2016-04-12 Thread Al Thompson
On 04/12/2016 10:52 AM, D. Michael McIntyre wrote:
> Why not a button to clear the lock ?
> I thought about that, but it seems too tempting to invite users to just 
> click away a problem instead of taking the time to investigate and deal 
> with it.  Couldn't you have a .rg file on a shared volume that was being 
> edited by instances of Rosegarden on two entirely separate computers? 

How about if the lockfile contained the username, machine name, and
time/date the file was opened.  Then the dialog box could display that
information, with a button to delete the lockfile.



--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-12 Thread D. Michael McIntyre
On 04/12/2016 10:17 AM, Yves Guillemot wrote:

>> contents of some pixels on the screen in a dialog is obnoxious when you
>> have to clear a lock file after a crash.
>>
> Why not a button to clear the lock ?

I thought about that, but it seems too tempting to invite users to just 
click away a problem instead of taking the time to investigate and deal 
with it.  Couldn't you have a .rg file on a shared volume that was being 
edited by instances of Rosegarden on two entirely separate computers? 
In that case, a scan of the local machine for active Rosegarden 
processes would turn out negative, but the danger of losing work would 
be real enough.

I also thought about a use at own risk command line option.
   --force-unlock or something like that.

Whatever the solution, an improvement seems like a good plan.

-- 
D. Michael McIntyre

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-12 Thread Yves Guillemot
Le mardi 12 avril 2016, 08:57:35 D. Michael McIntyre a écrit :
> I finally figured out what this is missing.  The file location text
> needs to be in some kind of selectable area, so you can grab the text
> straight out of the dialog.  Navigating to the file based on the
> contents of some pixels on the screen in a dialog is obnoxious when you
> have to clear a lock file after a crash.
> 

Why not a button to clear the lock ?

Yves


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-06 Thread Yves Guillemot
Le mardi 5 avril 2016, 21:56:48 Ted Felix a écrit : 
>This should be fixed as of [r14586].

Works fine here.
 
Yves


--
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-06 Thread Yves Guillemot
Le mercredi 6 avril 2016, 06:02:18 D. Michael McIntyre a écrit :
> On 04/05/2016 10:54 PM, Ted Felix wrote:
> > I'm testing with diacritics in Ubuntu with no trouble.  The lock file
> > 
> > name in the message box matches the lock filename exactly.  No UTF-8
> > garbage.  Is this a distro-related problem?  Or am I testing with the
> > 
> > wrong diacritics?  My test file is named:
> > test-dīácrítícs.rg
> 
> Same result here.  I tried a bunch of random weird stuff.  I can prevent
> Rosegarden from being able to load a file by changing its encoding to
> something awful, but everything else I tried just works.
> 
> Could be locale- and/or filesystem-related.

It is locale related.

My distro (Mageia 5) offered two options for locales:
   - The default mode where filenames are encoded with UTF8 
   - The "Compatibility with old encoding" mode where filenames are encoded 
with ASCII or ISO-something.

In the first mode, my locale is LANG=fr_FR.UTF-8.
In the second mode it is LANG=fr_FR.

Filenames may contain diacritics in the two modes, but utf8 garbages are only 
found with the first one.

The problem should be fixed in rev. 14587.

Yves



--
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-06 Thread D. Michael McIntyre
On 04/05/2016 10:54 PM, Ted Felix wrote:

> I'm testing with diacritics in Ubuntu with no trouble.  The lock file
> name in the message box matches the lock filename exactly.  No UTF-8
> garbage.  Is this a distro-related problem?  Or am I testing with the
> wrong diacritics?  My test file is named:
>
> test-dīácrítícs.rg

Same result here.  I tried a bunch of random weird stuff.  I can prevent 
Rosegarden from being able to load a file by changing its encoding to 
something awful, but everything else I tried just works.

Could be locale- and/or filesystem-related.  I don't have any weird 
filesystems to test, like an old partition that was created before utf-8 
became the norm.  I used to have one of those, and that's what I'm 
betting might cause breakage.  Haven't had that for a long time.

-- 
D. Michael McIntyre

--
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-05 Thread Ted Felix
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> There is a small issue (repeatedly occurring with RG) about UTF8 garbage in
> the displayed lock file name when the .rg file uses non ASCII characters (I 
> did
> the first test with a file name containing a diacritic).

   I'm testing with diacritics in Ubuntu with no trouble.  The lock file 
name in the message box matches the lock filename exactly.  No UTF-8 
garbage.  Is this a distro-related problem?  Or am I testing with the 
wrong diacritics?  My test file is named:

   test-dīácrítícs.rg

Ted.

--
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-05 Thread Ted Felix
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> Then I tried a less obvious case:
>
>   - Create a new composition in RG and save it in a file. Keep RG open.
>   - Create again a new composition in another RG instance
>   - Try to save the last composition in the same file as fhe first one.
>   => Can't save the file, the popup is displayed.
>
>   - Try again the same save operation
>   => no more popup.
>
> There is now two RG instances able to write alternatively in the same file.

   This should be fixed as of [r14586].

Ted.

--
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-01 Thread D. Michael McIntyre
On 03/31/2016 08:08 PM, Ted Felix wrote:

> I'll leave it up to you.  Feel free to tweak the message text too.  I
> don't anticipate any further changes near those areas, so conflicts are
> unlikely.

I WILL have a look, I just don't know what month quite yet.

-- 
D. Michael McIntyre

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-01 Thread Abrolag
On Fri, 1 Apr 2016 06:33:11 -0400
Ted Felix  wrote:

> On 04/01/2016 03:49 AM, Kevin Donnelly wrote:
> > The only thing I'd suggest is that it might be handy to give the
> > location of the lock file.  
> 
>Absolutely.  It's actually in there.  I just removed it to focus the 
> discussion on the explanation.  It also displays the user/time/host that 
> created the lock so you can walk over to their "office" and ask if they 
> are really still working on that file from three days ago.  All of this 
> is also in the lock file as plain text so you can just "cat" it to 
> figure out what's going on.
> 
> Ted.
> 

Well that completely answers the questions I was going to ask! Good forward
thinking :)

-- 
W J G

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-04-01 Thread Kevin Donnelly
Hi Ted

On 31/03/16 21:00, Ted Felix wrote:
> How about this: "Could not lock file. Another user or instance of 
> Rosegarden may already be editing this file. If you are sure no one 
> else is editing this file, delete the lock file and try again."

The only thing I'd suggest is that it might be handy to give the 
location of the lock file.

-- 
Kevin Donnelly
kevindonnelly.org.uk
cymraeg.org.uk


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-03-31 Thread D. Michael McIntyre
On 03/31/2016 05:34 PM, Yves Guillemot wrote:

>> OK, I figured somebody would find something like this.  Is there
>> something we can do about this?
>
> Usually QString::fromStdString() does the conversion.

Meant to mention I'll be happy to fiddle with that part of it if you 
don't get it worked out, Ted.

-- 
D. Michael McIntyre

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-03-31 Thread Yves Guillemot
Le jeudi 31 mars 2016, 16:00:12 Ted Felix a écrit :
> 
>How about this:
> 
> "Could not lock file.  Another user or instance of Rosegarden may
> already be editing this file.  If you are sure no one else is editing
> this file, delete the lock file and try again."
> 

Seems very good to me.

Yves


--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-03-31 Thread Yves Guillemot
Le jeudi 31 mars 2016, 15:53:23 Ted Felix a écrit :
> On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> > the displayed lock file name when the .rg file uses non ASCII characters
> > (I did the first test with a file name containing a diacritic).
> 
>OK, I figured somebody would find something like this.  Is there
> something we can do about this?

Usually QString::fromStdString() does the conversion.

Yves

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-03-31 Thread Ted Felix
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> An other (very) small problem is the "Could not lock file" message which may 
> be
> unclear for some users.
> An improvment should be to add in the popup a first sentence explaining that
> two different RG instances try to access the same file.

   How about this:

"Could not lock file.  Another user or instance of Rosegarden may 
already be editing this file.  If you are sure no one else is editing 
this file, delete the lock file and try again."

Ted.

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-03-31 Thread Ted Felix
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> Then I tried a less obvious case:

   Thanks for finding that.  I'll have a look.

> There is a small issue (repeatedly occurring with RG) about UTF8 garbage in
> the displayed lock file name when the .rg file uses non ASCII characters (I 
> did
> the first test with a file name containing a diacritic).

   OK, I figured somebody would find something like this.  Is there 
something we can do about this?

> An other (very) small problem is the "Could not lock file" message which may 
> be
> unclear for some users.
> An improvment should be to add in the popup a first sentence explaining that
> two different RG instances try to access the same file.

   The wording is just a rough draft, so suggestions are definitely 
appreciated.  I'll see what I can come up with.

Ted.

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] File Locking

2016-03-31 Thread Yves Guillemot
Le mercredi 30 mars 2016, 23:03:12 Ted Felix a écrit :
>Just finished implementing file locking (see bug #1510) to prevent
> having a file open in two instances of rg.  I would appreciate any
> testing anyone can do.

>The obvious test case to see the new behavior is to launch rg twice
> and try to open the same file with each instance.

I first tried the obvious case:

 - Open a file in a first RG instance
 - Try to open the same file from an other RG instance
 => Can't open the file in the new instance: a popup with a "could not lock 
file" message is displayed.

 - Close the file in the first RG instance
 - Try again to open the file in the second instance
 => file is normally opened.

 - Kill the second instance (Ctrl-C)
 - Try to open the file in the first instance
 => Can't open the file, the popup is displayed.

 - rm the lock file (whose name is given in the popup)
 - Try again to open the file in the first instance
 => file is normally opened.

 - Create a new RG instance 
 - Try to open the same file from this new instance
 => Can't open the file, the popup is displayed.


Then I tried a less obvious case:

 - Create a new composition in RG and save it in a file. Keep RG open.
 - Create again a new composition in another RG instance
 - Try to save the last composition in the same file as fhe first one. 
 => Can't save the file, the popup is displayed.

 - Try again the same save operation
 => no more popup.

There is now two RG instances able to write alternatively in the same file.


So, except this last problem, it works fine here.

There is a small issue (repeatedly occurring with RG) about UTF8 garbage in 
the displayed lock file name when the .rg file uses non ASCII characters (I did 
the first test with a file name containing a diacritic).

An other (very) small problem is the "Could not lock file" message which may be 
unclear for some users. 
An improvment should be to add in the popup a first sentence explaining that 
two different RG instances try to access the same file.

Yves




--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user