On Aug 14, 2011, at 9:04 PM, Jerry Krinock wrote:
> One more thing. Remember to leave some kind of back door for yourself. I've
> wanted to punch myself in the nose when I needed to reproduce a bug report
> and my app told me that it wouldn't launch because it was expired.
Really? Surely ther
Does anybody know a programmatic way or a reference resource to get graphical
keyboard map or layout for the currently active keyboard?
Are these documented anywhere anymore?
I would like to provide an on-screen display that is at least a close
approximation of the user's
keyboard.__
On Aug 15, 2011, at 12:08 AM, Charles Srstka wrote:
> Really? Surely there are better uses of your time than trying to track down
> an old bug in an expired beta version that people aren’t even supposed to be
> able to run anymore.
Isn't the purpose of a beta to uncover bugs for you to track do
http://msdn.microsoft.com/en-us/goglobal/bb964651
15-Aug-11 11:07, John Joyce пишет:
Does anybody know a programmatic way or a reference resource to get graphical
keyboard map or layout for the currently active keyboard?
Are these documented anywhere anymore?
I would like to provide an on-scree
Thanks Vyacheslav, but I am a little more interested in Mac keyboards...
On Aug 15, 2011, at 5:35 PM, Vyacheslav Karamov wrote:
> http://msdn.microsoft.com/en-us/goglobal/bb964651
>
> 15-Aug-11 11:07, John Joyce пишет:
>> Does anybody know a programmatic way or a reference resource to get
>> gr
http://scripts.sil.org/cms/scripts/page.php?item_id=inputtoollinks#dc9009da
?
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=Ukelele
15-Aug-11 11:47, John Joyce пишет:
Thanks Vyacheslav, but I am a little more interested in Mac keyboards...
_
On Aug 15, 2011, at 01:47 , John Joyce wrote:
> I am a little more interested in Mac keyboards...
Try starting here:
http://developer.apple.com/library/mac/#technotes/tn2056/_index.html
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Hi Quincy,
Thanks, but I read that one.
10.5 + has no user readable xml layouts.
But also, these xml files do not present any representation of how the keyboard
looks for a given locale.
For example the Japanese Mac KB layout is quite different from the US KB layout.
The left control key is in a
On Aug 15, 2011, at 02:24 , John Joyce wrote:
> Thanks, but I read that one.
> 10.5 + has no user readable xml layouts.
> But also, these xml files do not present any representation of how the
> keyboard looks for a given locale.
> For example the Japanese Mac KB layout is quite different from t
On Aug 15, 2011, at 7:04 PM, Quincey Morris wrote:
> On Aug 15, 2011, at 02:24 , John Joyce wrote:
>
>> Thanks, but I read that one.
>> 10.5 + has no user readable xml layouts.
>> But also, these xml files do not present any representation of how the
>> keyboard looks for a given locale.
>> Fo
John Joyce wrote:
Actually, I'm seeking something more concretely visual. Apple used to
publish the keyboard maps or at least the visual representation. That
is the only thing I am after at the moment. If I cannot get mappings
for each model of Mac (not going too far back though) then it would
I have a Cocoa document app targeting Snow Leopard. It is, in most respects, a
standard document app except that, given an input file, it launches a long,
multi-threaded computation. Consequently, it can handle only one input file at
a time.
For the obvious reasons, I would very much like to
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MenuList/Articles/EnablingMenuItems.html#//apple_ref/doc/uid/2261-BAJBFGED
15-Aug-11 16:08, McLaughlin, Michael P. пишет:
I have a Cocoa document app targeting Snow Leopard. It is, in most respects, a
standard document
I managed to find this solution shortly after sending a request to this list
for help. I show the code below so that future programmers might find this
more easily that I did. This solution has not been tested with Lion. [Note:
This app does not have a File/New command and does not open an un
On Aug 14, 2011, at 6:15 PM, Vince wrote:
> Being a free ADC member I'm unfortunately very sparsely informed about
> Apple's stand regarding IBPlugin's assassination...
That has nothing to do with you being a free ADC member.
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.co
On 15 Aug 2011, at 14:52, McLaughlin, Michael P. wrote:
> I managed to find this solution shortly after sending a request to this list
> for help. I show the code below so that future programmers might find this
> more easily that I did. This solution has not been tested with Lion. [Note:
>
On Aug 15, 2011, at 1:28 AM, Ron Hunsinger wrote:
>
> On Aug 15, 2011, at 12:08 AM, Charles Srstka wrote:
>> Really? Surely there are better uses of your time than trying to track down
>> an old bug in an expired beta version that people aren’t even supposed to be
>> able to run anymore.
>
>
On 2011-08-15, at 3:08 AM, Charles Srstka wrote:
> On Aug 14, 2011, at 9:04 PM, Jerry Krinock wrote:
>
>> One more thing. Remember to leave some kind of back door for yourself.
>> I've wanted to punch myself in the nose when I needed to reproduce a bug
>> report and my app told me that it wo
On Aug 15, 2011, at 8:28 AM, Izak van Langevelde wrote:
> It is my experience that with restricting access to your software you are
> either shooting yourself in the foot, or somebody else. Without, other people
> are shooting themselves in the foot. Personally, I prefer the latter.
Generally,
Sorry for jumping in late...
But that does not even make sense. Usually people who are beta users will
always stay up to date with products, testing the latest and greatest, and any
one who does leave it on, may want to at some point revisit the product, with
out having to install it.
I have
At 8:35 AM -0600 8/15/11, Scott Ribe wrote:
Generally, but closed betas are the one case where expirations
really make sense. It is after all a beta, and you do not want
someone still running the beta a year after the actual release, just
because the person who was your contact for testing forg
On Aug 15, 2011, at 3:28 AM, Ron Hunsinger wrote:
> Isn't the purpose of a beta to uncover bugs for you to track down? If a bug
> is reported the day before the beta expires, do you really want to
> self-impose a one-day time limit to track it down? Even if no one is running
> that beta, all of
But you are forcing your users hand, which is never a good thing. They may need
more time, or lack the resources to continually upgrade.
I tent to give users choice, and as much as possible build the app forward
compatible (get the Model(VC) right from the beginning, it means A LOT). You
can'
On Aug 15, 2011, at 8:55 AM, Shawn Bakhtiar wrote:
> But you are forcing your users hand, which is never a good thing. They may
> need more time, or lack the resources to continually upgrade.
>
> I tent to give users choice, and as much as possible build the app forward
> compatible (get the Mo
On Aug 15, 2011, at 8:53 AM, Charles Srstka wrote:
> If you’re giving your testers betas that are expiring by the time they’re
> sending you reports, you’ve got the expiration date set *way* too early. By
> the time a beta expires, you should have sent them a newer build long ago.
Yes, good poi
On 15/08/2011, at 11:14, cocoa-dev-requ...@lists.apple.com wrote:
> From: John Brownie
> Date: 15 de agosto de 2011 07:19:48 BRT
>
> John Joyce wrote:
>> Actually, I'm seeking something more concretely visual. Apple used to
>> publish the keyboard maps or at least the visual representation. Tha
Dear list,
I guess this is a really simple question to answer, but somehow my googling
doesn't lead me to it.
I have an app and I want to include NSPopovers when the app runs on Lion. I
have some run-time way of finding out if it is Lion or not (see below), but
when the app runs on 10.6 I get
Hi Martin,
NSPopover is not present in the frameworks on 10.6
You will not be able to use it there.
On Aug 16, 2011, at 2:38 AM, Martin Hewitson wrote:
> Dear list,
>
> I guess this is a really simple question to answer, but somehow my googling
> doesn't lead me to it.
>
> I have an app and
On Aug 15, 2011, at 10:38 AM, Martin Hewitson wrote:
> I guess this is a really simple question to answer, but somehow my googling
> doesn't lead me to it.
>
> I have an app and I want to include NSPopovers when the app runs on Lion. I
> have some run-time way of finding out if it is Lion or no
On Aug 15, 2011, at 07:40 PM, John Joyce wrote:
Thanks for the quick response, John.
> Hi Martin,
>
> NSPopover is not present in the frameworks on 10.6
> You will not be able to use it there.
That I understand, but I want to use it in the app when it's running on Lion.
When the app is runn
On Mon, Aug 15, 2011 at 10:45 AM, David Duncan wrote:
> In either case, the best general way to determine availability of weak-linked
> implementations is to test for them directly rather than using a system
> version check (like gestalt). If your using Clang (which I suspect you are
> not give
On Aug 15, 2011, at 10:47 AM, Kyle Sluder wrote:
> On Mon, Aug 15, 2011 at 10:45 AM, David Duncan wrote:
>> In either case, the best general way to determine availability of
>> weak-linked implementations is to test for them directly rather than using a
>> system version check (like gestalt). I
Is it ok to declare a property to be NSPopover, even if that class doesn't
exist on 10.6?
I tried the
if ([NSPopover class]) {}
trick, but I get the same error when running on 10.6.8. I'll try some more in
case I made a mistake, but….
Thanks!
Martin
On Aug 15, 2011, at 07:47 PM, Kyle Slud
On Aug 14, 2011, at 2:46 AM, Martin Wierschin wrote:
> You make it sound as if a single NSTextView is responsible for completely
> showing all the text in each NSTextStorage. In other words, that each of your
> NSLayoutManagers has exactly one NSTextContainer (and one NSTextView)
> associated
On Aug 15, 2011, at 10:09 AM, Scott Ribe wrote:
> Yes, good point. The expiration date should be just to make sure that the
> next release has actually gotten installed--and I suspect that's what he
> meant, getting reports about bugs in old versions after newer ones have been
> received...
If
On Aug 15, 2011, at 10:56 AM, Martin Hewitson wrote:
> Is it ok to declare a property to be NSPopover, even if that class doesn't
> exist on 10.6?
Yes. Using a class as a data type doesn't create linkage.
> I tried the
>
> if ([NSPopover class]) {}
>
> trick, but I get the same error when r
perhaps I didn't say this earlier, but the problem is not a run-time error as
such; the app doesn't launch. Maybe that provides a clue as to what's wrong?
Martin
On Aug 15, 2011, at 07:56 PM, Martin Hewitson wrote:
> Is it ok to declare a property to be NSPopover, even if that class doesn't
>
On Aug 15, 2011, at 08:13 PM, David Duncan wrote:
> On Aug 15, 2011, at 10:56 AM, Martin Hewitson wrote:
>
>> Is it ok to declare a property to be NSPopover, even if that class doesn't
>> exist on 10.6?
>
> Yes. Using a class as a data type doesn't create linkage.
>
>> I tried the
>>
>> if
On Aug 15, 2011, at 11:19 AM, Martin Hewitson wrote:
>
> On Aug 15, 2011, at 08:13 PM, David Duncan wrote:
>
>> On Aug 15, 2011, at 10:56 AM, Martin Hewitson wrote:
>>
>>> Is it ok to declare a property to be NSPopover, even if that class doesn't
>>> exist on 10.6?
>>
>> Yes. Using a class a
OK, using Clang didn't help. I took out all the NSPopover code I'd added and
confirmed the app runs on 10.6.8. Then I added in the following snippet in to
an action message:
if ([NSPopover class]) {
NSPopover *p = [[[NSPopover alloc] init] autorelease];
}
recompiled with Xcode 4.1 on Li
On Aug 15, 2011, at 10:50 AM, David Duncan wrote:
> On Aug 15, 2011, at 10:47 AM, Kyle Sluder wrote:
>> On Mon, Aug 15, 2011 at 10:45 AM, David Duncan
>> wrote:
>>> In either case, the best general way to determine availability of
>>> weak-linked implementations is to test for them directly rath
OK, problem solved, sort of. Using NSClassFromString makes it work on both
systems. I think I prefer this solution rather than hacking the headers.
Many thanks to all who helped!
Martin
On Aug 15, 2011, at 08:31 PM, Greg Parker wrote:
> On Aug 15, 2011, at 10:50 AM, David Duncan wrote:
>> On A
On Aug 15, 2011, at 07:50 PM, David Duncan wrote:
> On Aug 15, 2011, at 10:47 AM, Kyle Sluder wrote:
>
>> On Mon, Aug 15, 2011 at 10:45 AM, David Duncan
>> wrote:
>>> In either case, the best general way to determine availability of
>>> weak-linked implementations is to test for them directly
On 8/14/2011 1:34 PM, Seth Willits wrote:
On Aug 12, 2011, at 3:03 PM, Charles Srstka wrote:
You could use the copyfile() API. It’s not Cocoa, but it might be a little
cleaner than FSCopyObjectAsync.
It appears copyfile() doesn't give progress callbacks during a single file's
copy?
The m
>> I don't know the particulars of your situation or what might be triggering
>> the cutoff display (are they just descenders?), but have you tried reducing
>> the height of the NSTextContainer while keeping your NSTextView height the
>> same? (You'll have to disable automatic resizing).
>
> I
On Sun, 14 Aug 2011 10:53:28 -0700, Chris Hanson said:
>If you're targeting Mac OS X 10.6 or later, you can set arbitrary
>properties on your objects in Interface Builder that will be set via KVC
>at nib load time.
I just discovered this last week. Are they guaranteed to be set before/after
awa
On Sun, 14 Aug 2011 09:52:41 +0100, Peter Hudson said:
>I have an app with a large number of nib files.
>These have all worked very happily in xCode 3 - and function perfectly
>at run time.
>Interface Builder with xCode 3 has never produced any warnings in
>relation to these nib files.
>
>When I b
On Mon, 15 Aug 2011 10:50:14 -0700, David Duncan said:
>I'd actually forgotten that this required 10.6.8. If you can require
>10.6.8, I would use the new style universally. If you cannot I would use
>the NSClassFromString style until you can.
It's probably a bit early to require a 7 week old OS (
Hi. I have two UIView hierarchies, visually side-by side, but at different
parts of an overall view hierarchy. I'd like to create a single UIImage of the
two, using -renderInContext: and UIGraphicsGetImageFromCurrentImageContext(). I
was able to make one work alone just fine. But when I make my
On Aug 15, 2011, at 2:22 PM, Martin Wierschin wrote:
>>> I don't know the particulars of your situation or what might be triggering
>>> the cutoff display (are they just descenders?), but have you tried reducing
>>> the height of the NSTextContainer while keeping your NSTextView height the
>>>
It looks like Apple's current answer is to programatically create the
custom elements. I find this interesting considering the roasting I
took some time back when I wrote in about a problem I was having
programatically creating a custom element. I remember a lot of
dogmatic evangelism about
On Mon, Aug 15, 2011 at 2:47 PM, Rick Mann wrote:
> Hi. I have two UIView hierarchies, visually side-by side, but at different
> parts of an overall view hierarchy. I'd like to create a single UIImage of
> the two, using -renderInContext: and
> UIGraphicsGetImageFromCurrentImageContext(). I wa
> until a rich uncle dies and I
> can afford the multi-k$ outlay for a *@*@* Intel machine.
The DoJ could break up Apple's anti-trust lock on shardware/software.
There's nothing like paying $1500 for a commodity x86 board and case
with a $39 operating system and beta software installed.
Jeff
On M
Each of my layers is actually a layer hierarchy.
The problem I'm seeing is that if the image context's size is larger than the
layer being drawn, the resulting image is smaller than it should be, even for a
single layer hierarchy.
For example, let's say my layer is 100 px wide, but the image co
On Aug 15, 2011, at 3:56 PM, Jeffrey Walton wrote:
> The DoJ could break up Apple's anti-trust lock on shardware/software.
> There's nothing like paying $1500 for a commodity x86 board and case
> with a $39 operating system and beta software installed.
Oh man, the ‘90s called and they want their
I am currently running a private beta of an app. I use a combination of
private license codes requiring server activation and expiration dates to force
users to stay up-to-date. If a user is not okay with that, then he's probably
not going to be okay with the usual problems beta releases have.
On Mon, Aug 15, 2011 at 4:34 PM, Jens Alfke wrote:
> Oh man, the ‘90s called and they want their anti-Apple arguments back. (Plus
> that Bush CD you never returned.)
And none of this really has anything to do with Cocoa.
--Kyle Sluder
___
Cocoa-dev m
Is there any way to get a list of UITableView cells that intersect a rect? Or
will I have to iterate the cells myself?
--
Rick
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list
-[UITableView indexPathsForRowsInRect:]
Dave
Sent from my iPhone
On Aug 15, 2011, at 4:59 PM, Rick Mann wrote:
> Is there any way to get a list of UITableView cells that intersect a rect? Or
> will I have to iterate the cells myself?
>
> --
> Rick
>
> _
Ha! Thanks. Sheesh, I kept looking for "cellsXXX"
On Aug 15, 2011, at 17:09 , Dave DeLong wrote:
> -[UITableView indexPathsForRowsInRect:]
>
> Dave
>
> Sent from my iPhone
>
> On Aug 15, 2011, at 4:59 PM, Rick Mann wrote:
>
>> Is there any way to get a list of UITableView cells that interse
On Aug 15, 2011, at 3:53 PM, Sean McBride wrote:
> But what about bindings? If a custom view exposes additional bindings, how
> can one connect them in IB? As best as I can tell, you can't. I'd love to
> be corrected!
You can’t. It’s particularly annoying because I had just finished spiffing
On Aug 14, 2011, at 12:36 AM, Eli Bach wrote:
> I wonder what the FinalCutPro and the rest of those apps guys do with all
> their custom UI.
I have often wondered about that question myself. If you look inside the Xcode
bundle you will find a single nib file (MainMenu.nib). So it would appear
On 15 aug 2011, at 19:20, Richard Somers wrote:
>> I wonder what the FinalCutPro and the rest of those apps guys do with all
>> their custom UI.
>
> I have often wondered about that question myself. If you look inside the
> Xcode bundle you will find a single nib file (MainMenu.nib). So it wou
Hello.
I'm having a problem with a UIAlertView that was working fine under iOS 4. Now,
when running under iOS 4.3.2, the application crashes when the user click on
the "Go" button and I'm not sure why, since I haven't changed anything in this
code in months.
Basically, I set up and UIAlerView
Forget my question about Xcode 4 and the stacktrace. I found the slider that
controls how much details is displayed in the navigation view.
My problem with UIAlertView still stands, though :-/
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin
http://
On Mon, Aug 15, 2011 at 7:40 PM, Joar Wingfors wrote:
> That aside, here are my 2 cents on this topic: I don't think that there's a
> lot of value to adding IB plugins for your own custom controls (not that you
> can right now, but even if you could). It makes sense for framework
> developers t
On Aug 15, 2011, at 7:45 PM, Laurent Daudelin wrote:
> I'm having a problem with a UIAlertView that was working fine under iOS 4.
> Now, when running under iOS 4.3.2, the application crashes when the user
> click on the "Go" button
Maybe your delegate object (‘self’ in your snippet) got deallo
What version of Xcode are you using?
There was a bug very similar to this in earlier beta versions of Xcode 4.1.
On Aug 15, 2011, at 7:45 PM, Laurent Daudelin wrote:
> Instead, I have to click the thread in the thread popup in the path-like
> control above the console output. Then, I get the st
> Date: Mon, 15 Aug 2011 19:45:03 -0700
> From: Laurent Daudelin
> Subject: Problems with UIAlertView
> [loginAlertView addSubview:emailAddressTextField];
> [loginAlertView addSubview:passwordTextField];
> [loginAlertView addSubview:iPadNumberTextField];
Not that it necessaril
I'm using Xcode 4.1, build 48103. Crash occurs both on the iPad (running 4.3.2)
and in the simulator (4.3) although I just discovered that if I click the
"cancel" button of the UIAlertView, my alertView:didDismissWithButtonIndex: is
correctly called and it doesn't crash.
Not sure what that mean
On Aug 15, 2011, at 21:39, Matt Neuburg wrote:
>>
>> Date: Mon, 15 Aug 2011 19:45:03 -0700
>> From: Laurent Daudelin
>> Subject: Problems with UIAlertView
>
>> [loginAlertView addSubview:emailAddressTextField];
>> [loginAlertView addSubview:passwordTextField];
>> [loginAlertView
Not sure if it's related to my problem but my last textfield on the view has
its returnKeyType set to UIReturnTypeGo. I've tried to find more about what
this does when the return key on the keyboard is pressed but I don't seem to
find anything explaining what is triggered by this return key type
I finally found out that my UITextField delegate 'textFieldShouldReturn:' is
called. When I detect that the textfield that has returned is the last one on
the view, I call:
[(UIAlertView *)[iPadNumberTextField superview] dismissWithClickedButtonIndex:1
animated:YES];
That's what is removing th
Do you mean UIReturnKeyGo? I can't find a UIReturnTypeGo in my docs.
It just changes the return key to say "GO"
On Aug 16, 2011, at 13:05, Laurent Daudelin wrote:
> Not sure if it's related to my problem but my last textfield on the view has
> its returnKeyType set to UIReturnTypeGo. I've t
Autocorrection enabled text fields and text views in iOS 4.3 simulator
would crash on Lion with autocorrection enabled in System Preferences.
:)
On Aug 16, 2011, at 1:26 PM, Roland King wrote:
> Do you mean UIReturnKeyGo? I can't find a UIReturnTypeGo in my docs.
>
> It just changes the return
On Mon, Aug 15, 2011 at 7:34 PM, Jens Alfke wrote:
>
> On Aug 15, 2011, at 3:56 PM, Jeffrey Walton wrote:
>
> The DoJ could break up Apple's anti-trust lock on shardware/software.
> There's nothing like paying $1500 for a commodity x86 board and case
> with a $39 operating system and beta software
76 matches
Mail list logo
