dhis2-devs team mailing list archive

[Ese Egerega <ese@xxxxxxxxxx>]

Thanks Abyot

On Mon, Oct 26, 2015 at 10:13 AM, Abyot Gizaw <abyota@xxxxxxxxx> wrote:

> Hi Ese,
>
> Thanks for reporting. This is now fixed in trunk, 2.21 and 2.20.
>
> ---
> Thank you,
> Abyot.
>
> On Sat, Oct 24, 2015 at 9:16 AM, Ese Egerega <ese@xxxxxxxxxx> wrote:
> <ese@xxxxxxxxxx>
>
>> Hi Abyot,
>>
>> It Seems there is still a problem with long text / textarea in custom
>> forms. I actually thought it was a problem with my instance until I
>> tested it on the dhis2 demo site.
>>
>> When you add a data element of type long text to a custom form,
>> everything beyond That data element is not displayed in data entry in
>> Tracker capture. When you remove the long text data element from the
>> form, everything displays correctly.
>>
>> Here are some snapshots:
>> http: //www.awesomescreenshot. com / image / 690998 / bdcf6180adeb060e8abf90fadc497d
>> 69
>> <http://www.awesomescreenshot.com/image/690998/bdcf6180adeb060e8abf90fadc497d69>
>>
>> http: //www.awesomescreenshot. com / image / 691004 / 0d22790ca526368fce19a5a7bb0a98
>> ask
>> <http://www.awesomescreenshot.com/image/691004/0d22790ca526368fce19a5a7bb0a98be>
>>
>> Thanks,
>> Ese
>>
>>
>> On Tue, Oct 13, 2015 at 9:34 AM, Abyot Gizaw <abyota@xxxxxxxxx> wrote:
>> <abyota@xxxxxxxxx>
>>
>>> Hi Ese,
>>>
>>> Yes, the aggregate party is more flexible and stack - wooden has Evolved
>>> through time. We will reach two Also- That stage with the tracker.
>>>
>>> I have now Implemented long text / textarea input for 2:20 (check for
>>> rev. 19957).
>>>
>>> Will try two do the same for 2.19. Trunk has alreadytakenusername this.
>>>
>>>
>>> ---
>>> Thank you,
>>> Abyot.
>>>
>>> On Mon, Oct 12, 2015 at 10:21 PM, Ese Egerega <ese@xxxxxxxxxx> wrote:
>>> <ese@xxxxxxxxxx>
>>>
>>>> Thanks for your response Abyot.
>>>> Custom forms Appear to be more flexible with aggregate datasets than in
>>>> the Tracker. Here are screenshots of the same data element in
>>>> aggregate dataset and in Tracker.
>>>>
>>>> Data element in a custom form in aggregate dataset - http://awesomescreenshot.com/
>>>> 0615bcug0c <http://awesomescreenshot.com/0615bcug0c>
>>>>
>>>> The same data element in Tracker - http://awesomescreenshot.com/
>>>> 0265bcyt99 <http://awesomescreenshot.com/0265bcyt99>
>>>>
>>>> Thanks,
>>>> Ese
>>>>
>>>> On Mon, Oct 12, 2015 at 4:50 PM, Abyot Gizaw <abyota@xxxxxxxxx> wrote:
>>>> <abyota@xxxxxxxxx>
>>>>
>>>>> Hi Ese,
>>>>>
>>>>> Do you have some screenshots to share? In custom form, we do not
>>>>> apply any style - you as custom form designer are fully in charge.
>>>>>
>>>>>
>>>>> ---
>>>>> Thank you,
>>>>> Abyot.
>>>>>
>>>>> On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega <ese@xxxxxxxxxx> wrote:
>>>>> <ese@xxxxxxxxxx>
>>>>>
>>>>>> Dear all,
>>>>>>
>>>>>> I am facing a challenge with data elements of type *"long text"* in *custom
>>>>>> forms in* Tracker Capture. Data element with data type "Long text"
>>>>>> ice Usually rendered as *textarea in* n data entry when using the
>>>>>> the default data entry form. However, the same data element is
>>>>>> rendered as an input box *(not* *textarea) in **custom forms* making
>>>>>> it impossible two see parts of your text as you are typing.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I have tried to work around this by overusing HTML style tag two
>>>>>> stretch the input box so it fills the entire cell area but it still does
>>>>>> not make it a *textarea* actually. Any suggestions will be
>>>>>> appreciated.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Ese
>>>>>>
>>>>>>
>>>>>> ______________________________ _________________
>>>>>> Mailing list: https://launchpad.net/~dhis2- users
>>>>>> <https://launchpad.net/~dhis2-users>
>>>>>> Post to: dhis2-users@lists.launchpad. Net
>>>>>> <dhis2-users@xxxxxxxxxxxxxxxxxxx>
>>>>>> Unsubscribe: https://launchpad.net/~dhis2- users
>>>>>> <https://launchpad.net/~dhis2-users>
>>>>>> More help: https: // help.launchpad.net/ List Help
>>>>>> <https://help.launchpad.net/ListHelp>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>