When creating a form using three20 components with the methodology found in this example code, there are some strange behaviors with multiple TTTextEditors and UITextFields. Sometimes the fields disappear when touching the next one to enter text. After scouring for a solution, I found someone else with the same problem. Thought it would be useful to see it in his/her words.
My code hardly differs from the example given with three20 so I suspect it is a bug with the library. I too have tried self.autoresizesForKeyboard = NO; but find that it makes typing in a hidden (by the keyboard) field impossible.
I may have found the few lines of code to fix it!
http://github.com/noahmiller/three20/commit/577af26ed4cd636f152e2321fdc6ab08787452af
I found this link via this message
https://github.com/facebook/three20/issuesearch?state=open&q=autoresize#issue/139
Related
I ran to the issue and I cannot get my head around how to solve this. I have four views, each with elements inside has its constraints, you can see the full list in the picture below.
When I run the app, and click on the any one of the text fields, nothing happens and works just fine. However, when I click on the other text field I get this not very pleasant error message.
Well, I followed the steps, and added a symbolic breakpoint, but it did not give any useful information, as you can see below,
I have been stuck on this for a while, and tried many things, including changing the priorities of both views and textfields, as well as deleting some of the constraints that might have caused the problem. Unfortunately, nothing works :( Any help is very appreciated!
You're not doing anything wrong. The TUISystemInputAssistantView mentioned by the console message is not your view. Ignore the message (and file a bug report with Apple). It's not your problem.
I have a document into which I copy all kinds of VBA code regarding questions asked on this site and write code in preparation for answers. This document was created on my PC (with Word 2010). It has no event procedure that runs on the Save event, but at some point a few weeks back it started to ask me the above question before every save, including automatic saves. The document is based on the Normal template which has no code in it. I don't know which code may have caused this to start, nor which code to even suspect. Other documents open in the same instance of Word save normally. It's only this one document that is affected.
The document also contains a lot of special items, like content controls, fields, ActiveX controls, EndNotes, tables and comments. I suspect the comments to be related to this problem in some way.
I know that I could probably stop the alerts by disabling alerts but that isn't what I want. I want Word to display all the normal alerts. It's just this abnormal one which I would like to switch off. Any ideas how to do that? Or what caused Word to issue that alert in the first place?
In these situations I make several backups of the document and then start looking for something that is broken. So using a new backup each time, I systematically delete portions of the document to see if the unwanted / unexpected behavior disappears. For example I first try to isolate the issue to the top of bottom 1/2 of the document. If I can establish that the issue is related to the bottom half then I delete half of the bottom half of the document and so on... it can take a while but it has been an effective method of finding issues for me.
That said, I tried this on a document recently and just ended up going round in circles. I thought I had narrowed the issue down to a single corrupt image, but that turned out to be NOT the case.
I've also found that there are some things that I can do with VBA that Word simply can NOT undo... I'm only aware of a few things (which I'd have to look up in my notes) but I'm sure there's a whole list of things.
A possible workaround might be to clear the undo history for this specific document prior to saving, I imagine that will suppress the message and save you from losing the standard notifications. Hope it helps :)
Good luck!
We have a customized mail template where we can set values of a parameter in mail preference.
After getting upgraded to Notes 9, when the parameter is set to Automatic it's working fine, but when another value is selected below thing happens (It was working fine in previous versions of Notes..):
After opening any external email, after double clicking on the mail body to edit.. notes is getting crashed.
I have two questions :
I see for external emails the control is going from querymodechange to queryclose while editing. Does it always happen?
I debugged the whole thing. Surprisingly it works in debug mode..no notes crash!!
Any help would be much appreciated !!!
This is why customizing the mail template is rarely recommended. There are interactions and dependencies between the code in the template and the Notes client, and it's very hard to debug. Since you haven't shown any of your customized code, I don't think anybody is going to be able to help you. I would recommend removing your customization code one piece at a time until it no longer crashes. Then you'll have an idea of what's triggering it, and you can try a different approach.
When Notes crashes, it dumps some diagnostics in the data/IBM_TECHNICAL_SUPPORT directory, notably the file console.log
You could review it and post here the lines pertaining to the crash.
Also, what was the previous version of Notes ?
To target the offending code line, you can use that old, dirty and tedious trick : add the folling line at the top of the QueryClose event, and move it down until you no longer see the result. Then post the context.
print now & "so far so good"
Just started to use jEdit (I'm a die-hard vi/vim user) and I've come across a question already that I cannot find anywhere.
I want to display any comments in my source code not just in a different colour (I already have that) but also with a highlighted background colour. Unfortunately the shop I am working at currently has a policy of never deleting code but instead commenting out and adding to. Works fine with a few lines of code but occasionally I come across programs where hundreds of lines have been commented out and if it's first thing in the AM I sometimes find myself altering code that has already been commented out.
I know there is the ability to "fold" comments but I'm looking for a colour background alternative.
TIA
N/
Apologies - the answer is in the options.
Highlight the token you are interested in.
Menu>Utilities>Quick Settings>Edit Syntax Style of Token Under Caret>Background Colour
N/
So I have 3 split containers, with 2 panels each.
SplitContainer1 is the main container that is docked in the Form ( Parent ).
SplitContainer1.Panel1 contains SplitContainer2 which is docked.
SplitContainer1.Panel2 contains SpliContainer3 which is docked.
So far so good.
SplitContainer1 has a SplitterWidth of 3.
SplitContainer2 and SplitContainer3 has a SplitterWidth of 6.
In the Designer, you can see the SplitterWidth difference between them, but when I build the solution, the SplitterWidth of SplitContainer2 and SplitContainer3 gets reset back to 4 no matter what I do. I have changed the code in "InitializeComponent" of the form with no effect.
The only way I got this working is in the Load Event of the form, re-specify the SplitterWidths which I find completely dumb. Why won't the SplitterWidths stay at the value I specified in the Designer?
If anyone can shed some light on this, what would be awesome!!
Thanks for your time,
Peter
Just so that this isn't left unanswered for eternity -
This is an old bug that has been in Visual Basic for many versions now, and is never addressed (nor is it likely to ever be addressed).
As Hans Passant mentions, the issue is due to the ISupportInitialize implementation for the SplitContainer.
Since it's a bug, there is not definitive way of resolving the issue that makes any logical sense.
One way, which I've tested in a mock up program, is as #xfx says - Add and manipulate the controls programmatically, rather than using the toolbox.
An alternative is to reload the SplitterWidths programatically, whether that's on Form_Load, which is most likely, or anywhere else in the code that it may be required.