Project

General

Profile

Actions

Feature #22482

closed

Request for GIFBUILDER breakWidth to accept data

Added by Ron Hall over 14 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2010-04-19
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:

Description

Currently the breakWidth property of GIFBUILDER only accepts integers as a value. It would be helpful for this to also accept data.

Here is how it would be of help. When creating graphic headlines it would be great to be able to grab values from the register and use them in the breakLine property much like is done with the max width of images in TYPO3.

Personally, I keep the width of the current container in the register and is what I would use in the above situation.

(issue imported from #M14147)


Files

bug_0014147-breakWidth-stdWrap.patch (550 Bytes) bug_0014147-breakWidth-stdWrap.patch Administrator Admin, 2010-08-26 16:19

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #24090: Optimize stdWrap usage for GIFBUILDERClosedSusanne Moog2010-11-17

Actions
Actions #1

Updated by Ferdinand Kuhl about 14 years ago

Perfect Idea!
I uploaded a patch, which adds stdWrap to breakWidth.
So I can use graphical headers perfectly in my TemplaVoila Containers!

Actions #2

Updated by Jigal van Hemert almost 14 years ago

I expected that this was included in #24090. Asked in core list about the reasons for not including these properties.

Actions #3

Updated by Jo Hasenau almost 14 years ago

This doesn't add stdWrap properties to breakWidth at all.
It's just a check for breakWidth to decide if the limit of 100 characters should be set or not.

The "real" breakWidth is handled in t3lib_stdgraphic which has not been part of the stdWrap optimization yet.

Actions #4

Updated by Jigal van Hemert almost 14 years ago

It's a feature so it can only go in a new version of TYPO3.
#24090 added stdWrap to virtually all Typoscript properties including breadWidth in v. 4.5.

Could you check with current trunk to see if it works as expected?

Actions #5

Updated by Jo Hasenau almost 14 years ago

I tested it with

breakWidth = 200
breakWidth.override = 300

and with

breakWidth.data = GP:test

both work as expected

Since the current stdWrap behaviour is to replace the original value of breakWidth with the result of the stdWrap operations, even the check mentioned in this bug report will remove the limit of 100 characters.

Actions #6

Updated by Jigal van Hemert almost 14 years ago

@Joey: thanks for testing!

Closed as duplicate of 16430 (16430 adds stdWrap support to this property and most other properties)

Actions

Also available in: Atom PDF