Menu
▾
▴
basilisk-devel — Basilisk II development-related discussion
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(13) |
Sep
(42) |
Oct
(17) |
Nov
(7) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(14) |
Feb
(8) |
Mar
(13) |
Apr
(10) |
May
(28) |
Jun
(28) |
Jul
(23) |
Aug
(7) |
Sep
(2) |
Oct
(24) |
Nov
(9) |
Dec
(2) |
| 2002 |
Jan
(58) |
Feb
(15) |
Mar
(57) |
Apr
(26) |
May
(7) |
Jun
|
Jul
(10) |
Aug
|
Sep
(19) |
Oct
(9) |
Nov
(6) |
Dec
(4) |
| 2003 |
Jan
(4) |
Feb
(1) |
Mar
(3) |
Apr
(5) |
May
(14) |
Jun
(3) |
Jul
(7) |
Aug
(4) |
Sep
(7) |
Oct
(4) |
Nov
(11) |
Dec
(3) |
| 2004 |
Jan
(32) |
Feb
(21) |
Mar
(3) |
Apr
(11) |
May
(33) |
Jun
(42) |
Jul
(46) |
Aug
(2) |
Sep
(3) |
Oct
|
Nov
(42) |
Dec
(23) |
| 2005 |
Jan
(5) |
Feb
(2) |
Mar
(12) |
Apr
(26) |
May
(8) |
Jun
(18) |
Jul
(21) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(10) |
Dec
(1) |
| 2006 |
Jan
(17) |
Feb
(17) |
Mar
(3) |
Apr
(2) |
May
(2) |
Jun
(7) |
Jul
(6) |
Aug
(4) |
Sep
|
Oct
(3) |
Nov
(7) |
Dec
(4) |
| 2007 |
Jan
(6) |
Feb
(4) |
Mar
|
Apr
(3) |
May
(7) |
Jun
(17) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(2) |
Dec
(5) |
| 2008 |
Jan
(14) |
Feb
(2) |
Mar
(2) |
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2009 |
Jan
(2) |
Feb
(22) |
Mar
(3) |
Apr
|
May
(7) |
Jun
|
Jul
|
Aug
(15) |
Sep
|
Oct
(32) |
Nov
(9) |
Dec
|
| 2010 |
Jan
(18) |
Feb
(2) |
Mar
(14) |
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
(7) |
Sep
(6) |
Oct
(35) |
Nov
(4) |
Dec
|
| 2011 |
Jan
(4) |
Feb
|
Mar
(9) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(9) |
Oct
|
Nov
|
Dec
(4) |
| 2012 |
Jan
(4) |
Feb
|
Mar
(8) |
Apr
(9) |
May
|
Jun
(176) |
Jul
(86) |
Aug
(20) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(4) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2016 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
(13) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
|
From: Ronald P. R. <ron...@xs...> - 2012-07-08 08:39:56
|
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 |
|
From: Lew Irwin/S. B. <st...@us...> - 2012-07-08 02:15:51
|
Don't know whether this will be of any help, but on the few occasions when I have been unable to paste in ClarisWorks from OSX I have also been unable to connect to the Internet with Outlook Express in OS9. I have to restart SheepShaver -- and all is right. On Sat, Jul 7, 2012 at 7:08 PM, Lew Irwin/Studio Briefing <st...@us...>wrote: > 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<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 > > > -- Lew Irwin STUDIO BRIEFING www.studiobriefing.net st...@us... (818) 865-0044 |
|
From: Lew Irwin/S. B. <st...@us...> - 2012-07-08 02:08:44
|
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 |
|
From: Ronald P. R. <ron...@xs...> - 2012-07-08 01:26:23
|
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 |
|
From: Lew Irwin/S. B. <st...@us...> - 2012-07-07 22:32:38
|
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 |
|
From: howard s. <how...@ho...> - 2012-07-07 21:10:28
|
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...@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 |
|
From: Alexei S. <ale...@gm...> - 2012-07-07 18:14:28
|
Hey Christian, Do you mind updating http://sheepshaver.cebix.net/ to point at the new GIT repo instead of the old CVS one? -Alexei On Mon, Jun 18, 2012 at 7:06 PM, Alexei Svitkine <ale...@gm...>wrote: > Seems to work, thanks! > > > On Mon, Jun 18, 2012 at 2:39 PM, Christian Bauer <cb...@ce...> wrote: > >> Hi! >> >> On 06/16/2012 07:38 PM, Alexei Svitkine wrote: >> > Can you create a new GitHub repo containing both SS and BasiliskII >> > sources from the CVS TOT and add me as a collaborator? >> >> Let me know whether this works for you: >> https://github.com/cebix/macemu >> >> Bye, >> Christian >> >> -- >> / Physics is an algorithm >> \/ www.cebix.net >> >> >> ------------------------------------------------------------------------------ >> 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 >> > > |
|
From: Charles S. <bas...@ch...> - 2012-07-07 17:59:49
|
On Jul 7, 2012, at 12:55 PM, Lew Irwin/Studio Briefing wrote: > 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. Could you please compiling from the current source and seeing if you still have this problem? I’ve sent a lot of patches to the clipboard support in the last week, and your issue might be one of the many that have already been fixed. Charles |
|
From: Lew Irwin/S. B. <st...@us...> - 2012-07-07 17:55:13
|
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 |
|
From: Alexei S. <ale...@gm...> - 2012-07-07 15:42:10
|
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 > > |
|
From: Charles S. <bas...@ch...> - 2012-07-07 09:27:12
|
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 |
|
From: Dave V. <va...@us...> - 2012-07-06 11:19:14
|
It's also possible to build a BasiliskII GUI against the OS X port of GTK+, allowing it to run without X11. It still looks kinda like the X11 version, but it uses Quartz windowing. I put some instructions here, though they may be a bit out of date: https://github.com/vasi/b2gui -Dave On Thu, Jul 5, 2012 at 11:45 PM, Robert Munafo <mr...@gm...> wrote: > Hey great, thank you! > > X11 is fine for me, I launch the emulator from a script anyway, so I > just have the script check if X11 is running, launch it and set the > DISPLAY environment variable appropriately, etc. > > On 7/5/12, Alexei Svitkine <ale...@gm...> wrote: >> --enable-macosx-gui without any other options (from latest git TOT). Note: >> This is BasiliskII only, not SheepShaver. >> >> It uses CoreGraphics and Cocoa to render the screen. >> >> On Thu, Jul 5, 2012 at 9:05 PM, Robert Munafo <mr...@gm...> wrote: >>> [I used no --enable-blargs and got an X11 version] >> >> If you build it that way, then yes it uses X11 and not SDL, but it does >> require X11 to be running. But this is a different config that >> --enable-macosx-gui. > > -- > Robert Munafo -- mrob.com > Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 - > mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com > > ------------------------------------------------------------------------------ > 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 |
|
From: Ronald P. R. <ron...@xs...> - 2012-07-06 07:08:28
|
---------------------------------------- Op 6 juli 2012, om 03:05, schreef Robert Munafo: > Could you provide details on how you built it without SDL? > In Snow Leopard, with XCode 3.2.6 installed: cd BasiliskII/src/Unix export CC=/usr/bin/gcc-4.0 export CXX=/usr/bin/g++-4.0 ./autogen.sh --enable-macosx-gui make make BasiliskII_app Ronald. |
|
From: Robert M. <mr...@gm...> - 2012-07-06 03:45:20
|
Hey great, thank you! X11 is fine for me, I launch the emulator from a script anyway, so I just have the script check if X11 is running, launch it and set the DISPLAY environment variable appropriately, etc. On 7/5/12, Alexei Svitkine <ale...@gm...> wrote: > --enable-macosx-gui without any other options (from latest git TOT). Note: > This is BasiliskII only, not SheepShaver. > > It uses CoreGraphics and Cocoa to render the screen. > > On Thu, Jul 5, 2012 at 9:05 PM, Robert Munafo <mr...@gm...> wrote: >> [I used no --enable-blargs and got an X11 version] > > If you build it that way, then yes it uses X11 and not SDL, but it does > require X11 to be running. But this is a different config that > --enable-macosx-gui. -- Robert Munafo -- mrob.com Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 - mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com |
|
From: Alexei S. <ale...@gm...> - 2012-07-06 02:34:01
|
Thanks. I went ahead and landed your patch here: https://github.com/cebix/macemu/commit/2b51d635a7c60d6f9a2817e55480a172088324b8 -Alexei On Thu, Jul 5, 2012 at 12:18 PM, Charles Srstka < bas...@ch...> wrote: > On Jul 5, 2012, at 8:06 AM, Alexei Svitkine wrote: > > Could you point me at a reference that explains why @autoreleasepool would > be more efficient than just managing one yourself? > > > Doesn’t say *why*, but Apple does claim that @autoreleasepool is about six > times (!) faster: > > > http://developer.apple.com/library/mac/#releasenotes/ObjectiveC/RN-TransitioningToARC/Introduction/Introduction.html%23//apple_ref/doc/uid/TP40011226-CH1-SW16 > > Presumably this would be done by avoiding the creation of actual objects > (i.e. the NSAutoreleasePool instance and whatever internal storage it > uses), and by using optimized versions of the retain and release methods. > Maybe other dark magics as well; one would have to pore through the clang > sources to find out exactly what it’s doing. > > Also, shouldn't the ifdef to use it be testing for the version of clang > that added it? Some Googling reveals that it's not supported by older clang > (e.g. the one shipped with Xcode 3.2). > > > Well, clang didn’t become the default compiler for Xcode until Xcode 4, as > the early versions were not fully baked, so I have my doubts that anyone > would still be using those old versions of clang. Nevertheless, you are > correct; it would be best to check. unfortunately, clang doesn’t seem to > have a __has_feature(()) macro for @autoreleasepool, which is the preferred > way to check for these things, and the clang docs claim you’re not supposed > to check the version number, since different vendors are apparently allowed > to have different version numbering schemes ( > http://clang.llvm.org/docs/LanguageExtensions.html#builtinmacros). OTOH, > since these files are Apple-specific, it’s probably safe *most* of the time > to assume they’ll be using Apple’s version of clang and thus their > numbering scheme. Not 100% though. > > I guess we could add a ./configure check, or we could just put this off > until we actually have LLVM/clang support working. > > 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 > > |
|
From: Alexei S. <ale...@gm...> - 2012-07-06 02:20:50
|
--enable-macosx-gui without any other options (from latest git TOT). Note: This is BasiliskII only, not SheepShaver. It uses CoreGraphics and Cocoa to render the screen. On Thu, Jul 5, 2012 at 9:05 PM, Robert Munafo <mr...@gm...> wrote: > Could you provide details on how you built it without SDL? > > I think I'm doing right, by leaving out the --enable-sdl-video and > --enable-sdl-audio options (and I think it's working because the final > link command doesn't include the ".../SDL-1.2.15/lib/..." object > files), but the result will only run if I have the X11 server running. > > But I guess that's right, it has to draw to the screen somehow, so it > uses X11 instead of SDL, right? > If you build it that way, then yes it uses X11 and not SDL, but it does require X11 to be running. But this is a different config that --enable-macosx-gui. -Alexei > > - Robert > > On 7/5/12, Ronald P. Regensburg <ron...@xs...> wrote: > > After seeing the related commits, I built a 32-bit Intel GUI version of > > BasiliskII MacOSX. Never tried it before because I thought it could not > be > > done anymore in current OSX versions. > > > > It has several problems, especially with some of the GUI buttons, but it > > runs remarkably well, even better than Nigel Pearson's 2006 UB build > (that > > crashes when you try to emulate a 68040). > > > > It seems not to need SDL. Is that correct? > > > > Ronald. > > -- > Robert Munafo -- mrob.com > Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 - > mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com > > > ------------------------------------------------------------------------------ > 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 > |
|
From: Robert M. <mr...@gm...> - 2012-07-06 01:06:06
|
Could you provide details on how you built it without SDL? I think I'm doing right, by leaving out the --enable-sdl-video and --enable-sdl-audio options (and I think it's working because the final link command doesn't include the ".../SDL-1.2.15/lib/..." object files), but the result will only run if I have the X11 server running. But I guess that's right, it has to draw to the screen somehow, so it uses X11 instead of SDL, right? - Robert On 7/5/12, Ronald P. Regensburg <ron...@xs...> wrote: > After seeing the related commits, I built a 32-bit Intel GUI version of > BasiliskII MacOSX. Never tried it before because I thought it could not be > done anymore in current OSX versions. > > It has several problems, especially with some of the GUI buttons, but it > runs remarkably well, even better than Nigel Pearson's 2006 UB build (that > crashes when you try to emulate a 68040). > > It seems not to need SDL. Is that correct? > > Ronald. -- Robert Munafo -- mrob.com Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 - mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com |
|
From: Alexei S. <ale...@gm...> - 2012-07-05 23:13:29
|
> > It seems not to need SDL. Is that correct? > Correct. -Alexei |
|
From: Alexei S. <ale...@gm...> - 2012-07-05 23:13:02
|
Thanks for taking the time to file these. -Alexei On Thu, Jul 5, 2012 at 4:06 PM, Ronald P. Regensburg <ron...@xs...>wrote: > I filed the remaining issues with BasiliskII and SheepShaver MacOSX from a > user's point of view at this point in time: > > https://github.com/cebix/macemu/issues > > If these issues would be solved, 64-bit Intel versions could be presented > to average users unreservedly. > > 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 > |
|
From: Ronald P. R. <ron...@xs...> - 2012-07-05 20:23:00
|
After seeing the related commits, I built a 32-bit Intel GUI version of BasiliskII MacOSX. Never tried it before because I thought it could not be done anymore in current OSX versions. It has several problems, especially with some of the GUI buttons, but it runs remarkably well, even better than Nigel Pearson's 2006 UB build (that crashes when you try to emulate a 68040). It seems not to need SDL. Is that correct? Ronald. |
|
From: Ronald P. R. <ron...@xs...> - 2012-07-05 20:06:16
|
I filed the remaining issues with BasiliskII and SheepShaver MacOSX from a user's point of view at this point in time: https://github.com/cebix/macemu/issues If these issues would be solved, 64-bit Intel versions could be presented to average users unreservedly. Ronald. |
|
From: Charles S. <bas...@ch...> - 2012-07-05 16:18:56
|
On Jul 5, 2012, at 8:06 AM, Alexei Svitkine wrote: > Could you point me at a reference that explains why @autoreleasepool would be more efficient than just managing one yourself? Doesn’t say *why*, but Apple does claim that @autoreleasepool is about six times (!) faster: http://developer.apple.com/library/mac/#releasenotes/ObjectiveC/RN-TransitioningToARC/Introduction/Introduction.html%23//apple_ref/doc/uid/TP40011226-CH1-SW16 Presumably this would be done by avoiding the creation of actual objects (i.e. the NSAutoreleasePool instance and whatever internal storage it uses), and by using optimized versions of the retain and release methods. Maybe other dark magics as well; one would have to pore through the clang sources to find out exactly what it’s doing. > Also, shouldn't the ifdef to use it be testing for the version of clang that added it? Some Googling reveals that it's not supported by older clang (e.g. the one shipped with Xcode 3.2). Well, clang didn’t become the default compiler for Xcode until Xcode 4, as the early versions were not fully baked, so I have my doubts that anyone would still be using those old versions of clang. Nevertheless, you are correct; it would be best to check. unfortunately, clang doesn’t seem to have a __has_feature(()) macro for @autoreleasepool, which is the preferred way to check for these things, and the clang docs claim you’re not supposed to check the version number, since different vendors are apparently allowed to have different version numbering schemes (http://clang.llvm.org/docs/LanguageExtensions.html#builtinmacros). OTOH, since these files are Apple-specific, it’s probably safe *most* of the time to assume they’ll be using Apple’s version of clang and thus their numbering scheme. Not 100% though. I guess we could add a ./configure check, or we could just put this off until we actually have LLVM/clang support working. Charles |
|
From: Alexei S. <ale...@gm...> - 2012-07-05 13:07:27
|
Could you point me at a reference that explains why @autoreleasepool would be more efficient than just managing one yourself? Also, shouldn't the ifdef to use it be testing for the version of clang that added it? Some Googling reveals that it's not supported by older clang (e.g. the one shipped with Xcode 3.2). -Alexei On Thu, Jul 5, 2012 at 4:46 AM, Charles Srstka < bas...@ch...> wrote: > On Jul 5, 2012, at 1:38 AM, Alexei Svitkine wrote: > > On Thu, Jul 5, 2012 at 2:29 AM, Charles Srstka < > bas...@ch...> wrote: > >> On Jul 5, 2012, at 12:39 AM, Alexei Svitkine wrote: >> >> if (floor(NSFoundationVersionNumber) > NSFoundationVersionNumber10_5) >>> ... new API >>> else >>> ... old API >>> >> >> Is your new implementation strictly better than the clip_macosx.cpp one? >> Can you give a brief overview comparing them in terms of what works and >> what doesn't? This will help make it clear whether it makes sense to always >> prefer to use the new API code when running on 10.6 for 32-bit builds. (And >> hence whether it makes sense to consolidate them now like this.) >> >> >> Well, it’s definitely better than the clip_macosx.cpp in that the latter >> doesn’t run on 64-bit systems. I’ve also added a couple of features to it: >> >> 1. copy/paste styled text into and out of the emulator >> >> 2. copy/paste international text using non-Roman scripts into and out of >> the emulator >> >> As for the 10.6+ pasteboard API, that adds two features: >> >> 1. The ability to just say “lemme read/write an NSAttributedString off >> the pasteboard!” and have the OS do the conversion for you to and from >> whatever internal representation it’s using, instead of saying “Gimme some >> data of kUTTypeRTF and I hope that’s what OS X still uses!” >> >> 2. The fact that the API is just more current and is a complete >> replacement for the old one, and although the old API isn’t deprecated yet, >> you know how Apple is (Exhibit A: the fact that the implementation in >> clip_macosx.cpp no longer works). Basically, this is for future-proofing. >> > > Okay, but clip_macosx.cpp would still be able to handle scrap types that > exist both under Classic and Mac OS X transparently (at least, on PPC or if > there is no byteswapping needed), correct? Ones that wouldn't get handled > without explicit support in clip_macosx64.mm. That's the big difference, > still, right? > > > I believe that can be done in the ... old API section; the docs for > NSPasteboard claim that the API marked "10.5 and earlier” are still capable > of taking types that aren’t UTIs, although it warns that this will probably > stop working in some future version of OS X (which is why I feel that we > definitely don’t want code that does that running on modern OS X versions). > > One thing about that, though — as you point out, it’s only a safe thing to > do on PPC — on Intel, it could lead to all sorts of byte-swapping issues. > And forgive me if I’m missing an important use case, but if you’re on > Tiger/PPC, why would you need SheepShaver? Machines in that configuration > have access to the Classic environment, which in my experience is generally > much better at running Classic Mac OS applications than SheepShaver is. > > I think there will also be problems compiling this combined file on 10.4, > for example, since it wouldn't have headers for the new APIs. That can be > worked around with additional ifdefs, but that gets hairy fast. > > > With Objective-C, it can be done much more easily than that. The first > thing to note is that Objective-C is a completely dynamic language, and all > the “static typing” you get at the source code level is purely advisory; > trying to send a message that isn’t defined in any header to an object only > generates a warning at compile time, although if execution actually reaches > that nonexistent call at runtime, it’ll throw an exception. So how much > work this would be depends a lot on whether we care about warnings that > only show up when compiling on ancient systems. There are a few exceptions, > of course, one being that if we try to allocate a class that doesn’t exist > in the 10.4 version of the frameworks, it won’t link. There are ways around > that too, though, like for instance replacing this: > > SomeObjectThatsNotInTiger *myObject = [[SomeObjectThatsNotInTiger alloc] > init]; > > with this: > > SomeObjectThatsNotInTiger *myObject = > [[NSClassFromString(@“SomeObjectThatsNotInTiger”) alloc] init]; > > and that’ll work fine, as long as you keep the execution from getting to > this line in Tiger. > > We’d definitely need to have a tester with Tiger and the dev tools to > catch any surprises, though. > > Let's leave merging these off for now, but we can revisit that later. > > > I’m perfectly fine with that, and my original intent was to have this > apply only to 10.6 and up; the only reason I brought it up was because you > seemed to express some disappointment in it not being back-portable to > 10.4, something that is certainly fixable in the future should the need > arise. > > >> Still, if you do think the autorelease pools are really required, I >>> suggest making a C++ scoped object that will alloc an autorelease pool in >>> its ctor and release it in its dtor, which will eliminate the need for >>> draining the pool at all the early return points. >>> >>> >>> Yeah, that could work. >>> >> >> Could you make that change? I think it would be much cleaner than all the >> early-return cleanup in your current patch. >> >> >> Sure thing. I think I’ll put the wrapper object in a header file so that >> it can be used elsewhere if people want to. This’ll be an Objective-C++ >> header file and will only be includable by Objective-C++ code; do you have >> any preference whether to put #ifdef guards around it or just use #import? >> > > My preference would be to still have ifdef guards. Thanks. > > > Here’s a new patch: > > > > 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 > > |
|
From: Charles S. <bas...@ch...> - 2012-07-05 08:46:16
|
On Jul 5, 2012, at 1:38 AM, Alexei Svitkine wrote: > On Thu, Jul 5, 2012 at 2:29 AM, Charles Srstka <bas...@ch...> wrote: > On Jul 5, 2012, at 12:39 AM, Alexei Svitkine wrote: > >> if (floor(NSFoundationVersionNumber) > NSFoundationVersionNumber10_5) >> ... new API >> else >> ... old API >> >> Is your new implementation strictly better than the clip_macosx.cpp one? Can you give a brief overview comparing them in terms of what works and what doesn't? This will help make it clear whether it makes sense to always prefer to use the new API code when running on 10.6 for 32-bit builds. (And hence whether it makes sense to consolidate them now like this.) > > Well, it’s definitely better than the clip_macosx.cpp in that the latter doesn’t run on 64-bit systems. I’ve also added a couple of features to it: > > 1. copy/paste styled text into and out of the emulator > > 2. copy/paste international text using non-Roman scripts into and out of the emulator > > As for the 10.6+ pasteboard API, that adds two features: > > 1. The ability to just say “lemme read/write an NSAttributedString off the pasteboard!” and have the OS do the conversion for you to and from whatever internal representation it’s using, instead of saying “Gimme some data of kUTTypeRTF and I hope that’s what OS X still uses!” > > 2. The fact that the API is just more current and is a complete replacement for the old one, and although the old API isn’t deprecated yet, you know how Apple is (Exhibit A: the fact that the implementation in clip_macosx.cpp no longer works). Basically, this is for future-proofing. > > Okay, but clip_macosx.cpp would still be able to handle scrap types that exist both under Classic and Mac OS X transparently (at least, on PPC or if there is no byteswapping needed), correct? Ones that wouldn't get handled without explicit support in clip_macosx64.mm. That's the big difference, still, right? I believe that can be done in the ... old API section; the docs for NSPasteboard claim that the API marked "10.5 and earlier” are still capable of taking types that aren’t UTIs, although it warns that this will probably stop working in some future version of OS X (which is why I feel that we definitely don’t want code that does that running on modern OS X versions). One thing about that, though — as you point out, it’s only a safe thing to do on PPC — on Intel, it could lead to all sorts of byte-swapping issues. And forgive me if I’m missing an important use case, but if you’re on Tiger/PPC, why would you need SheepShaver? Machines in that configuration have access to the Classic environment, which in my experience is generally much better at running Classic Mac OS applications than SheepShaver is. > I think there will also be problems compiling this combined file on 10.4, for example, since it wouldn't have headers for the new APIs. That can be worked around with additional ifdefs, but that gets hairy fast. With Objective-C, it can be done much more easily than that. The first thing to note is that Objective-C is a completely dynamic language, and all the “static typing” you get at the source code level is purely advisory; trying to send a message that isn’t defined in any header to an object only generates a warning at compile time, although if execution actually reaches that nonexistent call at runtime, it’ll throw an exception. So how much work this would be depends a lot on whether we care about warnings that only show up when compiling on ancient systems. There are a few exceptions, of course, one being that if we try to allocate a class that doesn’t exist in the 10.4 version of the frameworks, it won’t link. There are ways around that too, though, like for instance replacing this: SomeObjectThatsNotInTiger *myObject = [[SomeObjectThatsNotInTiger alloc] init]; with this: SomeObjectThatsNotInTiger *myObject = [[NSClassFromString(@“SomeObjectThatsNotInTiger”) alloc] init]; and that’ll work fine, as long as you keep the execution from getting to this line in Tiger. We’d definitely need to have a tester with Tiger and the dev tools to catch any surprises, though. > Let's leave merging these off for now, but we can revisit that later. I’m perfectly fine with that, and my original intent was to have this apply only to 10.6 and up; the only reason I brought it up was because you seemed to express some disappointment in it not being back-portable to 10.4, something that is certainly fixable in the future should the need arise. > >>> Still, if you do think the autorelease pools are really required, I suggest making a C++ scoped object that will alloc an autorelease pool in its ctor and release it in its dtor, which will eliminate the need for draining the pool at all the early return points. >> >> Yeah, that could work. >> >> Could you make that change? I think it would be much cleaner than all the early-return cleanup in your current patch. > > Sure thing. I think I’ll put the wrapper object in a header file so that it can be used elsewhere if people want to. This’ll be an Objective-C++ header file and will only be includable by Objective-C++ code; do you have any preference whether to put #ifdef guards around it or just use #import? > > My preference would be to still have ifdef guards. Thanks. Here’s a new patch: Thanks, Charles |
|
From: Ronald P. R. <ron...@xs...> - 2012-07-05 08:15:09
|
Efforts should be aimed at the future, and that is Intel 64-bit. If improvements can easily be shared with ppc and Intel 32-bit, that is fine. But I do not think feature parity needs to be maintained at all costs. Clipboard integration in MacOSX ppc and intel 32-bit works fine. As far as I am aware, its limitations (like no international language support) are not experienced as bugs. Ronald. ---------------------------------------- Op 5 juli 2012, om 03:35, schreef Alexei Svitkine: Cool! Changing clip_macosx64.mm to require 10.6+ is fine as long as we abandon the idea to eventually having 32-bit use that code too (since we want to keep supporting Tiger and friends). Which I'm okay with, but it does mean that the two implementations may diverge in the features they support. -Alexei |
9 messages has been excluded from this view by a project administrator.
