basilisk-devel — Basilisk II development-related discussion

[B2-devel] Building BII GUI under Lion

[C.W. B. <com...@ho...>]

I've been trying to build the OS X GUI under Lion, but have run into major obstacles. For one, the video_macosx class is using functions that aren't available under Lion (CGDisplayBaseAddress,  CGDisplayBytesPerRow, CGDisplayBitsPerPixel). Also, it seems to want to write straight to the display, which is a no-no now. Also, it looks like the whole CGPallette support is deprecated in Lion. While I have worked around the missing CGDisplayBytesPerRow, I think the move away from CGDisplayBaseAddress will be more of a challenge, and I don't know what to say about the deprecation of CGPallettes. Another thing is that it uses a lot of deprecated calls, which should probably be cleaned up before they're removed.

Re: [B2-devel] [PATCH] Yet another clipboard patch for Basilisk / SheepShaver

[Alexei S. <ale...@gm...>]

Committed. Thanks.

On Thu, Jul 12, 2012 at 5:41 PM, Charles Srstka <
bas...@ch...> wrote:

> This patch introduces a few changes:
>
> 1. Data of arbitrary Mac OS types which aren't handled (i.e. non
> text/picture types) will now be passed through to the host pasteboard, just
> like in the 32-bit code.
>
> 2. Reorganization of a few things.
>
> 3. Fixed a memory leak (whoops).
>
> I'm basically submitting this patch now because I have a few other changes
> I'm going to try, but since I'm not sure that they're going to work, I
> thought it better to flush out the changes I've already made at this point
> first.
>
> Thanks,
> Charles
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>

[B2-devel] [PATCH] Yet another clipboard patch for Basilisk / SheepShaver

[Charles S. <bas...@ch...>]

This patch introduces a few changes:

1. Data of arbitrary Mac OS types which aren't handled (i.e. non text/picture types) will now be passed through to the host pasteboard, just like in the 32-bit code.

2. Reorganization of a few things.

3. Fixed a memory leak (whoops).

I'm basically submitting this patch now because I have a few other changes I'm going to try, but since I'm not sure that they're going to work, I thought it better to flush out the changes I've already made at this point first.

Thanks,
Charles

Re: [B2-devel] How do I get removed from this list?

[Frank T. <fra...@gm...>]

Follow the link at the bottom of any message from the list to the list
information page. Scroll to the button that says Unsubscribe or edit
options. Enter your e-mail address and click the button. Follow the
instructions from there.

On Thu, Jul 12, 2012 at 11:20 AM, Mark Poehlmann <mar...@ao...> wrote:

> How do I get removed from this list?  I no longer need it anymore.  If
> there is someone out there that can remove me from this list, I would be
> extremely happy.  Thank you.
>
> Mark
>
>
> On Jul 11, 2012, at 6:24 PM, Kevin Jaques (at home) wrote:
>
> > I am a user dependent on Sheepshaver who would also love to have the
> clipboard repaired. The issue is entirely about the Classic Mac system
> being aware that there has been an application switch. In the Classic Mac,
> the system would monitor that. However when the Classic Mac is running in
> emulation, it can't tell when there has been a switch to an application of
> the host system. That's where Sheepshaver, as the emulater, must assume
> that responsibility, and inform the Classic Mac system about the switch.
> >
> > Right now, I can ensure a copy works by keeping an intermediary Classic
> Mac app. I mainly use Stickies for that purpose, because it strips
> formatting when it copies. If I want to keep the formatting, I use Word
> 5.1. So, from my Classic app, I copy, then go to the intermediary Classic
> app and paste. Then I switch to Mac X and can paste.
> >
> > To copy from Mac X, I must go to the intermediary Classic app, then
> switch to the intended Classic Mac target, then switch to the Mac X app and
> copy. Then I return to the intended Classic Mac target. I still can't
> paste. If I attempt to do so, it will bugger the process and I will have to
> start over. Instead, I must go to the intermediate Classic Mac app and
> paste. THEN I return for the 3rd time to the intended Classic Mac target
> and can now paste.
> >
> > It's not quite that simple. Sometimes it will work with the first paste
> of the day. Sometimes it will just work for no reason I can see. But the
> above method is the only way to be sure it will work.
> >
> > It seems like a simple solution would be to create a dummy Classic app.
> Then whenever Sheepshaver loses focus, it would make note of the current
> Classic Mac app (the 'departed'), and switch to the dummy Classic Mac app,
> triggering a clipboard update. Then when Sheepshaver gets focus back, it
> would tell Classic Mac to return to the 'departed' app, triggering another
> clipboard update. I don't know whether Sheepshaver would have to update the
> Mac X clipboard or whether than happens automatically with the change in
> focus.
> >
> > Weirdly, the old Classic Mac application 4D has no problems with the
> clipboard. It must have fanatically triggered a clipboard update every time
> it was used, or maybe it didn't keep a private clipboard. Anyway, pretty
> much every other Classic Mac app must have tried to be efficient, and is
> consequently being a pain in the ass.
> >
> > On Jul. 10, 2012, at 05:23 , Ronald P. Regensburg wrote:
> >
> >> I installed the TESyncScrap extension in MacOS 9.0.4 in my latest
> SheepShaver 2.4 build and, of course, restarted. The system recognizes the
> file as extension.
> >>
> >> However, it does not change anything to the behavior, in both
> directions, when trying to copy and paste text between OSX TexEdit and
> MacOS AppleWorks. It is exactly the same as I described yesterday, both the
> behavior in 32-bit mode and the behavior in 64-bit mode.
> >>
> >> While trying this with and without the TESyncScrap extension, I found
> the easiest way to have copy and paste between TextEdit and AppleWorks work
> in 64-bit mode. Just leave the Clipboard window in MacOS Finder open. With
> the Clipboard window open, not only switching to the MacOS Finder after
> copying in AppleWorks works to paste in TextEdit but also, after copying in
> TextEdit, pasting in AppleWorks works after switching from AppleWorks to
> the MacOS Finder and back again to AppleWorks.
> >>
> >>
> >> Ronald.
> >>
> >> ----------------------------------------
> >> Op 10 juli 2012, om 12:26, schreef Ronald P. Regensburg:
> >>
> >>
> >> Ah! Apparently MacBinary. I have seen thousands of MacBinary files in
> past decades, always with a .bin file extension. This is the first time I
> see a .mbin extension.
> >>
> >> I will try the extension to see if it solves the issues with AppleWorks
> and clipboard synchronizing.
> >>
> >> Ronald.
> >>
> >> ----------------------------------------
> >> Op 10 juli 2012, om 11:55, schreef Ronald P. Regensburg:
> >>
> >> What is a .mbin file? How do I use this?
> >>
> >> Ronald.
> >>
> >> ----------------------------------------
> >> Op 10 juli 2012, om 02:27, schreef Josh Juran:
> >>
> >>> On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:
> >>>
> >>>> Have you tried using the Mac OS extension that Jean-Pierre posted
> >>>> to this list some time ago?
> >>>>
> >>>> I think it's meant to solve exactly the problem of needing to
> >>>> change app focus before clipboard changes "stick".
> >>>>
> >>>> I'd be curious to know whether it improves things for you.
> >>>
> >>> Are you referring to TESyncScrap?
> >>>
> >>> "Typical non-Carbon apps synchronize the system clipboard with the
> >>> TextEdit clipboard when you switch layers, i.e. bring another app
> >>> forward. If in between copying text and switching layers the app
> >>> crashes, or quits without synchronizing, or you're running it in an
> >>> emulator and you try to paste in another app in the host OS, you'll
> >>> get stale data. A similar issue pertains to pasting into the
> >>> emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy
> >>> and just before Paste (like Carbon apps do), avoiding these issues."
> >>>
> >>> http://www.jjuran.org/hacks/TESyncScrap.mbin
> >>>
> >>> Josh
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Live Security Virtual Conference
> >> Exclusive live event will cover all the ways today's security and
> >> threat landscape has changed and how IT managers can respond.
> Discussions
> >> will include endpoint security, mobile security and the latest in
> malware
> >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >> _______________________________________________
> >> basilisk-devel mailing list
> >> bas...@li...
> >> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
> >
> > --
> > Sincerely, Kevin Jaques (at home)
> >
> > Download my Electronic Business Card by right-clicking the following
> link, or by pasting it into your browser, then saving the page to ".vcf"
> format.
> > http://www.hierlaw.com/Dr.KevinJaquesB.A.,J.D..vcf
> >
> > Use ja...@hi... for work related messages
> >
> > "Send lawyers, guns and money! Dad get me out of this!" - Warren Zevon
> >
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > basilisk-devel mailing list
> > bas...@li...
> > https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>

[B2-devel] How do I get removed from this list?

[Mark P. <mar...@ao...>]

How do I get removed from this list?  I no longer need it anymore.  If there is someone out there that can remove me from this list, I would be extremely happy.  Thank you.

Mark


On Jul 11, 2012, at 6:24 PM, Kevin Jaques (at home) wrote:

> I am a user dependent on Sheepshaver who would also love to have the clipboard repaired. The issue is entirely about the Classic Mac system being aware that there has been an application switch. In the Classic Mac, the system would monitor that. However when the Classic Mac is running in emulation, it can't tell when there has been a switch to an application of the host system. That's where Sheepshaver, as the emulater, must assume that responsibility, and inform the Classic Mac system about the switch.
> 
> Right now, I can ensure a copy works by keeping an intermediary Classic Mac app. I mainly use Stickies for that purpose, because it strips formatting when it copies. If I want to keep the formatting, I use Word 5.1. So, from my Classic app, I copy, then go to the intermediary Classic app and paste. Then I switch to Mac X and can paste. 
> 
> To copy from Mac X, I must go to the intermediary Classic app, then switch to the intended Classic Mac target, then switch to the Mac X app and copy. Then I return to the intended Classic Mac target. I still can't paste. If I attempt to do so, it will bugger the process and I will have to start over. Instead, I must go to the intermediate Classic Mac app and paste. THEN I return for the 3rd time to the intended Classic Mac target and can now paste.
> 
> It's not quite that simple. Sometimes it will work with the first paste of the day. Sometimes it will just work for no reason I can see. But the above method is the only way to be sure it will work.
> 
> It seems like a simple solution would be to create a dummy Classic app. Then whenever Sheepshaver loses focus, it would make note of the current Classic Mac app (the 'departed'), and switch to the dummy Classic Mac app, triggering a clipboard update. Then when Sheepshaver gets focus back, it would tell Classic Mac to return to the 'departed' app, triggering another clipboard update. I don't know whether Sheepshaver would have to update the Mac X clipboard or whether than happens automatically with the change in focus.
> 
> Weirdly, the old Classic Mac application 4D has no problems with the clipboard. It must have fanatically triggered a clipboard update every time it was used, or maybe it didn't keep a private clipboard. Anyway, pretty much every other Classic Mac app must have tried to be efficient, and is consequently being a pain in the ass.
> 
> On Jul. 10, 2012, at 05:23 , Ronald P. Regensburg wrote:
> 
>> I installed the TESyncScrap extension in MacOS 9.0.4 in my latest SheepShaver 2.4 build and, of course, restarted. The system recognizes the file as extension.
>> 
>> However, it does not change anything to the behavior, in both directions, when trying to copy and paste text between OSX TexEdit and MacOS AppleWorks. It is exactly the same as I described yesterday, both the behavior in 32-bit mode and the behavior in 64-bit mode.
>> 
>> While trying this with and without the TESyncScrap extension, I found the easiest way to have copy and paste between TextEdit and AppleWorks work in 64-bit mode. Just leave the Clipboard window in MacOS Finder open. With the Clipboard window open, not only switching to the MacOS Finder after copying in AppleWorks works to paste in TextEdit but also, after copying in TextEdit, pasting in AppleWorks works after switching from AppleWorks to the MacOS Finder and back again to AppleWorks.
>> 
>> 
>> Ronald.
>> 
>> ----------------------------------------
>> Op 10 juli 2012, om 12:26, schreef Ronald P. Regensburg:
>> 
>> 
>> Ah! Apparently MacBinary. I have seen thousands of MacBinary files in past decades, always with a .bin file extension. This is the first time I see a .mbin extension.
>> 
>> I will try the extension to see if it solves the issues with AppleWorks and clipboard synchronizing.
>> 
>> Ronald.
>> 
>> ----------------------------------------
>> Op 10 juli 2012, om 11:55, schreef Ronald P. Regensburg:
>> 
>> What is a .mbin file? How do I use this?
>> 
>> Ronald.
>> 
>> ----------------------------------------
>> Op 10 juli 2012, om 02:27, schreef Josh Juran:
>> 
>>> On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:
>>> 
>>>> Have you tried using the Mac OS extension that Jean-Pierre posted  
>>>> to this list some time ago?
>>>> 
>>>> I think it's meant to solve exactly the problem of needing to  
>>>> change app focus before clipboard changes "stick".
>>>> 
>>>> I'd be curious to know whether it improves things for you.
>>> 
>>> Are you referring to TESyncScrap?
>>> 
>>> "Typical non-Carbon apps synchronize the system clipboard with the  
>>> TextEdit clipboard when you switch layers, i.e. bring another app  
>>> forward. If in between copying text and switching layers the app  
>>> crashes, or quits without synchronizing, or you're running it in an  
>>> emulator and you try to paste in another app in the host OS, you'll  
>>> get stale data. A similar issue pertains to pasting into the  
>>> emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy  
>>> and just before Paste (like Carbon apps do), avoiding these issues."
>>> 
>>> http://www.jjuran.org/hacks/TESyncScrap.mbin
>>> 
>>> Josh
>> 
>> 
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and 
>> threat landscape has changed and how IT managers can respond. Discussions 
>> will include endpoint security, mobile security and the latest in malware 
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> basilisk-devel mailing list
>> bas...@li...
>> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
> 
> --
> Sincerely, Kevin Jaques (at home)
> 
> Download my Electronic Business Card by right-clicking the following link, or by pasting it into your browser, then saving the page to ".vcf" format.
> http://www.hierlaw.com/Dr.KevinJaquesB.A.,J.D..vcf
> 
> Use ja...@hi... for work related messages
> 
> "Send lawyers, guns and money! Dad get me out of this!" - Warren Zevon
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

Oops!

I see that I made a mistake. In the test descriptions I wrote "clipboard" where it should be "desktop". Copying and pasting within the message spread the mistake. I read and re-read before sending, but I did not see the mistake. Blame it on my dyslexia.

Here are the corrected test descriptions:

These tests are all done with SheepShaver, built from source after the latest (July 07, 2012) commits, running in 64-bit mode in OSX 10.7.4 (Lion). TextEdit is kept running all the time during these tests. Each test starts with SheepShaver not running.


Test 1.

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In TextEdit copy CCC
In AppleWorks paste CCC

In TextEdit copy DDD
click on the OS9 desktop
click in AppleWorks document window
In AppleWorks paste DDD

In TextEdit copy EEE
In AppleWorks paste DDD

In TextEdit copy FFF
click on the OS9 desktop
click in AppleWorks document window
In AppleWorks paste DDD

This is what I mentioned above: After switching to the OS9 Finder the problem starts. The same text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 2. (AppleWorks is launched after copying in TextEdit)

Start up SheepShaver

In TextEdit copy AAA
Launch AppleWorks and open a new text document
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste AAA

In TextEdit copy CCC
click on the OS9 desktop
click in AppleWorks document window
In AppleWorks paste AAA

If the text is copied in TextEdit before AppleWorks is launched, that text will be pasted in AppleWorks once. After that, the same text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 3. (Effect of copying in AppleWorks)

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In AppleWorks copy CCC
(In AppleWorks paste CCC)
The result will be the same whether or not is pasted in AppleWorks here.

In TextEdit copy DDD
In AppleWorks paste CCC

In TextEdit copy EEE
click on the OS9 desktop
click in AppleWorks document window
In AppleWorks paste CCC

After copying text in AppleWorks, that text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 4. (the same as test 3. but now copying in SimpleText)

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In SimpleText copy CCC
(In AppleWorks paste CCC)
The result will be the same whether or not is pasted in AppleWorks here.

In TextEdit copy DDD
In AppleWorks paste CCC

In TextEdit copy EEE
click on the OS9 desktop
click in AppleWorks document window
In AppleWorks paste CCC

After copying text in SimpleText, that text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.



Now a few examples of how AppleWorks can be made to always paste the text that was copied in TextEdit. These examples will work after the problem has started (as demonstrated above):

Example 1.

In TextEdit copy GGG
Click on the OS9 desktop and choose Show Clipboard from the Finder Edit menu and leave the Clipboard window open.
In AppleWorks paste GGG

In TextEdit HHH 
Click on the OS9 desktop
In AppleWorks paste HHH

In TextEdit copy III
Click on the OS9 desktop and close the Clipboard window
In AppleWorks paste III

In TextEdit copy JJJ
Click on the OS9 desktop
In AppleWorks paste III

Switching to the Finder with the Clipboard window open enables pasting in AppleWorks the text that was copied in TextEdit. Switching to the Finder without the Clipboard window open does not work.


Example 2.

In TextEdit copy GGG
Launch SimpleText and make sure a document window is opened
In AppleWorks paste GGG

In TextEdit HHH 
Bring the SimpleText to the front
In AppleWorks paste HHH

In TextEdit copy III
Bring SimpleText to the front and close the SimpleText document window without quitting SimpleText
In AppleWorks paste III

In TextEdit copy JJJ
Switch to SimpleText
In AppleWorks paste III

Switching to SimpleText with a SimpleText document open works the same as switching to the Finder with the Clipboard window open to enable pasting in AppleWorks the text that was copied in TextEdit. Switching to SimpleText without a SimpleText window open does not work.

Note that pasting or copying in SimpleText is not needed.


Example 3.

Identical to Example 2. but now with ResEdit and a new new ResEdit file window open.


Ronald.


----------------------------------------
Op 12 juli 2012, om 15:04, schreef Ronald P. Regensburg:


Op 11 juli 2012, om 21:47, schreef Charles Srstka:

> Ronald, could you try the following? I’m curious whether this works:
> 
> 1. Open AppleWorks, copy in TextEdit, click on emulated desktop, then bring AppleWorks back to the front, then paste in AppleWorks.

There is no simple answer to that question. The paste behavior of AppleWorks (pasting text that was copied in TextEdit) is not constant. After certain actions it changes (the problem then becomes manifest) and the change/problem persists until SheepShaver is quit and launched again.

Short answer 1.: No, on the contrary, it is one of the actions that initiates the issue AppleWorks has with pasting text that was copied in TextEdit.

Short answer 2.: Yes, if the Clipboard window is left open in the OS9 Finder.

See below for more information.


> 2. Copy in AppleWorks, click on emulated desktop, bring AppleWorks back to the front, then paste in TextEdit.

Yes. AppleWorks does not need to brought back to the front. This works always:

Copy in AppleWorks, click on the emulated desktop, then paste in TextEdit.


Here are examples of what I see when trying to copy in OSX TextEdit and paste in OS9 AppleWorks. It took me some time to find recurring patterns in the changing paste behavior in AppleWorks.

These tests are all done with SheepShaver, built from source after the latest (July 07, 2012) commits, running in 64-bit mode in OSX 10.7.4 (Lion). TextEdit is kept running all the time during these tests. Each test starts with SheepShaver not running.


Test 1.

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In TextEdit copy CCC
In AppleWorks paste CCC

In TextEdit copy DDD
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste DDD

In TextEdit copy EEE
In AppleWorks paste DDD

In TextEdit copy FFF
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste DDD

This is what I mentioned above: After switching to the OS9 Finder the problem starts. The same text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 2. (AppleWorks is launched after copying in TextEdit)

Start up SheepShaver

In TextEdit copy AAA
Launch AppleWorks and open a new text document
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste AAA

In TextEdit copy CCC
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste AAA

If the text is copied in TextEdit before AppleWorks is launched, that text will be pasted in AppleWorks once. After that, the same text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 3. (Effect of copying in AppleWorks)

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In AppleWorks copy CCC
(In AppleWorks paste CCC)
The result will be the same whether or not is pasted in AppleWorks here.

In TextEdit copy DDD
In AppleWorks paste CCC

In TextEdit copy EEE
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste CCC

After copying text in AppleWorks, that text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 4. (the same as test 3. but now copying in SimpleText)

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In SimpleText copy CCC
(In AppleWorks paste CCC)
The result will be the same whether or not is pasted in AppleWorks here.

In TextEdit copy DDD
In AppleWorks paste CCC

In TextEdit copy EEE
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste CCC

After copying text in SimpleText, that text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.



Now a few examples of how AppleWorks can be made to always paste the text that was copied in TextEdit. These examples will work after the problem has started (as demonstrated above):

Example 1.

In TextEdit copy GGG
Click on the OS9 desktop and choose Show Clipboard from the Finder Edit menu and leave the Clipboard window open.
In AppleWorks paste GGG

In TextEdit HHH 
Click on the OS9 desktop
In AppleWorks paste HHH

In TextEdit copy III
Click on the OS9 desktop and close the Clipboard window
In AppleWorks paste III

In TextEdit copy JJJ
Click on the OS9 desktop
In AppleWorks paste III

Switching to the Finder with the Clipboard window open enables pasting in AppleWorks the text that was copied in TextEdit. Switching to the Finder without the Clipboard window open does not work.


Example 2.

In TextEdit copy GGG
Launch SimpleText and make sure a document window is opened
In AppleWorks paste GGG

In TextEdit HHH 
Bring the SimpleText to the front
In AppleWorks paste HHH

In TextEdit copy III
Bring SimpleText to the front and close the SimpleText document window without quitting SimpleText
In AppleWorks paste III

In TextEdit copy JJJ
Switch to SimpleText
In AppleWorks paste III

Switching to SimpleText with a SimpleText document open works the same as switching to the Finder with the Clipboard window open to enable pasting in AppleWorks the text that was copied in TextEdit. Switching to SimpleText without a SimpleText window open does not work.

Note that pasting or copying in SimpleText is not needed.


Example 3.

Identical to Example 2. but now with ResEdit and a new new ResEdit file window open.



I hope all of this makes sense.


Ronald.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
basilisk-devel mailing list
bas...@li...
https://lists.sourceforge.net/lists/listinfo/basilisk-devel

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

Op 11 juli 2012, om 21:47, schreef Charles Srstka:

> Ronald, could you try the following? I’m curious whether this works:
> 
> 1. Open AppleWorks, copy in TextEdit, click on emulated desktop, then bring AppleWorks back to the front, then paste in AppleWorks.

There is no simple answer to that question. The paste behavior of AppleWorks (pasting text that was copied in TextEdit) is not constant. After certain actions it changes (the problem then becomes manifest) and the change/problem persists until SheepShaver is quit and launched again.

Short answer 1.: No, on the contrary, it is one of the actions that initiates the issue AppleWorks has with pasting text that was copied in TextEdit.

Short answer 2.: Yes, if the Clipboard window is left open in the OS9 Finder.

See below for more information.


> 2. Copy in AppleWorks, click on emulated desktop, bring AppleWorks back to the front, then paste in TextEdit.

Yes. AppleWorks does not need to brought back to the front. This works always:

Copy in AppleWorks, click on the emulated desktop, then paste in TextEdit.


Here are examples of what I see when trying to copy in OSX TextEdit and paste in OS9 AppleWorks. It took me some time to find recurring patterns in the changing paste behavior in AppleWorks.

These tests are all done with SheepShaver, built from source after the latest (July 07, 2012) commits, running in 64-bit mode in OSX 10.7.4 (Lion). TextEdit is kept running all the time during these tests. Each test starts with SheepShaver not running.


Test 1.

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In TextEdit copy CCC
In AppleWorks paste CCC

In TextEdit copy DDD
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste DDD

In TextEdit copy EEE
In AppleWorks paste DDD

In TextEdit copy FFF
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste DDD

This is what I mentioned above: After switching to the OS9 Finder the problem starts. The same text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 2. (AppleWorks is launched after copying in TextEdit)

Start up SheepShaver

In TextEdit copy AAA
Launch AppleWorks and open a new text document
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste AAA

In TextEdit copy CCC
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste AAA

If the text is copied in TextEdit before AppleWorks is launched, that text will be pasted in AppleWorks once. After that, the same text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 3. (Effect of copying in AppleWorks)

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In AppleWorks copy CCC
(In AppleWorks paste CCC)
The result will be the same whether or not is pasted in AppleWorks here.

In TextEdit copy DDD
In AppleWorks paste CCC

In TextEdit copy EEE
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste CCC

After copying text in AppleWorks, that text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.


Test 4. (the same as test 3. but now copying in SimpleText)

Start up SheepShaver
Launch AppleWorks and open a new text document

In TextEdit copy AAA
In AppleWorks paste AAA

In TextEdit copy BBB
In AppleWorks paste BBB

In SimpleText copy CCC
(In AppleWorks paste CCC)
The result will be the same whether or not is pasted in AppleWorks here.

In TextEdit copy DDD
In AppleWorks paste CCC

In TextEdit copy EEE
click on the OS9 clipboard
click in AppleWorks document window
In AppleWorks paste CCC

After copying text in SimpleText, that text will continue to be pasted in AppleWorks, no matter what has been copied in TextEdit.



Now a few examples of how AppleWorks can be made to always paste the text that was copied in TextEdit. These examples will work after the problem has started (as demonstrated above):

Example 1.

In TextEdit copy GGG
Click on the OS9 desktop and choose Show Clipboard from the Finder Edit menu and leave the Clipboard window open.
In AppleWorks paste GGG

In TextEdit HHH 
Click on the OS9 desktop
In AppleWorks paste HHH

In TextEdit copy III
Click on the OS9 desktop and close the Clipboard window
In AppleWorks paste III

In TextEdit copy JJJ
Click on the OS9 desktop
In AppleWorks paste III

Switching to the Finder with the Clipboard window open enables pasting in AppleWorks the text that was copied in TextEdit. Switching to the Finder without the Clipboard window open does not work.


Example 2.

In TextEdit copy GGG
Launch SimpleText and make sure a document window is opened
In AppleWorks paste GGG

In TextEdit HHH 
Bring the SimpleText to the front
In AppleWorks paste HHH

In TextEdit copy III
Bring SimpleText to the front and close the SimpleText document window without quitting SimpleText
In AppleWorks paste III

In TextEdit copy JJJ
Switch to SimpleText
In AppleWorks paste III

Switching to SimpleText with a SimpleText document open works the same as switching to the Finder with the Clipboard window open to enable pasting in AppleWorks the text that was copied in TextEdit. Switching to SimpleText without a SimpleText window open does not work.

Note that pasting or copying in SimpleText is not needed.


Example 3.

Identical to Example 2. but now with ResEdit and a new new ResEdit file window open.



I hope all of this makes sense.


Ronald.

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

The latest version of AppleWorks contains two applications, the "MacOSClassic" version AppleWorks 6.2.8 and the "MacOS" (MacOSX) version AppleWorks 6.2.9. AppleWorks 6.2.9 certainly is a Carbon application. I am not sure if it proves that AppleWorks 6.2.8 is not a Carbon application, but AppleWorks 6.2.8 runs fine in MacOS 9.0.4 without the CarbonLib extension.

As, apparently, the same issues were reported by Lew Irwin using ClarisWorks, I suppose it must be ClarisWorks/AppleWorks not using TextEdit scrap routines.


(I will later answer the question asked by Charles Srstka yesterday. The question cannot be answered by a simple yes or no.)


Ronald.


Op 12 juli 2012, om 05:19, schreef Josh Juran:

> 
> I recall that AppleWorks 6 is a Carbon application, so TESyncScrap  
> would have no effect in this case.  Also, TESyncScrap only concerns  
> the TextEdit scrap routines; applications which don't use TextEdit  
> (or otherwise don't call TE{Cut,Copy,Paste}()) aren't affected.
> 
> Josh

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Josh J. <jj...@gm...>]

On Jul 10, 2012, at 4:23 AM, Ronald P. Regensburg wrote:

> I installed the TESyncScrap extension in MacOS 9.0.4 in my latest  
> SheepShaver 2.4 build and, of course, restarted. The system  
> recognizes the file as extension.
>
> However, it does not change anything to the behavior, in both  
> directions, when trying to copy and paste text between OSX TexEdit  
> and MacOS AppleWorks. It is exactly the same as I described  
> yesterday, both the behavior in 32-bit mode and the behavior in 64- 
> bit mode.

I recall that AppleWorks 6 is a Carbon application, so TESyncScrap  
would have no effect in this case.  Also, TESyncScrap only concerns  
the TextEdit scrap routines; applications which don't use TextEdit  
(or otherwise don't call TE{Cut,Copy,Paste}()) aren't affected.

Josh

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Josh J. <jj...@gm...>]

On Jul 10, 2012, at 3:26 AM, Ronald P. Regensburg wrote:

> Ah! Apparently MacBinary. I have seen thousands of MacBinary files  
> in past decades, always with a .bin file extension. This is the  
> first time I see a .mbin extension.

It's true that most MacBinary files use .bin.  But .bin is also used  
for other kinds of binary files, like disk images, and I wanted to  
avoid ambiguity.

Josh

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Kevin J. (at home) <kj...@gm...>]

I am a user dependent on Sheepshaver who would also love to have the clipboard repaired. The issue is entirely about the Classic Mac system being aware that there has been an application switch. In the Classic Mac, the system would monitor that. However when the Classic Mac is running in emulation, it can't tell when there has been a switch to an application of the host system. That's where Sheepshaver, as the emulater, must assume that responsibility, and inform the Classic Mac system about the switch.

Right now, I can ensure a copy works by keeping an intermediary Classic Mac app. I mainly use Stickies for that purpose, because it strips formatting when it copies. If I want to keep the formatting, I use Word 5.1. So, from my Classic app, I copy, then go to the intermediary Classic app and paste. Then I switch to Mac X and can paste. 

To copy from Mac X, I must go to the intermediary Classic app, then switch to the intended Classic Mac target, then switch to the Mac X app and copy. Then I return to the intended Classic Mac target. I still can't paste. If I attempt to do so, it will bugger the process and I will have to start over. Instead, I must go to the intermediate Classic Mac app and paste. THEN I return for the 3rd time to the intended Classic Mac target and can now paste.

It's not quite that simple. Sometimes it will work with the first paste of the day. Sometimes it will just work for no reason I can see. But the above method is the only way to be sure it will work.

It seems like a simple solution would be to create a dummy Classic app. Then whenever Sheepshaver loses focus, it would make note of the current Classic Mac app (the 'departed'), and switch to the dummy Classic Mac app, triggering a clipboard update. Then when Sheepshaver gets focus back, it would tell Classic Mac to return to the 'departed' app, triggering another clipboard update. I don't know whether Sheepshaver would have to update the Mac X clipboard or whether than happens automatically with the change in focus.

Weirdly, the old Classic Mac application 4D has no problems with the clipboard. It must have fanatically triggered a clipboard update every time it was used, or maybe it didn't keep a private clipboard. Anyway, pretty much every other Classic Mac app must have tried to be efficient, and is consequently being a pain in the ass.

On Jul. 10, 2012, at 05:23 , Ronald P. Regensburg wrote:

> I installed the TESyncScrap extension in MacOS 9.0.4 in my latest SheepShaver 2.4 build and, of course, restarted. The system recognizes the file as extension.
> 
> However, it does not change anything to the behavior, in both directions, when trying to copy and paste text between OSX TexEdit and MacOS AppleWorks. It is exactly the same as I described yesterday, both the behavior in 32-bit mode and the behavior in 64-bit mode.
> 
> While trying this with and without the TESyncScrap extension, I found the easiest way to have copy and paste between TextEdit and AppleWorks work in 64-bit mode. Just leave the Clipboard window in MacOS Finder open. With the Clipboard window open, not only switching to the MacOS Finder after copying in AppleWorks works to paste in TextEdit but also, after copying in TextEdit, pasting in AppleWorks works after switching from AppleWorks to the MacOS Finder and back again to AppleWorks.
> 
> 
> Ronald.
> 
> ----------------------------------------
> Op 10 juli 2012, om 12:26, schreef Ronald P. Regensburg:
> 
> 
> Ah! Apparently MacBinary. I have seen thousands of MacBinary files in past decades, always with a .bin file extension. This is the first time I see a .mbin extension.
> 
> I will try the extension to see if it solves the issues with AppleWorks and clipboard synchronizing.
> 
> Ronald.
> 
> ----------------------------------------
> Op 10 juli 2012, om 11:55, schreef Ronald P. Regensburg:
> 
> What is a .mbin file? How do I use this?
> 
> Ronald.
> 
> ----------------------------------------
> Op 10 juli 2012, om 02:27, schreef Josh Juran:
> 
>> On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:
>> 
>>> Have you tried using the Mac OS extension that Jean-Pierre posted  
>>> to this list some time ago?
>>> 
>>> I think it's meant to solve exactly the problem of needing to  
>>> change app focus before clipboard changes "stick".
>>> 
>>> I'd be curious to know whether it improves things for you.
>> 
>> Are you referring to TESyncScrap?
>> 
>> "Typical non-Carbon apps synchronize the system clipboard with the  
>> TextEdit clipboard when you switch layers, i.e. bring another app  
>> forward. If in between copying text and switching layers the app  
>> crashes, or quits without synchronizing, or you're running it in an  
>> emulator and you try to paste in another app in the host OS, you'll  
>> get stale data. A similar issue pertains to pasting into the  
>> emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy  
>> and just before Paste (like Carbon apps do), avoiding these issues."
>> 
>> http://www.jjuran.org/hacks/TESyncScrap.mbin
>> 
>> Josh
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel

--
Sincerely, Kevin Jaques (at home)

Download my Electronic Business Card by right-clicking the following link, or by pasting it into your browser, then saving the page to ".vcf" format.
http://www.hierlaw.com/Dr.KevinJaquesB.A.,J.D..vcf

Use ja...@hi... for work related messages

"Send lawyers, guns and money! Dad get me out of this!" - Warren Zevon

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Charles S. <bas...@ch...>]

Sorry about my absence for the last couple of days; turns out that I absent-mindedly left the quota size at the far-too-low default when setting up the e-mail address that I’m using with this list, and it filled up, causing me to miss a number of messages. I’ve since caught up using the web archive.

Ronald, could you try the following? I’m curious whether this works:

1. Open AppleWorks, copy in TextEdit, click on emulated desktop, then bring AppleWorks back to the front, then paste in AppleWorks.

2. Copy in AppleWorks, click on emulated desktop, bring AppleWorks back to the front, then paste in TextEdit.

Charles

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

I installed the TESyncScrap extension in MacOS 9.0.4 in my latest SheepShaver 2.4 build and, of course, restarted. The system recognizes the file as extension.

However, it does not change anything to the behavior, in both directions, when trying to copy and paste text between OSX TexEdit and MacOS AppleWorks. It is exactly the same as I described yesterday, both the behavior in 32-bit mode and the behavior in 64-bit mode.

While trying this with and without the TESyncScrap extension, I found the easiest way to have copy and paste between TextEdit and AppleWorks work in 64-bit mode. Just leave the Clipboard window in MacOS Finder open. With the Clipboard window open, not only switching to the MacOS Finder after copying in AppleWorks works to paste in TextEdit but also, after copying in TextEdit, pasting in AppleWorks works after switching from AppleWorks to the MacOS Finder and back again to AppleWorks.


Ronald.

----------------------------------------
Op 10 juli 2012, om 12:26, schreef Ronald P. Regensburg:


Ah! Apparently MacBinary. I have seen thousands of MacBinary files in past decades, always with a .bin file extension. This is the first time I see a .mbin extension.

I will try the extension to see if it solves the issues with AppleWorks and clipboard synchronizing.

Ronald.

----------------------------------------
Op 10 juli 2012, om 11:55, schreef Ronald P. Regensburg:

What is a .mbin file? How do I use this?

Ronald.

----------------------------------------
Op 10 juli 2012, om 02:27, schreef Josh Juran:

> On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:
> 
>> Have you tried using the Mac OS extension that Jean-Pierre posted  
>> to this list some time ago?
>> 
>> I think it's meant to solve exactly the problem of needing to  
>> change app focus before clipboard changes "stick".
>> 
>> I'd be curious to know whether it improves things for you.
> 
> Are you referring to TESyncScrap?
> 
> "Typical non-Carbon apps synchronize the system clipboard with the  
> TextEdit clipboard when you switch layers, i.e. bring another app  
> forward. If in between copying text and switching layers the app  
> crashes, or quits without synchronizing, or you're running it in an  
> emulator and you try to paste in another app in the host OS, you'll  
> get stale data. A similar issue pertains to pasting into the  
> emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy  
> and just before Paste (like Carbon apps do), avoiding these issues."
> 
> http://www.jjuran.org/hacks/TESyncScrap.mbin
> 
> Josh

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

Ah! Apparently MacBinary. I have seen thousands of MacBinary files in past decades, always with a .bin file extension. This is the first time I see a .mbin extension.

I will try the extension to see if it solves the issues with AppleWorks and clipboard synchronizing.

Ronald.

----------------------------------------
Op 10 juli 2012, om 11:55, schreef Ronald P. Regensburg:

What is a .mbin file? How do I use this?

Ronald.

----------------------------------------
Op 10 juli 2012, om 02:27, schreef Josh Juran:

> On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:
> 
>> Have you tried using the Mac OS extension that Jean-Pierre posted  
>> to this list some time ago?
>> 
>> I think it's meant to solve exactly the problem of needing to  
>> change app focus before clipboard changes "stick".
>> 
>> I'd be curious to know whether it improves things for you.
> 
> Are you referring to TESyncScrap?
> 
> "Typical non-Carbon apps synchronize the system clipboard with the  
> TextEdit clipboard when you switch layers, i.e. bring another app  
> forward. If in between copying text and switching layers the app  
> crashes, or quits without synchronizing, or you're running it in an  
> emulator and you try to paste in another app in the host OS, you'll  
> get stale data. A similar issue pertains to pasting into the  
> emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy  
> and just before Paste (like Carbon apps do), avoiding these issues."
> 
> http://www.jjuran.org/hacks/TESyncScrap.mbin
> 
> Josh
> 

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

What is a .mbin file? How do I use this?

Ronald.

----------------------------------------
Op 10 juli 2012, om 02:27, schreef Josh Juran:

> On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:
> 
>> Have you tried using the Mac OS extension that Jean-Pierre posted  
>> to this list some time ago?
>> 
>> I think it's meant to solve exactly the problem of needing to  
>> change app focus before clipboard changes "stick".
>> 
>> I'd be curious to know whether it improves things for you.
> 
> Are you referring to TESyncScrap?
> 
> "Typical non-Carbon apps synchronize the system clipboard with the  
> TextEdit clipboard when you switch layers, i.e. bring another app  
> forward. If in between copying text and switching layers the app  
> crashes, or quits without synchronizing, or you're running it in an  
> emulator and you try to paste in another app in the host OS, you'll  
> get stale data. A similar issue pertains to pasting into the  
> emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy  
> and just before Paste (like Carbon apps do), avoiding these issues."
> 
> http://www.jjuran.org/hacks/TESyncScrap.mbin
> 
> Josh
> 

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Alexei S. <ale...@gm...>]

On Mon, Jul 9, 2012 at 8:27 PM, Josh Juran <jj...@gm...> wrote:

> On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:
>
> > Have you tried using the Mac OS extension that Jean-Pierre posted
> > to this list some time ago?
> >
> > I think it's meant to solve exactly the problem of needing to
> > change app focus before clipboard changes "stick".
> >
> > I'd be curious to know whether it improves things for you.
>
> Are you referring to TESyncScrap?
>

Woops, my apologies for mis-crediting your work (yes I was referring to it).

-Alexei


>
> "Typical non-Carbon apps synchronize the system clipboard with the
> TextEdit clipboard when you switch layers, i.e. bring another app
> forward. If in between copying text and switching layers the app
> crashes, or quits without synchronizing, or you're running it in an
> emulator and you try to paste in another app in the host OS, you'll
> get stale data. A similar issue pertains to pasting into the
> emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy
> and just before Paste (like Carbon apps do), avoiding these issues."
>
> http://www.jjuran.org/hacks/TESyncScrap.mbin
>
> Josh
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Josh J. <jj...@gm...>]

On Jul 9, 2012, at 4:46 PM, Alexei Svitkine wrote:

> Have you tried using the Mac OS extension that Jean-Pierre posted  
> to this list some time ago?
>
> I think it's meant to solve exactly the problem of needing to  
> change app focus before clipboard changes "stick".
>
> I'd be curious to know whether it improves things for you.

Are you referring to TESyncScrap?

"Typical non-Carbon apps synchronize the system clipboard with the  
TextEdit clipboard when you switch layers, i.e. bring another app  
forward. If in between copying text and switching layers the app  
crashes, or quits without synchronizing, or you're running it in an  
emulator and you try to paste in another app in the host OS, you'll  
get stale data. A similar issue pertains to pasting into the  
emulator. TESyncScrap synchronizes the clipboard just after Cut/Copy  
and just before Paste (like Carbon apps do), avoiding these issues."

http://www.jjuran.org/hacks/TESyncScrap.mbin

Josh

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Alexei S. <ale...@gm...>]

Have you tried using the Mac OS extension that Jean-Pierre posted to this
list some time ago?

I think it's meant to solve exactly the problem of needing to change app
focus before clipboard changes "stick".

I'd be curious to know whether it improves things for you.

-Alexei

On Mon, Jul 9, 2012 at 5:03 PM, Ronald P. Regensburg <ron...@xs...>wrote:

>
> I hope you are not getting annoyed by my investigations into the clipboard
> and AppleWorks (ClarisWorks) issue. I will stop after this message.
>
> This is what I found with today's (July 9th) SheepShaver 2.4 build.
>
> Definitions:
> AW = AppleWorks in OS9
> ST = SimpleText in OS9
> TE = TextEdit in OSX
>
> In 32-bit mode it works as it did in older builds:
>
> Works (plain text):
> - Copy in TE and paste in ST
> - Copy in ST and paste in TE
>
> Does not work:
> - Copy in AW and paste in TE
>
> Works (plain text)
> - Copy in TE and paste in AW
> - Copy in AW -> paste in ST -> copy in ST -> paste in TE
>
>
> In 64-bit mode:
>
> Works (formatted text):
> - Copy in TE and paste in ST
> - Copy in ST and paste in TE
>
> Does not work:
> - Copy in TE and paste in AW
> - Copy in AW and paste in TE
>
> Works only once (formatted text):
> - Copy in TE -> launch AW for the first time after SheepShaver startup ->
> paste in AW
>
> Works (formatted text):
> - Copy in TE -> choose "Show clipboard" in OS9 Finder Edit menu (you may
> or may not leave the clipboard window open) -> paste in AW
> (Show clipboard can be replaced by paste in ST or paste in ResEdit.)
> - Copy in AW -> switch to the OS9 Finder (e.g., click on the OS9 desktop)
> -> paste in TE
> (Switch to the OS9 Finder can be replaced by switch to ST that has at
> least one window open.)
>
> AppleWorks seems to be special in the way it relates to the clipboard.
>
>
> Ronald.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

I hope you are not getting annoyed by my investigations into the clipboard and AppleWorks (ClarisWorks) issue. I will stop after this message.

This is what I found with today's (July 9th) SheepShaver 2.4 build.

Definitions:
AW = AppleWorks in OS9
ST = SimpleText in OS9
TE = TextEdit in OSX

In 32-bit mode it works as it did in older builds:

Works (plain text):
- Copy in TE and paste in ST
- Copy in ST and paste in TE

Does not work:
- Copy in AW and paste in TE

Works (plain text)
- Copy in TE and paste in AW
- Copy in AW -> paste in ST -> copy in ST -> paste in TE


In 64-bit mode:

Works (formatted text):
- Copy in TE and paste in ST
- Copy in ST and paste in TE

Does not work:
- Copy in TE and paste in AW
- Copy in AW and paste in TE

Works only once (formatted text):
- Copy in TE -> launch AW for the first time after SheepShaver startup -> paste in AW

Works (formatted text):
- Copy in TE -> choose "Show clipboard" in OS9 Finder Edit menu (you may or may not leave the clipboard window open) -> paste in AW
(Show clipboard can be replaced by paste in ST or paste in ResEdit.)
- Copy in AW -> switch to the OS9 Finder (e.g., click on the OS9 desktop) -> paste in TE
(Switch to the OS9 Finder can be replaced by switch to ST that has at least one window open.)

AppleWorks seems to be special in the way it relates to the clipboard.


Ronald.

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

The issue in 64-bit mode with copying images from OS X to Mac OS is indeed solved.

Thanks.

Ronald.

----------------------------------------
Op 7 juli 2012, om 11:27, schreef Charles Srstka:

In addition, I've added a rudimentary PICT converter. It's rudimentary at the moment, only going in one direction, converting to PICT and not from PICT, and currently it always rasterizes the source image and creates a PICT containing bitmap data. However, it's a start, and it should solve Ronald's issue with copying images from OS X to Mac OS.

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

For completeness: The scripts work to enable copy/paste from AppleWorks in MacOS to OSX and vice versa in SheepShaver 64-bit. Activating a different application is apparently needed for sharing data between the MacOS clipboard and what I imagined as being a separate AppleWorks clipboard.

However, when SheepShaver runs in 32-bit mode, it works as before: Copy/paste directly from OSX to AppleWorks is possible (plain text only). And copy/paste from AppleWorks to OSX is not possible, pasting and again copying in SimpleText is needed as intemediary step (also plain text only).

There is something with resources that I cannot figure out. Is it possible that AppleWorks uses for copy/paste internally only "styl" resources and no "TEXT" resources?

Ronald.


----------------------------------------
Op 8 juli 2012, om 14:28, schreef Ronald P. Regensburg:

Still not knowing what exactly is the issue with AppleWorks (and presumably ClarisWorks), I made two simple AppleScripts in MacOS9 that work for copying and pasting between AW in MacOS9 and applications in OSX. Both scripts work 100% in all situations I tried. The fact that these scripts work may be an indication of where the problem arises.

For copying a selection from MacOS9 AW with the intention to paste in OSX:

tell application "AppleWorks 6"
	activate
	copy to clipboard
end tell
tell application "SimpleText"
	activate
end tell
tell application "AppleWorks 6"
	activate
end tell

(The last activation of AW is not needed, but it brings back the application you are working in.)


For pasting in MacOS9 AW what was copied in OSX:

tell application "SimpleText"
	activate
end tell
tell application "AppleWorks 6"
	activate
	paste
end tell


Ronald.

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

Still not knowing what exactly is the issue with AppleWorks (and presumably ClarisWorks), I made two simple AppleScripts in MacOS9 that work for copying and pasting between AW in MacOS9 and applications in OSX. Both scripts work 100% in all situations I tried. The fact that these scripts work may be an indication of where the problem arises.

For copying a selection from MacOS9 AW with the intention to paste in OSX:

tell application "AppleWorks 6"
	activate
	copy to clipboard
end tell
tell application "SimpleText"
	activate
end tell
tell application "AppleWorks 6"
	activate
end tell

(The last activation of AW is not needed, but it brings back the application you are working in.)


For pasting in MacOS9 AW what was copied in OSX:

tell application "SimpleText"
	activate
end tell
tell application "AppleWorks 6"
	activate
	paste
end tell


Ronald.

----------------------------------------
Op 8 juli 2012, om 12:46, schreef Ronald P. Regensburg:


----------------------------------------
Op 8 juli 2012, om 11:59, schreef Ronald P. Regensburg:

----------------------------------------
Op 8 juli 2012, om 10:39, schreef Ronald P. Regensburg:

>> And, yes, I can directly paste in AW once, but only when I copy in OSX while SheepShaver is not yet running. This sequence works also:
>> 
>> Copy text in OSX -> launch SheepShaver -> launch AW in OS9 -> paste in AW
> 
> SheepShaver does not need to be launched after copying. This sequence also works:
> 
> Copy text in OSX -> launch AW in OS9 -> paste in AW

More:

This does not work:

Copy text in MacOS AW -> paste in OSX TextEdit

But this works:

Copy text in MacOS AW -> quit AW -> paste in OSX TextEdit

And this works:

Copy text in MacOS AW -> show the copied text on the MacOS clipboard (MacOS Finder Edit menu) -> paste in OSX TextEdit

So:

> Or maybe CW/AW has its own private clipboard and are data shared between that private clipboard and the general MacOS clipboard when the general clipboard is used for either copying or pasting

Or is accessed in another way ("Show clipboard")

> and when CW/AW is launched?

And when CW/AW is quit?

> That would work fine as long as copying and pasting would only be between applications inside MacOS, but between applications in the OSX host and CW/AW in the MacOS guest it would work only after pasting in a different application in MacOS and it would work without that only once when CW/AW is launched after text was copied in OSX. Exactly the behavior I see.


Ronald.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
basilisk-devel mailing list
bas...@li...
https://lists.sourceforge.net/lists/listinfo/basilisk-devel

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

----------------------------------------
Op 8 juli 2012, om 11:59, schreef Ronald P. Regensburg:

----------------------------------------
Op 8 juli 2012, om 10:39, schreef Ronald P. Regensburg:

>> And, yes, I can directly paste in AW once, but only when I copy in OSX while SheepShaver is not yet running. This sequence works also:
>> 
>> Copy text in OSX -> launch SheepShaver -> launch AW in OS9 -> paste in AW
> 
> SheepShaver does not need to be launched after copying. This sequence also works:
> 
> Copy text in OSX -> launch AW in OS9 -> paste in AW

More:

This does not work:

Copy text in MacOS AW -> paste in OSX TextEdit

But this works:

Copy text in MacOS AW -> quit AW -> paste in OSX TextEdit

And this works:

Copy text in MacOS AW -> show the copied text on the MacOS clipboard (MacOS Finder Edit menu) -> paste in OSX TextEdit

So:

> Or maybe CW/AW has its own private clipboard and are data shared between that private clipboard and the general MacOS clipboard when the general clipboard is used for either copying or pasting

Or is accessed in another way ("Show clipboard")

> and when CW/AW is launched?

And when CW/AW is quit?

> That would work fine as long as copying and pasting would only be between applications inside MacOS, but between applications in the OSX host and CW/AW in the MacOS guest it would work only after pasting in a different application in MacOS and it would work without that only once when CW/AW is launched after text was copied in OSX. Exactly the behavior I see.


Ronald.

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Ronald P. R. <ron...@xs...>]

----------------------------------------
Op 8 juli 2012, om 10:39, schreef Ronald P. Regensburg:

> And, yes, I can directly paste in AW once, but only when I copy in OSX while SheepShaver is not yet running. This sequence works also:
> 
> Copy text in OSX -> launch SheepShaver -> launch AW in OS9 -> paste in AW

SheepShaver does not need to be launched after copying. This sequence also works:

Copy text in OSX -> launch AW in OS9 -> paste in AW


> Could it be that CW/AW uses its own format on the clipboard and that some kind of conversion is going on on the MacOS clipboard? Could it be related to the fact that CW/AW had both Mac and Windows versions and used a cross-platform format for its documents?

Or maybe CW/AW has its own private clipboard and are data shared between that private clipboard and the general MacOS clipboard when the general clipboard is used for either copying or pasting and when CW/AW is launched? That would work fine as long as copying and pasting would only be between applications inside MacOS, but between applications in the OSX host and CW/AW in the MacOS guest it would work only after pasting in a different application in MacOS and it would work without that only once when CW/AW is launched after text was copied in OSX. Exactly the behavior I see.

Ronald.

Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk / SheepShaver

[Lew Irwin/S. B. <st...@us...>]

Yes, I generally copy from the Chrome browser.

I have been using version 2.3 of SheepShaver. I do seem to recall that two
or three years ago I tried a newer version, was unable to copy from OSX and
paste in OS9 and decided to switch back to the older version. I've only
tried the latest version (it doesn't seem to have a number) for a couple of
days and very lightly at that but pasting in ClarisWorks seems to work OK.
As I indicated, previously copy and paste within ClarisWorks in OS9 failed
if I had SpellCatcher active. The latest version of SheepShaver allows me
to run SpellCatcher, an improvement that comes as some relief because that
program includes the GhostWriter back-up, a great protection against a
crash.

On Sun, Jul 8, 2012 at 1:39 AM, Ronald P. Regensburg <ron...@xs...>wrote:

> With "browser" you mean a web-browser? I never tried copying from a
> web-browser in OSX to paste in anything in OS9 before. I now tried in my
> February 11 2012 build and in yesterdays build to copy in OSX Safari and
> paste in AppleWorks OS9. It works here exactly as I described for copying
> in OSX TextEdit. Pasting directly in AW does not work, but after pasting
> first in SimpleText (without again copying in SimpleText) I can paste in AW.
>
> And, yes, I can directly paste in AW once, but only when I copy in OSX
> while SheepShaver is not yet running. This sequence works also:
>
> Copy text in OSX -> launch SheepShaver -> launch AW in OS9 -> paste in AW
>
> As I wrote before, I have no time now to check these things more
> thoroughly. Maybe Charles Srstka has an idea of what is going on on the
> MacOS clipboard. Could it be that CW/AW uses its own format on the
> clipboard and that some kind of conversion is going on on the MacOS
> clipboard? Could it be related to the fact that CW/AW had both Mac and
> Windows versions and used a cross-platform format for its documents?
>
> Ronald.
>
> ----------------------------------------
> Op 8 juli 2012, om 04:08, schreef Lew Irwin/Studio Briefing:
>
> I have rarely had a problem copying from the browser -- any browser -- in
> OSX and pasting to ClarisWorks in OS9. It won't work in the opposite
> direction, however. I have to paste from ClarisWorks to SimpleText and then
> paste in the OSX browser to WordPress.
>
> On Sat, Jul 7, 2012 at 6:26 PM, Ronald P. Regensburg <ron...@xs...>
> wrote:
> I use AppleWorks 6 in SheepShaver, which is in fact a later version of
> ClarisWorks. I have never been able to copy/paste consistently from
> AppleWorks in MacOS to OSX or from OSX to AppleWorks in MacOS. Occasionally
> it works. It seems to work if first is pasted (even without copying again)
> in SimpleText.
>
> Does not work:
> Copy in OSX TextEdit -> Paste in MacOS AW
> Copy in MacOS AW -> Paste in OSX TextEdit
>
> Works:
> Copy in OSX TextEdit -> Paste in MacOS SimpleText -> Paste in MacOS AW
> Copy in MacOS AW -> Paste in MacOS SimpleText -> Paste in OSX TextEdit
>
> Indeed, without again copying in SimpleText! Very strange. It does not
> need to be SimpleText. Pasting the resources in ResEdit also makes it work.
> But pasting in AW itself does not help.
>
> I would like to test more thoroughly the current state of SheepShaver (and
> BasiliskII) after the many changes in the past days, but I do not have the
> time right now. Maybe later this week.
>
> Ronald.
>
>
> ----------------------------------------
> Op 8 juli 2012, om 00:32, schreef Lew Irwin/Studio Briefing:
>
> Same issue. Still can only paste once from ClarisWorks to OSX. The first
> copied text remains in memory and is not replaced when I attempt to copy
> and paste different text.
>
> On Sat, Jul 7, 2012 at 2:10 PM, howard spoelstra <
> how...@ho...> wrote:
>
> Hi,
>
> You can pick up the latest version (as of July 7th) over at the
> emaculation forum:
> http://www.emaculation.com/forum/viewtopic.php?f=20&t=7656&p=43345#p43345
>
> Best,
> Howard
> Date: Sat, 7 Jul 2012 10:55:05 -0700
> From: st...@us...
> To: bas...@li...
> Subject: Re: [B2-devel] [PATCH] More clipboard-related fixes for Basilisk
> /     SheepShaver
>
>
> I'm a non-techie who uses Sheepshaver daily. I just tried out the 7/1/12
> version. While I can now copy and paste out of Tex-Edit (I could only paste
> into it from OSX previously) I can't do so with ClarisWorks, my primary OS9
> word processor. Previously I could copy from OSX and paste in ClarisWorks
> but not vice versa. (I had to use Simple Text as an intermediary.) Now I
> can do neither.  I don't need to copy styled text in either direction.
>
> Also, in neither version of SheepShaver can I copy and/or paste within
> ClarisWorks if SpellCatcher is active.
>
> On Sat, Jul 7, 2012 at 8:41 AM, Alexei Svitkine <ale...@gm...>
> wrote:
> Thanks!
>
> Landed:
> https://github.com/cebix/macemu/commit/6f2635ee3128cab12335009dd8a722d6df9fb726
>
> On Sat, Jul 7, 2012 at 5:27 AM, Charles Srstka <
> bas...@ch...> wrote:
> This patch fixes one lingering problem with the 64-bit clipboard code; the
> way it was designed, the Mac clipboard was being cleared every time a
> single item was being requested by GetScrap, causing clipboards with
> multiple items to be unceremoniously whittled down to one. On the other
> hand, a similar issue was causing some items to get duplicated on the host
> pasteboard. This patch fixes the issue by making conversion between the
> host pasteboard and the Mac clipboard a singular operation; when the
> pasteboard data changes on the host side, it is all converted and sent to
> the Mac pasteboard at once, and similarly, all Mac clipboard data is sent
> to the host pasteboard in one operation. Also, data from the host side is
> copied to the Mac clipboard only if it has changed since the last check,
> which should improve performance as conversions will not be done over and
> over every time the Mac side checks whether the scrap has changed.
>
> In addition, I've added a rudimentary PICT converter. It's rudimentary at
> the moment, only going in one direction, converting to PICT and not from
> PICT, and currently it always rasterizes the source image and creates a
> PICT containing bitmap data. However, it's a start, and it should solve
> Ronald's issue with copying images from OS X to Mac OS. In the future, more
> could possibly be added. I've put the new PICT code in the main source
> directory instead of in the MacOSX subdirectory, so that it can be used by
> other platforms if needed.
>
> I would like to leave the license on the new PICT code as "Public Domain"
> if that is okay.
>
> Thanks,
> Charles
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
>
> --
> Lew Irwin
> STUDIO BRIEFING
> www.studiobriefing.net
> st...@us...
> (818) 865-0044
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference Exclusive live event will cover all the
> ways today's security and threat landscape has changed and how IT managers
> can respond. Discussions will include endpoint security, mobile security
> and the latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________ basilisk-devel mailing
> list bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
>
> --
> Lew Irwin
> STUDIO BRIEFING
> www.studiobriefing.net
> st...@us...
> (818) 865-0044
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
> --
> Lew Irwin
> STUDIO BRIEFING
> www.studiobriefing.net
> st...@us...
> (818) 865-0044
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>



-- 
Lew Irwin
STUDIO BRIEFING
www.studiobriefing.net
st...@us...
(818) 865-0044